Slack has a new channel type — but only agents can create one

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

Slack on Thursday launched Slack Code, a new kind of Slack channel that’s built for coding agents and the developers supervising them.

Now, if you mention a supported agent anywhere in Slack and it decides that the request isn’t a good fit for a threat, it will spin up a code channel that carries its plan, the repository and branch it’s working in, code diffs, pull request information, and a live HTML preview of the output.

People in the channel can then request changes or stop the agent. Once the work is done, the agent archives the channel, though it remains searchable and, Slack says, can function as an audit log.

Interestingly, humans — at least for now — can’t spin up a code channel themselves.

Credit: Slack.

Slack Code is now live for teams using Anthropic’s Claude, Cognition’s Devin, GitHub Copilot, and Vercel, with OpenAI’s ChatGPT coming later. It’s available on any Slack plan, including free workspaces, and Slack isn’t charging extra for it, Katie Steigman, vice president of product at Slack, tells The New Stack.

Overall, this seems like a logical move for Slack. Today, most coding agents are single-player experiences that happen in a terminal, an IDE, a desktop app, or a browser session, though the industry has been pushing them toward team infrastructure for months.

Steigman says, “There’s a shift we need to make from sort of siloed, single player kind of AI work, like I’m working in my terminal, I’m doing my thing with whatever agent, to bringing that into a multiplayer environment.”

Why agents need a different kind of channel

Slack already has …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://thenewstack.io/slack-code-agent-channels/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.