Source: VentureBeat — 2026-08-21
Summary
Slack launched a feature — internally called Slack Code — that lets a team tag a coding agent (Claude Code, Devin, GitHub Copilot, or Vercel's agent are all supported) directly inside any Slack channel. Doing so spins up a dedicated project channel showing the agent's live diffs, a running plan, and preview links, and the channel auto-archives once the work is done. The pitch is moving AI coding work out of a single developer's terminal and into a shared, visible team surface, multi-vendor by design rather than locked to one agent provider.
Key Takeaways
- Multi-vendor support: works with Claude Code, Devin, GitHub Copilot, and Vercel's agent — Slack isn't picking a single coding-agent winner, it's building a shared surface across them.
- Mechanism: tagging an agent in any channel auto-creates a dedicated project channel with visible diffs, a running plan, and live previews — the coding work becomes a shared, observable artifact rather than something happening invisibly in one person's terminal.
- Auto-archiving once work completes keeps the shared-channel model from accumulating clutter as more coding tasks get delegated this way.
- Targets a real coordination gap: today, a teammate has no visibility into what a coding agent is doing on someone else's machine unless that person screen-shares or narrates it manually.
- Part of a broader trend of agentic coding tools moving from single-developer, local-only workflows toward team-visible, chat-native surfaces.