@GitHub in Slack and Teams is generally available: investigate bugs, create issues, implement changes and open pull requests from a conversation, with Canvas in Teams for reviewing plans together
The entry point for coding agents now reaches team chat: work can be handed off from wherever the discussion happens.
// Key points
- Mention @GitHub in Slack or Teams to investigate bugs, create issues, implement changes and open pull requests without leaving the conversation
- Canvas in Teams lets people review implementation plans, code changes and previews next to the conversation and keep refining together
- @GitHub now identifies the repository from the message and launches the session without asking you to select it again
- Issues and pull requests it creates include "Created from a Slack/Teams conversation with @username" in their description
Builder's takeOpening a PR from one chat message lowers the bar, and review volume will rise with it. I would enable it on one non-core repository first, watch merge and rework rates for two weeks, then decide on the main repos; the automatic "created from a conversation with @user" line is exactly the accountability trail we need for agent-made changes.
// Background · from #Coding agents
Full timeline →- Nov 8 Copilot code review settings can be managed through the REST and GraphQL APIs from enterprise down to repository, and comments report the skills, MCP servers and custom instructions they drew on
- Nov 7 AWS runs Claude Code as a remote agent on Bedrock AgentCore: one microVM per task, up to three attempts, and a draft pull request unless verification passes
- Nov 7 Foundry Local runs Qwen3.8-27B at 4-bit in about 18 GB, on 24 GB consumer GPUs with up to 64K context, as a GitHub Copilot model provider