Slack Code drops native vibe-coding channels with Claude and
What actually changes day-to-day
- Agent tabs are persistent — each coding task gets a named tab (e.g., "refactor-auth-flow") that stays attached to the channel. Teammates can scroll back, review the diff, drop comments, or take over mid-session.
- Diff-first workflow — changes render as unified diffs inline. You approve, request tweaks, or merge with one click. No separate PR tab unless you want one.
- Live preview for web work — HTML/CSS/JS changes render in an iframe pane. Backend changes show test output. It's basically a lightweight Codespace pinned to the discussion.
- Multi-agent handoff — start with Claude for architecture, hand off to Devin for implementation, tag a human for review. All in the same thread.
The integration feels like what GitHub Copilot Workspace wanted to be but buried inside a browser tab. Here the context — product specs, design screenshots, prior decisions — already lives in Slack. The agent inherits that history automatically.
Where it still feels rough
Authentication is the obvious friction point. The agent needs repo access, CI secrets, maybe staging deployment keys. Slack's handling this through a new "Connected Apps" layer that scopes tokens per channel, but setup still requires an admin step. Also, the preview pane only supports static assets and Node/Python simple servers today — no Docker Compose, no database spin-up. For anything beyond a marketing page or API endpoint, you'll still kick off a real preview environment.
Pricing hasn't been announced. My guess: per-agent-minute on top of the Slack seat, similar to how Slack AI bills. If you're already paying for Claude API or Devin seats, this might just be a UI wrapper. Worth asking your account rep.
Bottom line
If your team lives in Slack and codes in VS Code, this removes a genuine context-switch tax. The "vibe-coding" branding is cringe, but the primitive — code as a first-class channel citizen — is the right abstraction. I'll be testing it on a side project this week; the diff review flow alone could replace half our PR comments.
