Two-way Slack channel for Claude Code — chat from Slack DMs and channels via Socket Mode

2 Skills

5 MCP Tools

MIT License

$undefined undefined/undefined Pricing

Installation

Open Claude Code and run this command:

/plugin install slack-channel@claude-code-plugins-plus

Use --global to install for all projects, or --project for current project only.

What It Does

The Slack-native governance substrate for Claude Code — the kernel other governance tooling builds on. Humans, Claude Code sessions, and peer agents converse safely in shared channels: every tool call passes through a declarative, tier-aware policy engine; every decision lands in a hash-chained, Ed25519-signed audit journal you can verify offline. Per-thread session isolation, identity-aware permission gates, operator admin commands with cross-channel approval, peer-bot loop control, and defense-in-depth against prompt injection. The policy/journal/relay kernel here is the substrate that the companion agent-governance-plane (AGP) vendors for cross-runtime governance.

![CI](https://github.com/jeremylongshore/claude-code-slack-channel/actions/workflows/ci.yml)

![License: Apache 2.0](LICENSE)

![OpenSSF Scorecard](https://scorecard.dev/viewer/?uri=github.com/jeremylongshore/claude-code-slack-channel)

Links: Roadmap & Scope · Gist One-Pager · GitHub Pages · Release Notes

> Research Preview — Channels require Claude Code v2.1.80+ and claude.ai login.

Skills (4)

access SKILL.md View full skill →

Manage Slack channel access control — pairing, allowlist, channel opt-in.

[ReadWriteEdit]

/slack-channel:access

Manage who can reach your Claude Code session through Slack.

Usage


/slack-channel:access pair <code>                          # Approve a pending pairing
/slack-channel:access policy <pairing|allowlist|disabled>   # Set DM policy
/slack-channel:access add <slack_user_id>                   # Add user to allowlist
/slack-channel:access remove <slack_user_id>                # Remove from allowlist
/slack-channel:access channel <channel_id> [--mention] [--allow <user_id,...>]  # Opt in a channel
/slack-channel:access channel remove <channel_id>           # Remove channel opt-in
/slack-channel:access status                                # Show current config

State File

~/.claude/channels/slack/access.json

Instructions

Parse $ARGUMENTS and execute the matching subcommand:

`pair`



Load access.json
Find the pending entry matching  (case-insensitive)

If not found or expired: show "No pending pairing with that code."
If found:


Add entry.senderId to allowFrom
Remove the pending entry
Save access.json with permissions 0o600
Show: Approved! User  can now DM this session.
Send a confirmation message to the user in Slack (via the reply tool if the MCP server is running)

policy 

Validate mode is one of: pairing, allowlist, disabled
Update dmPolicy in access.json
Save with 0o600
Show the new policy and what it means:


pairing: New DMs get a code to approve (default)
allowlist: Only pre-approved users can DM
disabled: No DMs accepted

add 

Add the Slack user ID to allowFrom (deduplicate)
Save with 0o600
Show confirmation

remove 

Remove from allowFrom
Also remove from any channel-level allowFrom lists
Save with 0o600
Show confirmation

channel  [--mention] [--allow ]

Parse options:


--mention: require @mention to trigger (default: false)
--allow : restrict to specific users in that channel


Add/update channels[channel_id] in access.json
Save with 0o600
Show the channel policy

channel remove 

Delete channels[channel_id]
Save with 0o600


                
                  
                  
                  configure
                  SKILL.md
                  View full skill →
                
                
                  Configure Slack channel tokens (bot token + app-level token).
                  
                      [ReadWriteBash(cmd:chmod)"]
                    
                
                
                  /slack-channel:configure
Configure the Slack channel with your bot token and app-level token.
Usage

/slack-channel:configure <xoxb-bot-token> <xapp-app-token>

Instructions

Parse the two arguments from $ARGUMENTS:


First token must start with xoxb- (Bot User OAuth Token)
Second token must start with xapp- (App-Level Token)


If either token is missing or has the wrong prefix, show this error and stop:


   Error: Two tokens required.
     - Bot token (starts with xoxb-) from OAuth & Permissions
     - App token (starts with xapp-) from Socket Mode settings

   Usage: /slack-channel:configure xoxb-... xapp-...


Create the state directory if it doesn't exist:


   ~/.claude/channels/slack/


Write the .env file at ~/.claude/channels/slack/.env:


   SLACK_BOT_TOKEN=<bot-token>
   SLACK_APP_TOKEN=<app-token>


Set file permissions to owner-only:


   chmod 600 ~/.claude/channels/slack/.env


Confirm success:


   Slack channel configured.

   Start Claude with the Slack channel:
     claude --channels plugin:slack-channel@claude-code-plugins

   Or for development:
     claude --dangerously-load-development-channels server:slack

Security

Never echo the tokens back in the confirmation message
Never log tokens to stdout or any file other than .env
Always set 0o600 permissions on the .env file


                
                  
                  
                  install
                  SKILL.md
                  View full skill →
                
                
                  CCSC lifecycle command center — fresh install walkthrough, health doctor, verify round-trip, auto-repair, Slack app manifest export, reset, tour, and uninstall.
                  
                      [ReadWriteEditBashWebFetch]
                    
                
                
                  /slack-channel:install
CCSC lifecycle command center. One skill, eight modes — fresh install through
teardown. No subcommand defaults to the full install walkthrough.

/slack-channel:install [mode]

Modes:
  install     full fresh-clone walkthrough (default)        ← new user starts here
  doctor      run a health check against an existing install
  verify      run the verification round-trip only
  repair      auto-fix common issues surfaced by doctor
  manifest    export a Slack app manifest.json (one-click import — saves 10 min of scope clicking)
  reset       wipe state and restart from Step 3 (keeps Slack app)
  tour        explain CCSC features without installing (for evaluators)
  uninstall   clean teardown — remove state dir, optionally guide Slack app deletion

This skill orchestrates. It delegates token configuration to
/slack-channel:configure and pairing to /slack-channel:access pair —
do not re-implement those.
Mode dispatch
Parse the first word of $ARGUMENTS. If empty or install, run install.
Otherwise dispatch to the matching mode. Unknown modes show the help block
above and exit.

Mode: install (default)
End-to-end fresh-clone walkthrough.

┌────────────────────────────────────────────────────────┐
│ 0. Prerequisite check    (Bun, Claude Code, claude.ai) │
│ 1. Slack app creation    (or skip → /install manifest) │
│ 2. Add bot to channel    ← THE silent killer step      │
│ 3. Configure tokens      → /slack-channel:configure    │
│ 4. Start MCP server                                    │
│ 5. Pair account          → /slack-channel:access pair  │
│ 6. Verification round-trip                             │
│ 7. Offer optional next steps                           │
└────────────────────────────────────────────────────────┘

Step 0: Prerequisite check
See references/prerequisites.md for the
exact commands and recovery paths. Three checks in order:

Bun ≥ 1.0: bun --version. If missing, show install command (Node fallback is fine — see prerequisites doc).
Claude Code ≥ v2.1.80: claude --version. Older versions cannot load Channels.
claude.ai login (NOT API-key-only): Channels is Research Preview and rejects pure API-key auth. If ANTHROPICAPIKEY is set but no claude.ai session exists, instruct claude login.

If any check fails, give the recovery command, wait for the user to fix, then re-check. Don't proceed with broken prerequisites.
Step 1: Slack app creation
Two paths: offer the manifest path (faster) or walk the ma


                
                  
                  
                  policy
                  SKILL.md
                  View full skill →
                
                
                  Author MCP tool-call policy rules without hand-editing access.
                  
                      [ReadWriteEditBash(cmd:bun)Bash(cmd:chmod)"]
                    
                
                
                  /slack-channel:policy
Author, lint, and remove policy rules under access.json's top-level policy field.
The evaluator (evaluate() in policy.ts) is the veto layer for every MCP tool
call — this skill is the ergonomic front door to authoring rules without opening
access.json in a text editor.
See ACCESS.md §Policy schema for the full
rule shape and semantics. This skill does not replace the hand-edit path; it
complements it.
Usage

/slack-channel:policy list
/slack-channel:policy lint
/slack-channel:policy add <id> <effect> <json-match> [--reason "..."] [--ttl-ms N] [--approvers N] [--priority N]
/slack-channel:policy remove <id>

Effect is one of autoapprove, deny, requireapproval.
json-match is a JSON object literal for the match field — e.g.
'{"tool":"read_file","pathPrefix":"/workspace/docs"}'. At least one field
must be populated; the validator rejects empty matches.
Options by effect

Effect
Required
Optional


auto_approve
—
--priority


deny
--reason "…" (1-200)
--priority


require_approval
—
--ttl-ms, --approvers, --priority


Defaults: priority=100, ttl-ms=300000 (5 min), approvers=1.
State file
~/.claude/channels/slack/access.json — the policy field is a JSON array.
A missing or empty array means "no authored rules" and is valid.
Instructions
Parse $ARGUMENTS and execute the matching subcommand. Before every write, run
the validator script. Exit cleanly without writing if validation fails.
list

Read ~/.claude/channels/slack/access.json
If the policy field is missing or empty, print No policy rules authored. Evaluator applies defaults — see ACCESS.md §Default-branch behavior. and return.
Otherwise, print a table: id | effect | match summary | extras.


match summary — join populated fields: tool=read_file pathPrefix=/workspace (omit undefined fields).
extras — for deny show reason=…; for require_approval show ttlMs=… approvers=….

lint

Run: bun script



      
      
          How It Works
          For AI-assisted setup: run /slack-channel:install and your AI assistant will walk you through every step below. The install skill also supports doctor (health check), verify (round-trip test), repair (auto-fix), manifest (one-click Slack-app import), reset, tour, and uninstall modes — see skills/install/SKILL.md.
Prerequisites
Before step 1, confirm you have:

Bun ≥ 1.0 — install with curl -fsSL https://bun.sh/install | bash. Node.js / Docker fallbacks are documented in Option B / Option C below.
Claude Code ≥ v2.1.80 — see https://docs.claude.com/claude-code/install for upgrade.
claude.ai login — this is a Research Preview constraint. API-key-only auth (ANTHROPICAPIKEY set with no claude.ai session) does NOT work for Channels. Run claude login to complete the browser flow.

1. Create a Slack App

Go to api.slack.com/apps → Create New App → From scratch
Socket Mode: Settings → Socket Mode → Enable → Generate App-Level Token (xapp-...) with connections:write scope
Event Subscriptions: Enable → Subscribe to bot events:


message.im — DMs
message.channels — public channels
message.groups — private channels
app_mention — @ mentions


Bot Token Scopes (OAuth & Permissions):


chat:write — send messages
channels:history — read public channels
groups:history — read private channels
im:history — read DMs
reactions:write — add reactions
files:read — download shared files
files:write — upload files
users:read — resolve display names


Install to Workspace → Copy Bot Token (xoxb-...)

2. Configure Tokens

/slack-channel:configure xoxb-your-bot-token xapp-your-app-token

3. Run
Pick your runtime:

Option A: Bun (recommended)

bun install
claude --channels plugin:slack-channel@claude-code-plugins


Option B: Node.js / npx
...

        


      
      

      
      

      
      
  Ready to use slack-channel?
  
    
    
        
        View on GitHub
      
  




      
      
          Related Plugins
          
            
  ai-experiment-logger
  Track and analyze AI experiments with a web dashboard and MCP tools
  /plugin install ai-experiment-logger@claude-code-plugins-plus
  

  conversational-api-debugger
  Debug REST API failures using OpenAPI specs and HTTP logs (HAR) - root cause analysis with cURL generation
  /plugin install conversational-api-debugger@claude-code-plugins-plus
  

  design-to-code
  Convert Figma designs and screenshots to React/Svelte/Vue components with built-in accessibility
  /plugin install design-to-code@claude-code-plugins-plus
  

  domain-memory-agent
  Knowledge base with TF-IDF semantic search and extractive summarization - no ML dependencies required
  /plugin install domain-memory-agent@claude-code-plugins-plus
  

  lumera-agent-memory
  Durable agent memory with Cascade object storage, client-side encryption, and local full-text search index. Persists agent context across sessions.
  /plugin install lumera-agent-memory@claude-code-plugins-plus
  

  project-health-auditor
  Multi-dimensional code health analysis with complexity, churn, and test coverage - identifies technical debt hot spots
  /plugin install project-health-auditor@claude-code-plugins-plus
  

          
        

      
      
          Tags
          
            slackchannelmcpsocket-modechatopsclaude-code

Effect	Required	Optional
`auto_approve`	—	`--priority`
`deny`	`--reason "…"` (1-200)	`--priority`
`require_approval`	—	`--ttl-ms`, `--approvers`, `--priority`

slack-channel

Installation

What It Does

Skills (4)

/slack-channel:access

Usage

State File

Instructions

`pair`

`policy`

`add`

`remove`

`channel [--mention] [--allow ]`

`channel remove`

/slack-channel:configure

Usage

Instructions

Security

/slack-channel:install

Mode dispatch

Mode: `install` (default)

Step 0: Prerequisite check

Step 1: Slack app creation

/slack-channel:policy

Usage

Options by effect

State file

Instructions

`list`

`lint`

How It Works

Prerequisites

1. Create a Slack App

2. Configure Tokens

3. Run

Option A: Bun (recommended)

Option B: Node.js / npx

Ready to use slack-channel?

Related Plugins