|
Salesforce announced Thursday Slack Code, a product that moves AI coding out of private browser tabs and into Slack, where the whole team can see and steer it. Mention a coding agent on a piece of work — Anthropic’s Claude, Cognition’s Devin, GitHub Copilot, or Vercel’s agents are live at launch, with OpenAI’s ChatGPT coming soon — and it spins up a dedicated “code channel” shaped around the task: code diffs, planning docs, and live HTML previews appear right in the channel, where teammates can watch the agent work, weigh in, redirect it mid-task, and approve changes before anything ships. When the work lands, the channel archives itself and stays searchable as an audit log. Slack Code is available today on any Slack plan (partner-agent access required separately), inherits Slack’s existing permissions and admin controls, and can route high-stakes changes to a human for approval in the channel. Slack reports that internally, more than 70 percent of code channels spin up and close within a single day, idea to merged PR, and it plans to open the code-channel APIs so agents doing any kind of work — marketing campaigns, legal review, IT onboarding — can use the same surface. GitHub chief product officer Mario Rodriguez: “Humans set direction, agents close the loop.”
Why it matters for PMs: This is the clearest signal yet that the conversation where work is requested is becoming the surface where work is built. Salesforce’s own launch example is a product manager: spot a bug report in a channel, ask an agent to architect the fix, bring in an engineer to check the diff and approve the PR — no ticket, no meeting. If your org lives in Slack, expect small fixes and prototypes to start bypassing the backlog entirely, which changes what the roadmap is for. Three patterns worth stealing: visibility as governance (work happens in the open and auto-archives into an audit trail, with inherited permissions instead of new configuration), explicit human approval gates on high-stakes changes, and the aggregation play — Slack builds no agents itself; it owns the front end where competing agents meet your team’s context. Whoever owns that workspace in your category holds the leverage. If your product’s work starts in someone else’s canvas, you’re the backend.
|