20d • General discussion
Vibe Code with agents directly in slack?!
Wow. Check this out!
Slack Code — what it actually is and why it matters
Slack shipped agent channels. Here's the whole thing in plain English.
You mention an agent in any channel and it spins up a temporary code channel. That's the workspace — you, your team, and the agent in one room instead of you alone in a chat window copy-pasting context back and forth.
And that's the real unlock: the agent opens with your team's context already loaded. The conversations, the decisions, the files. It isn't starting from zero every session like every other AI tool you've used. That's the difference between an assistant and a coworker.
Four agents run inside it right now — Claude, Devin, GitHub Copilot, and Vercel.
You don't need to be technical. Watch what the agent builds, look at the preview, type "make the button purple." That's the entire workflow. If you can give feedback in a Slack thread, you can drive this.
Nothing ships without your sign-off. Same security stack as the rest of Slack — EKM, DLP, Discovery APIs. You review, you approve, then it goes.
When the work is done, the channel archives itself. Context stays searchable, your main channels stay clean.
Why I'm posting this here: this is the glue problem solving itself in public. The bottleneck was never the model — it was that every tool started from scratch and lived somewhere your team wasn't. Slack just moved the agent to where the context already lives.
Full breakdown: https://slack.com/features/code-channels
If your agent had your last six months of Slack loaded on day one, what's the first thing you'd hand it?
0
0 comments
Vibe Code with agents directly in slack?!
powered by
skool.com/ai-integration-algofuse-4947
Learn the structure behind AI, glue it into your business, and get your team actually using it with MCPs, apps, APIs, data, and workflows.
Suggested communities
Powered by