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. Updated .
Match the symptom to the smallest useful check
| 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 connection
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.
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.
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
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.
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.
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.
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, use the checked work-request pattern. If the website itself is uncertain, return to the website readiness guide. The FidelicAI permissions guide covers the separate public connector boundary.
Continue through the Claude hiring path
Each guide answers a separate part of the same decision. The canonical FidelicAI connector page carries the live server address and current public contract.
Give Claude Code a work request that can be checked
Vague Claude Code requests in Slack produce changes that are hard to trust. Use six facts to bound the work, verify it, and keep release with the owner.
Claude Code in Slack for small businesses and nonprofits
Pair Claude Code in Slack with role-specific AI agents that direct approved website changes, check the result, and report to small teams and nonprofits.
Add the FidelicAI connector to Claude Code
Add the public FidelicAI connector to one Claude Code project, verify its read-only tools, and find AI agent roles, rates, limits, and secure hire paths.
Turn an SEO finding into a reviewed site update from Slack
Follow an SEO finding from dated evidence to an approved brief, Claude Code pull request, rendered checks, owner publication, and later FARO verification.