Slack Code API: Who Governs Your Coding Agents?

Key takeaways

• On 28 October 2026, Salesforce published the Slack Code API, which lets agents create, review and archive code work inside a dedicated Slack channel.
• That makes Slack the place where coding agents and your team meet, so Slack is also where agent permissions will get decided in practice.
• Salesforce teams should name an owner for agent access to their orgs this week, before individual developers connect agents on their own.
• Keep a list of every agent and what it touches.

On 28 October 2026, Salesforce published Introducing the Slack Code API. The same day, Slack's developer blog posted Build with Slack Code: create, review, and archive agent work. Slack Code itself, the coding channels, was introduced in August 2026. The API is what lets your own agents join those channels.

One caveat. I've read the announcement and the developer post, and I haven't tested the API. Permission scopes, identity handling and audit details are things I'm not going to guess at.

What does the Slack Code API actually do?

It turns a Slack channel into the working surface for a coding agent, not just a chat window beside it.

Slack's own description is an agent that investigates a bug, implements a change, shares a diff and works through feedback with teammates, all in one channel. The launch coverage names agents such as Claude Code, Devin from Cognition and GitHub Copilot as part of the coding boom. The API is how your agents, including ones you build, get that same seat.

Until now, most coding-agent work happened in a developer's private terminal. That was a governance gap, but a quiet one. Moving the work into a shared channel makes it visible, and visibility is half of governance.

Who should govern coding agents in your Salesforce org?

One named person, usually an architect or your centre of excellence lead, not whichever developer wires it up first.

Here's the second-order effect nobody's talking about yet. A channel is easy to join, and "looks good, ship it" is easy to type. If channel membership starts to feel like permission, you've built a weak review process with a nice interface.

For example, a services company might let a developer connect an agent to a sandbox through a connected app with broad scopes, because it's quicker. Six weeks later nobody remembers what that agent can deploy. That's a hypothetical, but I'd bet it's happening somewhere already.

My take: Channel membership must never equal deploy permission. The person who can add an agent to a code channel should not be the person who decides what that agent can touch in production. Split those two decisions on paper before anyone connects anything.

What will coding agents cost your Salesforce org?

My Agentforce pricing calculator is a place to start modelling it.

The risk side is familiar. Agents drift, and teams don't notice for a long time. I wrote about three questions to ask before an agent goes into production, and they apply to a coding agent just as much as a service agent.

How do you roll out coding agents safely in Salesforce?

Start read-only, keep a human approving, and let the agent earn wider access.

That's how I'd roll out any agent. Give it a narrow job, access to a sandbox and nothing more, and a named human who approves every change. If you're already thinking about Slack as an AI surface, what Slackbot is and how to roll it out covers the admin side.

My take: Slack is becoming the control room for agents, which means your Slack admins are about to become part of your security team. Most companies haven't told them yet.

Try this week:

• List every coding agent your developers already use, and what credentials each one holds.
• Name one owner for agent access to your Salesforce orgs, and write down what an agent may never do (production deploys, permission set changes).
• Require a human reviewer outside the channel conversation for any change an agent proposes.

If you want a second pair of eyes on your setup, get in touch.

Frequently asked questions

What is the Slack Code API?

It's an API Salesforce announced on 28 October 2026 that lets agents create, review and archive code work in Slack Code channels, according to Slack's developer blog. Slack Code channels were introduced in August 2026.

Does the Slack Code API give agents access to my Salesforce org?

Nothing I've read says it does by itself. Access depends on how you connect the agent and what credentials it holds, so treat that as your decision, not Slack's.

Should Salesforce teams adopt Slack Code now?

Pilot it in a sandbox with one low-risk task and a human approving. Don't connect agents to production until you've written down who owns their permissions.