Slack Launches 'Slack Code' to Bring AI Software Agents Into Team Channels
The new 'Multiplayer AI Coding' feature integrates agents like Claude Code and GitHub Copilot directly into shared chats to move development out of isolated terminals.
Slack has launched Slack Code, a new feature that integrates AI coding agents directly into shared team channels. The move aims to shift software development from isolated terminals into a collaborative, "multiplayer" environment where human developers can monitor and steer AI agents in real time.
Under the new system, AI agents—including Claude Code, Devin, and GitHub Copilot—can write, review, and ship software within the chat interface. According to company descriptions, this "Multiplayer AI Coding" approach allows entire teams to see agent activity as it happens, providing a transparent stream of technical work that was previously hidden in private IDEs or command-line interfaces.
The Shift to Agentic Workspaces
This launch comes as AI tools evolve from simple autocomplete suggestions into autonomous agents capable of handling complex development tasks. Traditionally, the software development lifecycle has been siloed within specialized tools, creating a gap between the engineers writing the code and the rest of the organization. By integrating these capabilities into its chat platform, Slack is positioning itself as the central nervous system of work, bringing the technical execution layer into the same hub where project management and communication already occur.
Why Collaborative Coding Matters
Moving AI development into a shared space transforms software engineering from a solitary activity into a transparent process. By making the actions of AI agents visible to the whole team, Slack Code reduces the "black box" nature of autonomous coding. This visibility simplifies the peer-review process and allows non-coding stakeholders to stay aligned with technical progress without needing to navigate a codebase or terminal.
What's Next for AI Development
As teams begin adopting these integrated agents, the industry will be watching how this affects the traditional developer workflow and the role of the IDE. While the goal is to increase transparency and speed, the transition from isolated terminals to a chat-based environment represents a fundamental change in how software is built. It remains to be seen how these agents will handle complex, multi-file architectural changes within the constraints of a communication interface.