AI 模型和平台
Slack 代码 API 达到所有 Slack 计划的一般可用性
在 Google 上的首选来源中添加 Unite.AI
Slack使Slack代码API于2026年10月28日在所有Slack计划中普遍开放，于2026年8月将其发布的代码通道系统开放给任何开发商的agent. 在Slack开发者博客的一篇文章中，称公司超过150个客户和合作伙伴要求为自己的agents建立代码通道体验，这种能力以前仅限于少数发布合作伙伴。
8月，Slack 推出 Slack代码与包括Anthropic,Cognition,GitHub，和Vercel在内的合作伙伴并列，发布的公告也命名了OpenAI，并很快将ChatGPT列出。 一个代码频道是一个agent为单一任务打开的专用空间，其中包含合适的人，上下文，并且已经计划；当工作完成后，该频道自行归档，但仍然可以搜索。 Slack在发布上报道，超过70%的代码通道在一天之内旋转和关闭，从想法到合并拉请求。
带上自己的Agent
随着API的普及，任何开发者都可以让agent启动一个代码通道，添加相关的人和文件，在工作时发布更新，并在工作完成时归档频道。 Slack 称开发者获得其发布合作伙伴使用的相同原始，无论是为企业建造本土的agent还是为Slack市场建造新的agent.
Slack 称将编码agents带入Slack之前是指通过标准线程和直接消息输出agent的路由，它描述为agent需要附加一个大日志文件，提出50行代码diff，或者运行一个多步执行计划后抽筋。 安全性要求严格的企业Slack 称，完全不能使用现成的第三方agents.
公司形容API解锁了三种能力：agents在开放中工作，在请求需要自己的空间时通过创建自己的代码通道；agents 整个团队可以引导，使用书签和完整的执行历史；agents 企业可以信任，在已经使用的工作空间控制和数据边界管理员同时构建消息遵守。 API可以显示代码diffs,HTML预览，以及思考步骤，而Slack处理其余接口。 Slack 称它仍然是agent中立的中枢，因此球队可以稍后交换agents或型号，同时继续在同一地点工作。
Slack报告说，GitHub Copilot在其30%的agent会话上打开了专用的代码频道。 蒂姆·亨特(Tim Hunter)是GitHub的一位员工工程师，称 GitHub正在建设Copilot互动用户已经熟悉到他们完成其余工作的地方。 Mael Kerichard是Mistral的软件工程师，称 API在设计时曾想到AI agents，指出其灵活性，设置简单，功能深度。
根据 Slack 构建治理：agent 继承了它所工作的频道的权限和管理员控制，没有单独的开发者建立访问模式，也没有新的IT配置。 一个人可以批准每次高收分的更改，在频道存档后，agent所作所为的记录仍然可以搜索。
Slack在凌晨2:00用生产警示说明模型，其中自定义的可观察性agent打开一个代码通道，在相关日志中拉动，并开始固定工作，同时随叫随到的工程师阅读并重定向其中任务。 公司称相同的模式适用于bug 分类和DevOps 任务，例如配置更改或回滚。
API如何运作
Slack的开发者文档称，应用通过两个API方法家族控制一个代码频道的标题，状态，上下文栏，并查看标签。 agents.sessions.*方法在代码频道和会话线索之间统一，由线程时间戳参数选择会话类型，它们需要聊天：write范围。 agents.conversation.* 方法管理代码通道特定任务，并要求代码通道：管理范围。
已记录的 agents.conversions.* 方法包括创建，归档(可以选择记录摘要)，设置Properties，设置Commands，设置View(支持html,diff,block kit，或canvas视图)，列表视图，删除View，获得Canvas，以及设置CanvasContent.
Apps通过设置特性来启用代码通道。 code channels. 启用后，程序显示中为真，可选的斜线 command url。 当一个用户提到该应用程序时，它会收到一个app mention事件，并决定是创建专用的代码频道还是就位回复。 创建调用取自源频道和消息时间戳；Slack然后创建频道，匹配其隐私设置，并自动邀请bot.
在有文献记载的授权模式下，调用者必须是指定给频道或频道成员的agent bot，否则调用返回不为 agent channel或不为授权错误。 代码频道被设计为半ephemeral(每个任务一个频道，会话结束后存档)，一次归档一个频道及其历史仍然可以观看，可以搜索，并能重新开放。
即将到来的工具和如何开始
Slack 称对拉动请求体验的改进很快就可以得到：GitHub用户可以在Slack中请求审查，评论会在Slack和GitHub之间双向同步，一旦拉动请求获得批准并测试通过，一个合并提示就会出现在代码通道中。 强化的Agents & Tools标签也被列出为很快可用的，提供了agent对话的鸟眼视图和具有状态，频道成员，以及最近上下文的代码频道，再加上浏览公共代码频道的能力。
Slack概述了三种开始方式：阅读文档并在agent运单中加入API，向Slack市场提交agent，或尝试在市场中现有的Slack代码agents，包括Claude,Devin,GitHub Copilot，以及Vercel.
本文由 AI图鉴自动抓取并翻译，版权归原作者所有；如需查看原文请点下方链接。
AI Models & Platforms
Slack Code API Reaches General Availability on All Slack Plans
Add Unite.AI to your preferred sources on Google
Slack made the Slack Code API generally available on all Slack plans on October 28, 2026, opening the code-channel system it launched in August 2026 to any developer’s agent. In a post on Slack’s developer blog, the company said more than 150 customers and partners had asked for access to build code-channel experiences for their own agents, a capability previously limited to a handful of launch partners.
Slack introduced Slack Code in August alongside partners including Anthropic, Cognition, GitHub, and Vercel, with the launch announcement also naming OpenAI and listing ChatGPT as available soon. A code channel is a dedicated space an agent opens for a single task, with the right people, context, and plan already in it; the channel archives itself when the work is done but remains searchable. Slack reported at launch that over 70% of code channels spin up and close within a single day, from idea to merged pull request.
Bring Your Own Agent
With the API generally available, any developer can have an agent start a code channel, add the relevant people and files, post updates as it works, and archive the channel when the work is done. Slack said developers get the same primitives its launch partners use, whether they are building a homegrown agent for an enterprise or a new agent for the Slack Marketplace.
Slack said bringing coding agents into Slack previously meant routing agent output through standard threads and direct messages, which it described as cramped once an agent needs to attach a large log file, propose a 50-line code diff, or run a multi-step execution plan. Enterprises with strict security requirements, Slack said, could not use off-the-shelf third-party agents at all.
The company describes the API as unlocking three capabilities: agents that work in the open by creating their own code channel when a request deserves its own space; agents a whole team can steer, using bookmarks and a full execution history; and agents enterprises can trust, with message compliance built in alongside the workspace controls and data boundaries admins already use. The APIs can show code diffs, HTML previews, and thinking steps while Slack handles the rest of the interface. Slack said it remains an agent-neutral hub, so teams can swap agents or models later while continuing to work in the same place.
Slack reported that GitHub Copilot opens a dedicated code channel on 30% of its agent sessions. Tim Hunter, a staff engineer at GitHub, said GitHub is building the Copilot interactions users are already familiar with into the same space where they do the rest of their work. Mael Kerichard, a software engineer at Mistral, said the API felt designed with AI agents in mind, pointing to its flexibility, simple setup, and depth of functionality.
Governance is built in, according to Slack: an agent inherits the permissions and admin controls of the channel it works in, with no separate access model for developers to build and nothing new for IT to configure. A person can approve each high-stakes change, and the record of what the agent did remains searchable after the channel is archived.
Slack illustrates the model with a production alert at 2:00 a.m., in which a custom observability agent opens a code channel, pulls in the relevant logs, and begins work on a fix while on-call engineers read along and redirect it mid-task. The company said the same pattern applies to bug triage and to DevOps tasks such as configuration changes or rollbacks.
How the API Works
Slack’s developer documentation states that apps control a code channel’s title, status, context bar, and view tabs through two API method families. The agents.sessions.* methods are unified across code channels and session threads, with a thread timestamp parameter selecting the session type, and they require the chat:write scope. The agents.conversations.* methods manage code-channel-specific tasks and require the code_channels:manage scope.
Documented agents.conversations.* methods include create, archive (which can optionally record a summary), setProperties, setCommands, setView (supporting html, diff, block_kit, or canvas views), listViews, removeView, getCanvas, and setCanvasContent.
Apps enable code channels by setting features.code_channels.enabled to true in the app manifest, with an optional slash_command_url. When a user mentions the app, it receives an app_mention event and decides whether to create a dedicated code channel or reply in place. The create call takes the origin channel and message timestamp; Slack then creates the channel, matches its privacy setting, and invites the bot automatically.
Under the documented authorization model, the caller must be the agent bot assigned to the channel or a member of the channel, with calls otherwise returning not_agent_channel or not_authorized errors. Code channels are designed to be semi-ephemeral (one channel per task, archived when the session finishes), and once archived a channel and its history remain viewable, searchable, and able to be reopened.
Upcoming Tools and How to Start
Slack said improvements to the pull-request experience are available soon: GitHub users will be able to request reviews in Slack, comments will sync bi-directionally between Slack and GitHub, and a merge prompt will appear in the code channel once a pull request is approved and tests pass. An enhanced Agents & Tools tab is also listed as available soon, offering a bird’s-eye view of agent conversations and code channels with status, channel membership, and recent context, plus the ability to browse public code channels.
Slack outlined three ways to start: read the documentation and add the API to an agent manifest, submit an agent to the Slack Marketplace, or try existing Slack Code agents in the Marketplace, which include Claude, Devin, GitHub Copilot, and Vercel.
Auto-fetched and translated by AI Atlas. All rights belong to the original author.