Slack

OpenCode is an open source AI coding agent. The OpenCode app brings it into Slack, and brings Slack into OpenCode.

In OpenCode

• Each member can connect their own Slack account from OpenCode Console. Their OpenCode can then search and read the conversations, files and canvases they can already see, and post as them, through Slack's MCP server.
• OpenCode only sees what the member could see in Slack, and workspace admins choose who can connect.

In Slack

• 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.
• Approve or deny what it asks to do, right from its message.

• An OpenCode Console workspace with Integrations. Integrations is in early access: if your workspace doesn't have an Integrations tab yet, email help@anoma.ly.
• An owner or admin of the workspace to add Slack. Members can't add integrations.
• A Slack account for each member who connects, in a Slack workspace whose admins allow the OpenCode app.
• Each member's OpenCode signed in to Console, as Connect OpenCode in Console shows.

If you're an owner or admin and your workspace doesn't show Integrations yet, email help@anoma.ly to have it turned on.

1. An owner or admin opens Integrations in Console and clicks Connect on Slack, or uses Connect Slack at the top of this page.
2. They don't choose whose accounts it uses: each member connects their own Slack account, and there's no shared workspace account.
3. They sign in to Slack and approve the access OpenCode asks for.
4. Each member then opens Slack in Integrations and clicks Connect to sign in. If their OpenCode tries Slack before they have, it tells them where to connect.

Once a member connects, Slack appears in their OpenCode. Anyone can leave it out of their own OpenCode with Include in your OpenCode config on its page.

Console stores each sign-in's access and refresh tokens, encrypted, and sends them only to Slack. It doesn't look up your Slack profile. It also records the tools Slack lists (their names, descriptions and inputs) and its instructions for agents, so admins can review them.

Ask OpenCode in your own words. For example:

• Summarize what #incidents said about last night's outage.
• Find the thread where we agreed on the retry policy and sum up what we decided.
• Post a short summary of this change in #releases.

OpenCode reaches Slack through Console, which adds your credentials on the way, so your OpenCode never holds them. Results go back to your OpenCode, which passes them to the model it's using. Console logs each call (the integration, the tool, whether it was allowed and whose account it used) but never what was sent or returned.

Owners and admins review Slack's tools on its page in Integrations and can turn any of them off. By default, a tool Slack adds or changes stays hidden from OpenCode until an owner or admin approves it. Rules in Controls decide who can use Slack, and can limit it to tools that only read.

The same app brings the OpenCode agent into your Slack workspace. An owner or admin installs it from Integrations › Slack Bot in Console with Add to Slack. People in a thread don't need a Console account: the workspace pays for the agent's model use.

The Slack Bot is in early access too. To take the agent out of Console, an owner or admin clicks Disconnect Slack on its page, which deletes the installation and its bot token from Console. The app stays in your Slack workspace until it's removed in Slack, as described below.

Disconnect your account

Open Slack in Integrations and click Disconnect. Console deletes its copy of your Slack tokens and any sign-in you had started. When someone leaves the workspace or is removed from it, Console deletes the accounts they connected for themselves the same way.

Remove Slack from the workspace

An owner or admin opens Slack in Integrations and chooses Remove… from the … menu. Console deletes Slack from the workspace with every account connected to it, the tools it recorded, its settings and members' choices. Disable… in the same menu turns it off for everyone instead and keeps all of that until it's turned back on.

Remove the app in Slack

Disconnecting only removes what Console holds. To end OpenCode's access on Slack's side too: In Slack, open Tools & settings › Manage apps, select OpenCode under Installed Apps, and choose Remove App on its Configuration tab. To end one member's access only, revoke their authorization on the same tab.

If you remove the app there first, Console shows your account as needing reconnecting once it's next used, and keeps the encrypted tokens until you disconnect or an admin removes Slack.

• Console keeps each Slack sign-in's tokens encrypted and sends them only to Slack, never to OpenCode.
• It records the tools and instructions Slack lists, so admins can review them. It doesn't look up your profile.
• It logs each tool call (who made it, the integration, the tool, the outcome and timing) for 30 days, never what was sent or returned, and doesn't keep tool results.
• Results reach your OpenCode and the model it's using.

The privacy policy explains how Anomaly handles personal data, and the terms of service cover using OpenCode. To ask for a copy of your data or for it to be deleted, email help@anoma.ly.

Email help@anoma.ly. We reply within two business days (Monday to Friday, excluding US holidays), and you don't need an account. The support page covers data requests, security reports and more.