This week we look into the launch of Slack Code. Salesforce's new product turns any Slack conversation into a dedicated workspace where AI coding agents such as Claude Code, Devin and GitHub Copilot can plan, write and ship code together, with a human still required to sign off before anything reaches production.
Mike Belsito unpacks how the launch fits Slack's rough year, what it means that Anthropic was named a founding partner just three days later, and why product managers should be paying close attention to the permissions model behind every agent platform they adopt.
Key takeaways
- Slack Code turns any Slack conversation into a dedicated workspace where coding agents can plan, write and ship code, splitting work into a conversation tab, a plan tab, a diff view and a live preview, with a human still required to sign off before anything reaches production.
- The launch reads as counter-programming for a difficult year at Salesforce, whose stock has lagged the market and whose Slack CEO defected to OpenAI, prompting the company to go on the offensive with AI rather than retreat.
- Vibe coding is no longer a fringe habit: it is already a $4.7 billion market projected to triple by 2027, with 63% of people doing it describing themselves as non-developers.
- Slack's bet is that coding works better as a team sport than a solo terminal session, wagering that visibility and peer comment beat one person working alone with an agent in private.
- The same openness that makes Slack Code powerful raises the stakes on quality: independent research puts the exploitable-vulnerability rate in AI-generated code at roughly 44%, even as AI-assisted developers ship three to four times faster than everyone else.
- Barely three days after launch, Slack Code's neutral positioning shifted when Salesforce and Anthropic announced Claude Force, naming Anthropic a founding partner and making Claude the default model across the Slack and Salesforce stack.
- For product managers, the workflow modelled by Slack's own VP of product, tagging in an engineer before asking for approval and taking one more pass on the agent's output, may become the template for contributing real code without pretending to be an engineer.
Chapters
- (00:00) Introduction and the new one-story format
- (01:15) Slack Code launches
- (02:15) Inside the Devin demo
- (03:35) Why now for Slack
- (05:20) Vibe coding by the numbers
- (07:05) Multiplayer versus single-player coding
- (07:55) The AI slop problem
- (11:00) Permissions and sandboxing
- (12:05) The Claude Force twist
- (13:25) What it means for product managers
- (16:15) The model war question
- (16:30) Wrap-up
