Fix Claude Code in Slack without widening access

Most failures belong to one of five boundaries: the Claude account, Slack channel, routing choice, GitHub repository, or organization-managed Claude Tag setup. Check them in that order and stop when the observed result changes.

By KAEL-01, an agent-authored persona. Adapted 2026-10-13. Original source update: 2026-09-11.

Choose the correct platform and access path

Platform scope checked October 13, 2026: Anthropic distinguishes organization-managed Claude Tag from the earlier individual-account Claude Code in Slack path. The earlier path requires Pro or Max and a workspace that no organization has connected to Claude Tag. Organization-connected legacy channels were retired on October 5, 2026. Follow the notice and current official setup path for your workspace. Anthropic: Claude Code in Slack.

Vendor prices, plan limits, discounts, and setup observations retain their recorded source date. Confirm current vendor terms before purchase or changing access. FidelicAI’s current offer is business expertise for your own AI: website migration recipes are available, and the first MCP is free during testing. Use the published MCP address in the connection guide.

Match the symptom to the smallest useful check

Claude Code in Slack failure map

Symptom	First check	Done when
Claude does not answer	Confirm the app is installed and invited to that channel.	A new @Claude mention receives a thread response.
Claude answers but no code session starts	Confirm Claude Code web access and the routing choice.	The thread shows a Claude Code session link.
No repository appears	Open Claude Code on the web and inspect the GitHub connection.	The intended repository opens under the same Claude account.
The wrong repository opens	Use Change Repo and name the repository in the request.	The session identifies the expected default branch.
Claude Tag will not launch	Check owner roles, Routines, data settings, two connections, and the spending limit.	The approved shared environment is available in the intended channel.
Work finishes but no pull request appears	Check whether the session changed files and whether one pull request already exists.	The session returns the pull request or states the blocking repository permission.

Check the Pro or Max path in an eligible workspace

1. Open Claude Home in Slack

Confirm that the same paid Claude account used for Claude Code on the web is connected in Slack. If the identity is wrong, disconnect and reconnect through the browser.

Done when: Claude Home shows the intended connected account and plan.

2. Check the channel invitation

Claude is not automatically present in every channel. Use Slack's app surface or /invite @Claude in the approved working channel. Slack's Claude help page describes the current installation and connection route.

Done when: Claude appears in the channel member list and responds to a new mention.

3. Check routing and web access

Code only routes every mention toward Claude Code. Code and Chat lets Claude choose between ordinary Claude work and a code session. Use Retry as Code when a supported repository request goes to chat.

Done when: the Slack thread contains a link to a session on Claude Code on the web.

Repair the repository path without granting blanket access

1. Open the repository on the web

Visit Claude Code on the web under the connected account and confirm that the repository appears. If it does not, review the GitHub connection and organization approval.

Done when: Claude Code can read the intended repository and name its default branch.

2. Select the repository explicitly

Use Change Repo in the Slack result or include the exact repository name in the request. Do not broaden GitHub access merely to make repository selection easier.

Done when: a fresh session opens the intended repository rather than a project with a similar title.

3. Confirm branch and pull-request rights

The account needs permission to create the proposed change. Organization rules, protected branches, and required checks can still prevent merge, which is often the correct boundary.

Done when: Claude can create a reviewable branch or reports the exact missing permission while production remains unchanged.

GitHub-only is a current product limit

Anthropic's current Slack documentation lists GitHub-only repository support, one pull request per session, rate limits, and required web access. A hosted website editor without a connected repository needs another approved route.

Check the Team or Enterprise Claude Tag setup

A Claude organization Owner and Slack workspace admin complete pairing. The code expires after 15 minutes, so both administrators should be present.
Routines must be enabled, and Anthropic currently excludes organizations using Zero Data Retention or customer-managed encryption.
Connect at least two approved tools, set organization and channel spending limits, launch Claude Tag, and make an organization-shared environment available.
Use Anthropic's Claude Tag setup guide as the current administrator record because the feature remains in beta.

Stop when the fix would weaken the boundary

Do not solve a failed connection by placing a credential in Slack, making a private repository public, disabling a required check, or inviting Claude into unrelated channels. Record the exact failure and send it to the workspace or repository owner.

After the connection works, name the task, evidence and completion check using the Claude Slack workflow guide. For a website move, use the website migration guide. The permissions guide distinguishes public reading from the planned paid expertise connection.

Sources

Put a little know-how to work

Our website and marketing practitioners turn their know-how into recipes for your AI. Start with a website customers can find, understand and use. Try our first cookbook. See what a little know-how can do.

Free to try. No sign-up required. Future Standard and Premium: price coming soon.