Salesforce Opens the Slack Code API: Your Own AI Agents Can Now Join Development Channels

On October 28, 2026, Salesforce (via Slack) announced the general availability of the Slack Code API, on all Slack plans. Launched in August 2026, Slack Code already let teams create dedicated "code channels" where human developers collaborate with partner AI agents (Claude Code, Devin, GitHub Copilot, the Vercel agent, and ChatGPT rolling out). The October 28 update changes the tool's scope: any custom AI agent, built in-house or by a third-party vendor, can now plug into the same mechanism — not just the launch partners Salesforce originally selected. Technical documentation is published at api.slack.com/partners/code-channels.

What the API Actually Enables

• Channel creation from a conversation: an agent can open a dedicated code channel from a simple mention in a channel or a direct message, with the relevant context and people already attached.
• Configuration via agent manifest: channel name, available commands, and views (tabs) are declared in the agent's manifest, with no need to build a dedicated interface.
• Built-in display: code diffs, HTML previews, and the agent's reasoning steps render through standard Slack components — the agent's developer doesn't have to build their own UI.
• Inherited permissions: the agent inherits the existing Slack channel's access rights and admin controls; per Slack, "there's no separate access model for you to build."
• Compliance and traceability: messages remain subject to Slack's existing compliance rules, and the agent's work stays searchable after the channel auto-archives.

What's Announced But Not Yet Available

Two features named in the announcement are explicitly marked "available soon" and are therefore not yet live as of October 28, 2026: bidirectional GitHub pull-request comment sync with a merge prompt after approval and passing tests, and an enhanced "Agents & Tools" tab. Slack also cites a figure supplied by GitHub: Copilot reportedly opens a code channel for 30% of its agent sessions — a partner-supplied figure, not an independent measurement, and should be treated as such.

What This Actually Means for Your Decision

• If your company has built or is considering building an internal AI agent (support, HR, legal, operations): the API lets you connect it to Slack with built-in audit logging and permissions, without building a dedicated collaboration interface from scratch.
• If you already use Claude Code, Devin, GitHub Copilot, or the Vercel agent on Slack Code: no action is required — the API's general availability doesn't change how you currently use these launch partners.
• The announcement publishes no API-specific pricing — access depends on the company's Slack plan, while each third-party partner agent (Claude, Copilot...) keeps its own separate license.
• Since bidirectional GitHub sync isn't available yet, don't build a production approval flow that depends on it before general availability is confirmed.

Considering connecting an internal AI agent (support, HR, operations) to your existing collaboration tools? Our custom development offering scopes the technical integration and permissions before go-live.