AI news videos

Slack Code API Is Now Generally Available on All Slack Plans

Slack has made the Slack Code API generally available on all Slack plans, so any developer can have their own AI coding agent open a Slack code channel.

Watch on YouTube

Transcript

Sources

Every claim in this video comes from the top ranking coverage of this topic. The claims and where each one came from:

• Overall provenance. The watcher alerted on a Salesforce newsroom linked-content URL, but a GET with redirects resolves in two hops to this first-party Slack developer blog post, bylined Rebecca Walker, dated October 28th, 2026, tagged Product Update and Engineering and Developers, with the footer '(c)2026 Slack Technologies, LLC, a Salesforce company.' So the Short credits Slack's own announcement rather than third-party coverage. This is a general-availability product launch, not a customer testimonial and not sponsored content, which is why the Short carries an assertive BREAKING framing with no 'not independently verified' disclaimer scene. The article is the sole source: YouTube transcript research returned zero usable transcripts and the dated-title probes returned only unrelated generic Slack API tutorials, so no corroborating outlet is cited. Deliberately NOT narrated: pricing, user counts, competitor comparisons, and any Salesforce financial framing, because the article contains none of those facts. Two items in the article are explicitly labelled by Slack as available soon and are therefore treated as unshipped throughout: the improved Pull Request experience in Slack Code, and the enhanced Agents and Tools tab.(Introducing the Slack Code API: Your agents, your team, one code channel)
• Hook. Traces to 'Today, that changes. The Slack Code API is now generally available, so any developer can have their agent start a code channel, adding the relevant people and files, posting updates as it works, and archiving the channel when the work is done.' The hook says 'live now' rather than 'today' because the narration rules forbid speaking a calendar date or the word 'today'; the dated byline is carried in the on-screen text and in this sources block instead. Deliberately NOT narrated: the article's framing phrase 'agentic development shouldn't be single-player', both because 'agentic' garbles in the voice engine and because 'single-player' is a figure of speech. Nothing in the hook refers to an available-soon feature.(Introducing the Slack Code API: Your agents, your team, one code channel)
• Scene 1, what shipped. Traces to two sentences: 'The Slack Code API is now generally available, so any developer can have their agent start a code channel' and, from the Get started section, 'The Slack Code API is generally available today on all Slack plans, so you can start building right away.' The scene therefore asserts general availability on all Slack plans as a shipped fact. Deliberately NOT narrated: the Slack Marketplace publishing path and the named Marketplace agents Claude, Devin, GitHub Copilot and Vercel, cut purely for the word budget, not for any doubt about them; also cut is the article's 'BYOA: Bring your own agents' label, since that angle is carried in a title candidate rather than spoken. No available-soon feature is implied here, because general availability in this scene is stated by Slack as present-tense and live.(Introducing the Slack Code API: Your agents, your team, one code channel)
• Scene 2, the mechanic. Traces to 'any developer can have their agent start a code channel, adding the relevant people and files, posting updates as it works, and archiving the channel when the work is done' and to the How it works section: 'When a teammate mentions the agent in a channel or a DM, if the request needs more than a quick reply, the agent creates a dedicated code channel and adds bookmarks and artifacts so people can follow along. As the work progresses, it posts updates and status, and it can archive the channel when it's finished.' The narration keeps the article's 'can archive' hedge rather than stating the agent always archives. Deliberately NOT narrated: the agent manifest configuration detail, the bookmark and artifact primitives, the code diff, HTML preview and thinking-step rendering surfaces, and the 2:00 a.m. observability-alert story, all cut for the word budget; the article's phrases 'out in the open' and 'cramped fast' are excluded as figures of speech. Nothing in this scene is an available-soon feature; channel creation, updates and archiving are all described as shipped in the generally available API.(Introducing the Slack Code API: Your agents, your team, one code channel)
• Scene 3, evidence and demand. Traces to 'GitHub Copilot is proving this works at scale: It opens a dedicated code channel on 30% of its agent sessions' and to 'More than 150 customers and partners asked for access to build code channel experiences for their own agents, but only a handful of our partners had the keys to delivering this experience.' The thirty percent figure is explicitly attributed in narration to Slack, because Slack is reporting a measurement about a partner's product and no outside party measured it. Deliberately NOT narrated: the launch partner list of Anthropic, Cognition, GitHub and Vercel, and the August 2026 launch of Slack Code itself, both cut for the word budget; the Tim Hunter pull quote from GitHub is excluded because it is marketing praise containing the idiom 'game changer', and the Mael Kerichard pull quote from Mistral is excluded for the same reason. The article's gloss 'nearly a third of the time' is replaced by the literal thirty percent. No available-soon feature appears in this scene.(Introducing the Slack Code API: Your agents, your team, one code channel)
• Scene 4, governance plus the honest limit. The governance half traces to 'Your agent inherits the permissions and admin controls of the channel it works in. There's no separate access model for you to build, and IT has nothing new to configure.' The limit half flags the two features Slack itself marks as not yet shipped. On Pull Requests: 'And, available soon, the latest improvements to the Pull Request experience in Slack Code extend this multiplayer philosophy all the way to deployment', including the future-tense 'Once a PR is approved and tests pass, you'll get a prompt to merge it directly from the code channel.' On the agent directory: 'your teams will find them all in the enhanced Agents and Tools tab, available soon.' The narration states plainly that both are not available yet, so viewers do not read them as part of the general-availability release. Deliberately NOT narrated: bi-directional Slack to GitHub comment sync and the GitHub review-request flow, which belong to the same unshipped Pull Request work, plus the built-in message compliance, workspace controls and data boundaries, cut for the word budget. The article's phrase 'bird's-eye view' is excluded as a figure of speech.(Introducing the Slack Code API: Your agents, your team, one code channel)