Eigen RadarAI
Archive
Analysis

The coding agent is moving out of the private window and into the team channel

GitHub and Slack are moving the coding agent out of the private window and into shared channels, while the new Microsoft Teams session lets teams start and watch the same work inside one flow.

Artificial Intelligence··Night
A small autonomous vehicle on a turquoise-lit rail moves from an isolated work cell into a bright shared production area where two people are seen from behind.

GitHub puts failure investigation inside the Slack channel

GitHub has opened a public preview of a Copilot agent that runs inside Slack when a team mentions @GitHub. The agent answers questions about code and repository activity, tidies issues, investigates failures in a secure sandbox and ties the resulting change back to a pull request opened from the same conversation. That workflow is different from a lone developer chatting with a private assistant window: the team can follow progress inside a Slack Code channel, review diffs together and require another approval step before the change lands in the repository. The feature is limited to Copilot Business and Enterprise plans and draws on the cloud-agent budgets those plans already set.[1]

Slack keeps the shared flow visible from the start

Slack's product logic points the same way. According to The Register, dedicated code channels let participants pause or redirect an agent, keep higher-risk actions behind expert approval and inherit existing permissions instead of rebuilding them. Agent work is therefore set up as a process the group can watch and interrupt together rather than as an output shown only at the end. The channel acts as both the conversation surface and the review surface.[2]

Teams connects the meeting to a shared working session

GitHub's Teams preview carries the same shared-work idea into the meeting flow. Work that starts with an @GitHub mention in a channel or thread continues asynchronously inside a secure cloud sandbox, with progress visible in dedicated code channels. Administrators enable the cloud agent and cloud sandboxes, set a default repository for public channels and can demand extra approval on Copilot-authored pull requests. The shared agent session therefore turns what a meeting discussed into an ongoing development flow that the team can see and steer together.[3]

References

  1. News sourceGitHubGitHub's Slack agent debugs in a sandbox and opens the pull request↩
  2. News sourceThe RegisterSlack Code moves coding agents from the terminal into project channels↩
  3. News sourceGitHubCopilot turns a Microsoft Teams discussion into a shared agent session↩
AI safety and regulation

More analysis from this desk

View all Brief analyses from the Artificial Intelligence desk →