Video wird geladen...
Video konnte nicht geladen werden
Now building is a team sport. Introducing Slack Code: a new way for your team and AI agents, like Anthropic's Claude Code, Claude Tag, Devin from Cognition, GitHub Copilot, ChatGPT, and Vercel agents, to write, review, and ship code together. Just mention an agent to spin up a channel,... show more
589,458 Aufrufe • vor 1 Monat •via X (Twitter)
36 Kommentare

@AnthropicAI @cognition @github @ChatGPT @vercel I don't need to be a CEO on a million a year to tell you this is complete useless shit.

@AnthropicAI @cognition @github @ChatGPT @vercel this is fantastic but an absolutely terrible launch. how do i use it?

It's on it's way! Slack Code is rolling out gradually over the next week or so, so it's landing in workspaces on a staggered schedule rather than all at once, keep watching yours and it'll show up soon. We've also added some clarity around rollout timing to the help doc:

@cognition @github @ChatGPT @vercel

@AnthropicAI @cognition @github @ChatGPT @vercel slack? the agentic development IDE?

@AnthropicAI @cognition @github @ChatGPT @vercel spinning up a whole ide in channel so an agent can fix some padding

@AnthropicAI @cognition @github @ChatGPT @vercel This is like an open office environment. None of the employees who work there want this but middle management loves it. People like working on problems on their own over time without feeling like they’re being surveilled by their managers.

@AnthropicAI @cognition @github @ChatGPT @vercel Slack just killed 50 startups

@AnthropicAI @cognition @github @ChatGPT @vercel oof. walmart version of openfloor just dropped.

@AnthropicAI @cognition @github @ChatGPT @vercel We were kinda doing this by invoking agents through Slack this whole time. Now it's native.

@AnthropicAI @cognition @github @ChatGPT @vercel Now wire in @modemdev's customer context graph and they'll ship code that actually solves user needs

Really excited about this. We already use AI agents to write and review code. Bringing them directly into Slack, where the team is already discussing decisions and sharing context, feels like a natural next step. Curious how much this changes the way teams actually build software day to day.

@AnthropicAI @cognition @github @ChatGPT @vercel you now can’t even fart into your SaaS without accidentally vibecoding something

@AnthropicAI @cognition @github @ChatGPT @vercel putting agents in the channel changes who reviews the output, because a thread has an audience and a terminal does not. that shift matters more than the tooling around it.

@AnthropicAI @cognition @github @ChatGPT @vercel This feels like the natural next step for coding agents. Put the agent where the team already communicates, keep humans in the loop, and make the work visible instead of creating another isolated AI workflow.

@AnthropicAI @cognition @github @ChatGPT @vercel no way they put the buy now button right above the bug report thats so on brand for this hellsite

@AnthropicAI @cognition @github @ChatGPT @vercel if future development really belongs in Slack and not IDEs, many developers will have depression after they discover human interaction

@AnthropicAI @cognition @github @ChatGPT @vercel agents in slack is wild, team plus ai in the same channel actually makes sense

@AnthropicAI @cognition @github @ChatGPT @vercel The interesting part isn’t just AI writing code faster It’s having AI agents work alongside the team with the same context and conversations That could seriously change how software teams build and ship

@AnthropicAI @cognition @github @ChatGPT @vercel oh wow! a channel and agents just to change the color of a button.

@SlackAPI @AnthropicAI @cognition @github @ChatGPT @vercel Goodluck with “extra usage” credits needed to run that claude in your slack chats 😆 You work gotta be earning millions to support that. Do yourself a favor and keep your ide’s or claude code or better yet Study coding!

@AnthropicAI @cognition @github @ChatGPT @vercel Agents in Slack channels is a wild idea.

@AnthropicAI @cognition @github @ChatGPT @vercel Bring @subtextdev into the channel so agents can ground their coding work in real user sessions.

@AnthropicAI @cognition @github @ChatGPT @vercel The fix was a button color 🤔

@AnthropicAI @cognition @github @ChatGPT @vercel Hermes and Openclaw

@AnthropicAI @cognition @github @ChatGPT @vercel

@AnthropicAI @cognition @github @ChatGPT @vercel Need cursor for this

@AnthropicAI @cognition @github @ChatGPT @vercel nothing says "ship faster" like putting the agents in the app where every thread goes to die under 14 unread channels

@AnthropicAI @cognition @github @ChatGPT @vercel I want a coding agent that is highly customized / tailored just like the one I have locally. I’d almost want to be able to connect my local agent to these slack code APIs once they are available.

@AnthropicAI @cognition @github @ChatGPT @vercel the context handoff between my MCP agents and the rest of my stack breaks constantly. if slack handled the orchestration natively i'd stop stitching 4 tools together tomorrow.

@AnthropicAI @cognition @github @ChatGPT @vercel Agents on agents

@AnthropicAI @cognition @github @ChatGPT @vercel Didn't this already exist

@AnthropicAI @cognition @github @ChatGPT @vercel This is harder to understand than Opus 5 output

@AnthropicAI @cognition @github @ChatGPT @vercel So you forked claude code inside slack & calling it slack code

@AnthropicAI @cognition @github @ChatGPT @vercel wow this is a terrible way to launch an awesome feature

@AnthropicAI @cognition @github @ChatGPT @vercel Putting agents in one channel changes collaboration, not authority. I’d still bind each agent to a scoped repo/branch, require explicit review/merge ownership, and keep deploy permissions separate. Shared context helps; shared write authority is where reliability breaks.




