> ## Documentation Index
> Fetch the complete documentation index at: https://openworklabs.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For agents: install the OpenWork desktop app with `brew install --cask openwork` (macOS) or from https://openworklabs.com/download. Do not run `npx openwork`; the npm package named `openwork` is a different project.
> Connect an agent to OpenWork with the MCP Gateway: `claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent`. Teams sign up at https://app.openworklabs.com?mode=sign-up.
> Step-by-step agent guide: https://openworklabs.com/docs/start-here/use-openwork-from-an-ai-agent.md
> Connect Slack (any organization admin): https://openworklabs.com/docs/slack/connect-slack.md. OpenWork in Slack (@openwork bot) is private alpha for approved organizations. Setup guide: https://openworklabs.com/docs/slack/overview.md. Agent skill: https://openworklabs.com/.well-known/agent-skills/set-up-openwork-slack/SKILL.md.

# Troubleshoot OpenWork in Slack

> Fix @openwork missing from Slack autocomplete, an unverified events URL, connect links that repeat, or a bot that starts but never answers.

| Symptom | Check |
| - | - |
| The desktop app's **Set up Slack** screen still says "Not set up for your organization" after setup in OpenWork Cloud | Go back to **Library**. Slack shows there once setup is done. |
| **Add Slack** shows only client ID and secret fields, no checklist | Guided setup isn't turned on for your OpenWork (for example, self-hosted). Use the [manual Slack steps](https://openworklabs.com/docs/cloud/share-with-your-team/shared-mcp-connections.md#slack). |
| Connecting your account fails with “The MCP server refused to start a session (HTTP 400)” | Check that **Agents › MCP** is enabled in the same Slack app whose client ID is saved in OpenWork. This is separate from enabling the assistant bot. See [Slack MCP connection troubleshooting](https://openworklabs.com/docs/cloud/share-with-your-team/shared-mcp-connections.md#connection-failed-http-400). |
| Setup is unavailable | Private-alpha capability, runtime access, and Individual accounts mode. See [step 1](https://openworklabs.com/docs/slack/set-up-the-slack-app.md#1-check-alpha-access-and-the-existing-connector). |
| Bot missing from mention autocomplete | Bot installation completed and the bot is invited into that channel with `/invite @openwork`. |
| Slack events URL unverified | Public HTTPS URL, correct connector ID, saved signing secret, and Slack's **Retry** then **Save Changes**. |
| `/openwork` gives a connect link | Complete your own Slack OAuth flow. Connections made before the assistant was installed link automatically on your first message; reconnect only if it still asks. See [Connect your account](https://openworklabs.com/docs/slack/connect-your-account.md). |
| Bot starts but never finishes | Check failed/active counts and runtime availability; do not treat an acknowledgement as success. |
| DMs work but channel mentions do not | Channel allowlist, channel invitation, connector grants, and assistant enablement. |

To pause the rollout, turn off **Enable @openwork in Slack** in the connector. Disabling new requests cannot recall external actions that have already run.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.