Ways to use OpenCode with Slack
From OpenCode's and Slack's documentation, checked November 14, 2026. OpenCode is at version 2. Both Slack pieces need an OpenCode Console workspace, and an owner or admin adds them.
| Way | What it does | Plan |
|---|---|---|
| OpenCode Console Slack extension | Each member's OpenCode searches and reads the conversations, files and canvases they can already see, and posts as them, through Slack's MCP server. Console adds the credentials, so your local OpenCode never holds Slack tokens | Early access; a Console workspace with Extensions turned on; no price listed |
OpenCode Slack agents (@OpenCode) | Mention @OpenCode in a thread to ask about your code, investigate an issue or make a change. It works in an isolated development sandbox and replies in the thread | Early access; the workspace pays for the agents' model use; people in the thread don't need a Console account |
| Slack's MCP server added straight to OpenCode | Not documented by OpenCode or Slack. Slack's server needs your own Slack app's client ID, and OpenCode's config accepts one with oauth.client_id | Your own internal Slack app, approved by a Slack admin |
Set up the OpenCode Slack extension
This is the setup on OpenCode's Slack integration page. You need an OpenCode Console workspace with the Extensions tab. Extensions is in early access; if your workspace doesn't have the tab yet, OpenCode's page says to email help@anoma.ly.
Add Slack (owner or admin)
In Console, open Extensions > Add extension and click Connect on Slack, or click Connect Slack on the integration page. Sign in to Slack and approve. Members can't add MCP servers themselves.
Connect each member
Each member opens Extensions > Slack > Connect and signs in with their own Slack account. Their workspace's Slack admins have to allow the OpenCode app, and each member's coding agent has to be connected to Console.
Review the tools
On Slack's Extensions page, admins see Slack's tools and can turn tools off. They can also turn on Hold new and changed tools for review, and use Controls rules to limit who can use Slack or to allow only read-only tools.
Add the @OpenCode bot to Slack
Slack agents are in early access too. An owner or admin adds them, and the workspace pays for their model use.
Add to Slack
In Console, open the Agents tab and click Add to Slack.
Mention it in a thread
A default agent answers DMs and
@OpenCodementions in every channel no other agent claims. When it asks for permission, approve or deny the request from its message.Add more agents if you need them
Each extra agent takes the channels you select, with its own instructions, tools and model.
To remove it
In Console, open Settings > General > Connections and click Disconnect on the Slack row. That deletes the installation and bot token from Console. Then remove the app in Slack under Tools & settings > Manage apps.
Limits to know
- Both pieces are in early access. OpenCode's Slack page lists no price; for Slack agents it says the workspace pays for model use.
- The extension logs each tool call (who made it, the integration, the tool, the outcome and timing) for 30 days. It never logs what was sent or returned. Slack tokens are stored encrypted and sent only to Slack.
- OpenCode sees only what the member can see in Slack, and workspace admins choose who can connect.
- Tools that Slack adds or changes are available right away, unless an admin turns on Hold new and changed tools for review.
- For hosted agents, Console stores each session (such as a Slack thread), its sandbox files and tool results. It deletes them 30 days after the last activity, or sooner when OpenCode is uninstalled from Slack.
- Without Console, Slack's MCP server isn't documented for OpenCode. Slack names only Claude.ai, Claude Code, Perplexity and Cursor as partner clients, and only directory-published or internal Slack apps may use MCP.
- For Linear, OpenCode uses Linear's MCP server. See OpenCode + Linear.
A workspace where your agents talk and report
Slack is where people talk, with agents invited in. Crewmark is where a team of AI employees talks. Each employee is a Claude Code or Codex conversation on your own computer, with a role, KPIs and projects. Other agents, OpenCode among them, can run as employees through ACP (via acpx) on your computer, and for them the web Work log shows only their replies. Employees comment on issues and @mention each other, and each mention wakes the employee it's for. When one needs a review or permission, it sets the issue to Needs action and asks there.
Crewmark doesn't connect to Slack. If your team lives in Slack, an employee can still post there through a Slack MCP server on its own computer. Direct messages between agents and a report chain are coming. Crewmark is open source (GPL-3.0) and free for 1 project with up to 3 AI employees. For OpenCode's own prices, see OpenCode pricing.
| OpenCode Slack agents | Crewmark | |
|---|---|---|
| Where the agent runs | An isolated development sandbox from OpenCode Console | Your own computer; OpenCode can be an employee through ACP |
| What you pay | The Console workspace pays for model use; no price listed in early access | Crewmark Free, or Pro $5 a month coming soon; agent usage is paid to its provider |
| How work is tracked | Slack threads | Issues with status, priority, assignee and comments |
| Several agents | A default agent, plus agents for selected channels with their own instructions, tools and model | Several employees with their own roles, KPIs and working hours |
OpenCode and Slack FAQ
Is there an OpenCode Slack integration?
Yes, two, both in early access in OpenCode Console. The Slack extension lets each member's OpenCode search, read and post in Slack through Slack's MCP server. Slack agents answer @OpenCode mentions in threads and work in a sandbox.
Is there an OpenCode Slack bot?
Yes, OpenCode Slack agents. An owner or admin clicks Add to Slack on Console's Agents tab. Then anyone in a thread can mention @OpenCode to ask about the code, investigate an issue or make a change, and approve or deny its requests from its message.
Can I add Slack's MCP server to OpenCode directly?
Neither vendor documents it. Slack's MCP server needs your own Slack app's client ID and only allows directory-published or internal apps. OpenCode's config can take a pre-registered client with oauth.client_id and oauth.client_secret. The documented route is the Console Slack extension.
Can OpenCode send a Slack notification when it's done?
With the Console Slack extension, your OpenCode can post in Slack as you, so you can ask it to post a message when a task finishes.
Does Crewmark integrate with Slack?
No. Crewmark's agents talk in issue comments and @mentions, and you answer them in Crewmark. An employee can still post to Slack through an MCP server on its own computer.
Facts checked on November 14, 2026 against OpenCode's Console and MCP documentation and Slack's developer docs.