--- title: How do I connect Slack to the Brain? question: connect slack to brain area: integrations order: 11 surface: desktop audience: beginner visibility: public keywords: [slack, message brain, direct message, mention, listening, xapp, xoxb, allowed people, app token, connect] related: [integrations-overview, talk-to-the-brain, what-is-the-brain] updated: 2026-09-15 --- # How do I connect Slack to the Brain? In Codus **0.2.184 or later**, open **Settings → Integrations → Slack**, connect an app in your workspace and choose who may message it. With **Brain 1 using Claude** and Codus running, those people can send the app a direct message or mention it in a channel. The Brain answers in the Slack conversation that asked. Other Brain providers cannot receive Slack work in this release. ## Before you start - You need permission to create and install an app in your Slack workspace. Your workspace may require approval before installation. - Keep Codus open on an awake computer with an internet connection. Slack messages cannot start work on a computer that is asleep or has Codus closed. - Set **Brain 1** to **Claude** in Codus, open it and wait for it to finish starting. Keep it running while you use Slack. Replies use that Brain's selected AI account and its usage limits. - Treat the keys copied from Slack like passwords. Paste them into the Slack connection card, not into a conversation. ## Create your app with the guided setup 1. Open **Settings → Integrations**, find **Slack**, then click **Open Slack app settings**. It opens [your Slack apps](https://api.slack.com/apps). 2. Below the list of apps, find **Your App Configuration Tokens** and click **Generate Token**. Choose your workspace. Copy the **Access Token** and **Refresh Token** into the matching fields in Codus. Slack documents these temporary keys in its [app configuration guide](https://docs.slack.dev/app-manifests/configuring-apps-with-app-manifests/). 3. Click **Create the app**. Codus creates the app and opens its installation page. If that page does not open, use **Open the install page**. 4. On **OAuth & Permissions** in Slack, install the app into your workspace and approve the requested permissions. Copy its **Bot User OAuth Token**, beginning `xoxb-`, into Codus's sending-key field. 5. In the app's **Basic Information**, find **App-Level Tokens** and click **Generate Token and Scopes**. Give it a name, add **connections:write**, generate it and copy the value beginning `xapp-` into the listening-key field. Slack's [setup guide](https://docs.slack.dev/tools/bolt-js/creating-an-app/) explains this separate listening key. 6. Click **Connect**. The card shows **Connected** and your workspace name when the sending key works. Receiving messages also needs the listening connection described below. 7. Under the people picker, select each person allowed to send work. An empty list permits nobody. Then send the app a test direct message in Slack. ## I already have a Slack app Open **I already have a Slack app** on the card. Follow its listed permissions and event settings in your app's Slack settings, including **Socket Mode**, then install the updated app into your workspace. Paste its sending and listening keys and click **Connect**. Select the permitted people after connecting. If Slack says messages to the app are disabled, use **Update the app in Slack** on the connected card. Follow any instruction to reinstall the app, then try another message. ## Connected, but not listening The sending key and listening key do different jobs. **Connected** by itself does not mean incoming messages can reach the Brain. If you skipped the `xapp-` key, create it in your app's **Basic Information → App-Level Tokens**, with **connections:write**, then paste it into the connected card and click **Turn on listening**. You do not need to disconnect first. Save the key when Slack displays it; if you cannot retrieve it later, generate a new one. If the card reports a rejected listening key, replace it with a valid key from the same app. If it says it is reconnecting, wait for a listening status before sending a new message. ## Who can send work? Only the people selected in the Slack card. If someone messages before they are allowed, the card can show their name with **Allow them**. Add only people you intend to give access. If the people picker cannot load, use the member-ID entry shown on the card; Slack exposes a person's member ID in the menu on their profile. Slack requests can ask about Brain status, tasks, plans and notes. They have limited, read-only access. They cannot run terminal commands, read or change files, build or deploy a project, install software, use connected accounts or control a browser or the desktop. Continue those actions at the computer. There is no unlock button for remote work, and replying “yes” in Slack does not lift a restriction. Requests wait for their turn when the Brain is busy. Each answer goes to the thread that requested it; another person's request does not become the destination for your reply. ## How do I know it worked? The card shows your connected workspace and says it is listening. Your name is selected in the allowed-people list. A test direct message or channel mention receives its answer in the same Slack thread. If there is no answer, check all three conditions, confirm Brain 1 is running with Claude, and read any displayed error. If Codus says it could not check which actions the request is allowed to take, restart Codus, open Brain 1 and send the request again. If Codus restarted while an answer was in progress, resend that request too. ## Disconnect Click **Disconnect** and confirm. Codus forgets the connection keys and stops receiving messages. Your Slack app and channels remain in Slack; you can reconnect later.