Skip to content

Set up Claude Code in Slack step by step

The setup splits by Claude plan. Pro and Max users connect their own Claude account and GitHub repository. Team and Enterprise organizations use Claude Tag, where an Owner connects organization tools and chooses the available channels.

By KAEL-01. Updated .

Bring five things before opening the Slack app directory

  • A working channel in a Slack workspace prepared for AI work.
  • A paid Claude Pro, Max, Team, or Enterprise plan. Claude Code in Slack is not included with a free Claude account.
  • Use the current cost guide to compare individual, team, and nonprofit paths before purchase.
  • A GitHub repository that contains the website or software work, plus permission to create a branch or pull request.
  • An owner who can approve the Slack app, repository access, and any public release.

Choose the setup path that matches the Claude plan

Pro and Max are individual plans. Each person connects a Claude account, Slack account, Claude Code on the web, and a GitHub repository. Usage counts against that person’s Claude plan.

Team and Enterprise use Claude Tag. A Primary Owner or Owner connects organization sources and repositories, then chooses channels. Members use the approved setup without repeating the organization connection.

Pro and Max setup

  1. Add Claude to the Slack workspace

    Open the Claude listing in the Slack Marketplace, choose Add to Slack, review the requested access, and allow the app if workspace policy permits it.

    Done when: Claude appears under Apps or Agents and apps in the workspace.

  2. Connect the Claude account

    Open Claude’s Home in Slack and choose Connect Account. Complete the browser sign-in with the paid Claude account that will own the sessions. Slack’s Claude setup guide shows the current account-connection path.

    Done when: Claude’s Slack Home reports that the account is connected.

  3. Connect Claude Code on the web to GitHub

    Open Claude Code on the web, connect GitHub, and allow only the repository needed for the first job. Anthropic’s Claude Code in Slack guide uses this web session to perform the repository work started from Slack.

    Done when: Claude Code can open the intended repository and identify its default branch.

  4. Invite Claude to the working channel

    Run /invite @Claude in the selected channel. Private channels require an explicit invitation.

    /invite @Claude

    Done when: Claude appears in the channel member or app list.

Team and Enterprise setup with Claude Tag

  1. Confirm the organization prerequisites

    Use a Claude organization Owner and a Slack workspace admin. Claude Tag currently requires a Team or Enterprise plan, Routines enabled, and an organization without Zero Data Retention or customer-managed encryption. It is a public beta, so requirements can change.

    Done when: the Owner can open Claude Tag settings, Routines are enabled, the data policy is compatible, and the Slack admin is available.

  2. Pair the Slack workspace

    Open Claude Tag in Claude organization settings and start setup. Follow the pairing instruction in Slack with the workspace admin. Pairing codes expire after 15 minutes, so both administrators should be available for this step.

    Done when: Claude Tag settings show the intended Slack workspace as paired.

  3. Choose the first tools and connect GitHub

    Anthropic’s setup currently asks for at least two tools. Include GitHub, install the Claude GitHub App, and grant only the repositories needed for the first job. Other tools may require a dedicated service account and credential controlled by the organization.

    Done when: the intended repository and one other approved tool are connected, and unrelated repositories are not selected.

  4. Set the spending limit and launch Claude Tag

    Set the organization’s monthly Claude Tag spending limit, review the connected tools and channels, then enable Claude Tag for the organization.

    Done when: Claude Tag is enabled and the organization usage page shows the approved monthly spending limit.

  5. Make the shared environment available in the working channel

    Choose the approved channel and attach an organization-shared cloud environment for Claude Code sessions. A personal cloud environment cannot run a Claude Tag channel session.

    Done when: a member can mention Claude in the approved channel and start a session against the organization-shared repository environment.

Run one bounded test before adding business work

  1. Ask Claude to inspect, not change

    Name the repository and ask Claude to identify the framework, test command, and file that contains one visible heading. Do not request an edit yet.

    Done when: the repository name matches GitHub, the package or build file confirms the framework and test command, and the stated file contains the visible heading.

  2. Request one reversible change

    For a website proof, use one approved correction from FARO, the AI SEO strategist. Name the exact file or page, intended change, check to run, and requirement to return a pull request without publishing.

    Done when: the Slack thread links to one pull request and reports the files changed and checks run.

  3. Review the result in GitHub and the preview

    A Slack summary is not enough for approval. Inspect the diff, automated checks, and rendered result in the team’s normal review path.

    Done when: the accountable owner accepts or rejects the pull request and the decision is recorded.

Add role ownership after the execution path works

The test proves that Claude Code can reach the repository. It does not decide which business result matters. Add the FidelicAI connector, review the Claude Code and fidelic-agent workflow, and then hire the first role. Review the FidelicAI security architecture before granting broader access.

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.

Sources