Slack has put coding agents inside the place where many software decisions already happen. Its new Slack Code feature, announced on August 20, lets teams tag agents such as Claude Code, Devin, GitHub Copilot and Vercel from a group chat, with the surrounding conversation supplied as working context. Gizmodo's report says the feature is available across Slack plans.
The pitch is deliberately practical: a colleague reports a bug, a project manager tags an agent, and the agent can begin producing a fix without waiting for an engineer to become available. Slack is also positioning the workflow as multiplayer coding rather than a private chatbot session. The agent works in the same channel as the humans who requested it, while Slack's enterprise controls govern the hand-off.
Unique insight
Slack is trying to make the chat transcript—not the code editor—the system of record for software work.
Analysis
That matters because the bottleneck in enterprise coding isn't only generating a patch; it's deciding what needs changing, who owns the risk and how context survives between teams. Putting agents in channels could reduce the time between a reported defect and a proposed fix, particularly for routine maintenance and internal tools. It also creates a new review problem: conversational context can be incomplete, ambiguous or wrong, even when the generated code looks plausible.
The immediate change is organisational. Developers will be asked to supervise agents that are visible to product managers, support staff and other stakeholders, rather than operating as a specialist tool behind the engineering boundary. Slack says high-stakes actions such as merging code to production still require human sign-off, which is the right dividing line for an initial rollout. Over the next few months, watch whether teams actually merge faster—or merely create a larger queue of agent-generated pull requests that humans must inspect.
Bottom line — If I only remember one thing tomorrow, what should it be?
Slack Code turns AI coding from a solo developer tool into a team workflow, but its value will be measured by review and deployment speed—not by how many agents can be tagged.
- Story type: Breaking news
- Impact: Medium
- Confidence: High (official announcement)
- Audience: Developers
- What changed: Slack launched Slack Code, bringing multiple coding agents into group chats with human approval for high-stakes actions.
- What to watch: Whether Slack reports faster bug-to-merge cycles without weakening production review.
- Reading time: 2 minutes
