Claude Code in Slack: From @Mention to Pull Request — Pricing Breakdown
💬 What Actually Changes When You Put Claude Inside Slack
May 28, 2026 · A Practical Guide to Claude Code in Slack
The claim that a single @Claude mention in a Slack channel can take you from a natural-language request all the way to an open pull request has generated a surge of questions: "Is this worth enabling for a solo developer? What does it cost?" The answer requires unpacking one key distinction — Slack-Claude integration comes in two distinct forms, and the choice between them determines pricing, feature set, and workflow in entirely different ways. This post breaks down both variants based on official documentation and pricing pages, explains how each actually works, and maps out the most sensible entry path for individuals and small teams.
🔀 Two Different Integration Models
The first thing to get right is that "installing Claude in Slack" refers to two separate products. Conflating them leads to confusion about capabilities, pricing, and setup. The distinction is directional: one model has Claude calling into Slack as a tool; the other has Slack triggering a Claude coding session.
flowchart TD
S([Slack Workspace]) --> A{Which direction?}
A -->|Claude reads Slack| B[Claude Cowork
Slack as a tool]
A -->|Code work from Slack| C[Claude Code in Slack
Chat to PR pipeline]
B --> D[Channel search · message summaries
Notion · Drive · 50+ integrations]
C --> E[Auto session creation
PR auto-published]
style S fill:#e8f8f5,stroke:#16a085,color:#117a65
style A fill:#fef9e7,stroke:#f39c12
style B fill:#eaf2f8,stroke:#2980b9
style C fill:#eafaf1,stroke:#27ae60,color:#1e8449
style D fill:#eaf2f8,stroke:#2980b9
style E fill:#eafaf1,stroke:#27ae60,color:#1e8449
🔗 Diagram summary: The same phrase "Slack-Claude integration" covers two distinct products: (1) Cowork, where Claude.ai calls Slack as an MCP tool, and (2) Claude Code in Slack, where an @mention triggers a full coding session. The slash-command app install most users encounter corresponds to the second model — the focus of this post.
▶ Claude Cowork (Slack → Claude direction)
Claude.ai connects to Slack via MCP (Model Context Protocol), the open standard for giving AI models structured access to external tools. Claude reads channel history, sends messages, and coordinates across 50+ external services — Notion, Google Drive, Linear, and more. The defining characteristic: Claude drives; Slack is one of many tools it can call.
▶ Claude Code in Slack (Slack → code session direction)
Mentioning @Claude in a channel automatically infers coding intent, spins up a session on claude.ai/code, and posts incremental progress back to the same Slack thread. The defining characteristic: the conversation thread is a direct trigger for a code session — chat becomes the PR pipeline. This is what the rest of this post covers.
⚙️ From Install to Pull Request: How It Actually Works
Based on Anthropic's official documentation (code.claude.com/docs/en/slack), setup is four steps and the full @mention-to-PR lifecycle stays visible within the Slack channel.
📦 Four-Step Setup
① Workspace install → A workspace admin installs the Claude app from the Slack App Marketplace.
② Connect personal account → Each user connects their own Claude account from the Claude app's Home tab in Slack.
③ Authorize GitHub → On claude.ai/code, authenticate with GitHub and register the target repositories. This step is required for PR creation — Claude needs write access to open branches.
④ Invite to channel → Run /invite @Claude in the channels where coding sessions should be available.
🔁 @Mention → PR Lifecycle
flowchart TD
M([@Claude Mention
Natural language request]) --> I{Coding intent?}
I -->|YES| S[claude.ai/code
Session auto-created]
I -->|NO| Q[Standard chat response
or Retry as Code]
S --> P[Thread progress updates
Analyze → Fix → Test]
P --> R([View Session
Create PR])
style M fill:#e8f8f5,stroke:#16a085,color:#117a65
style I fill:#fef9e7,stroke:#f39c12
style S fill:#eafaf1,stroke:#27ae60,color:#1e8449
style Q fill:#eaf2f8,stroke:#2980b9
style P fill:#eafaf1,stroke:#27ae60,color:#1e8449
style R fill:#e8f8f5,stroke:#16a085,color:#117a65
🔁 Diagram summary: An @Claude mention goes through intent classification. If coding intent is detected, a code session auto-creates on claude.ai/code and posts incremental progress (analyze → fix → test) to the Slack thread. On completion, a "View Session / Create PR" button appears — the full loop stays inside the channel.
🚦 Two Routing Modes
| Mode | Behavior |
|---|---|
| Code only | Every @Claude mention routes to a code session regardless of message content. Best for channels dedicated to engineering tasks. |
| Code + Chat | Intent is inferred per message — coding requests route to Code, general questions to Chat. A "Retry as Code" button lets you manually override the routing decision. |
⚠️ Known Limitations (as of May 2026)
• GitHub only — GitLab and Bitbucket are not supported. For GitLab-centric teams this is a hard blocker.
• One PR per session — large tasks must be decomposed into scoped, discrete requests.
• Channels only, no DMs — private one-on-one code triggers are not supported.
• Rate limits are plan-level, not integration-level — Slack sessions draw from the same usage pool as your other Claude sessions. Heavy use in one surface throttles the others.
• Without Claude Code on the web access, only standard chat responses are returned — no code sessions are created.
💰 Can Individuals Use Slack? What Does It Cost?
Based on Slack's official pricing page (slack.com/pricing), Slack is not enterprise-only. Anyone can create a workspace and act as its admin — a solo workspace is fully functional. The typical entry path is Free until the limitations become real friction, then upgrading to Pro.
| Feature | Free | Pro | Business+ | Enterprise |
|---|---|---|---|---|
| Price (annual) | $0 | $7.25/mo | $15/mo | Contact sales |
| Price (monthly) | $0 | $8.75/mo | $18/mo | — |
| Message history | 90 days | Unlimited | Unlimited | Unlimited |
| App integrations | 10 | Unlimited | Unlimited | Unlimited |
| Voice / video | 1:1 only | 50-person huddles | 50 people | Unlimited |
| SSO / security | ✗ | ✗ | SAML | ✓ |
📊 Monthly Cost by Plan (Annual Billing)
🟡 Free Plan: What Hurts Most in Practice
• 90-day message history cap — Messages older than three months are inaccessible for both search and retrieval. This directly undercuts one of Claude's primary strengths: using accumulated conversation history as session context. If the project history isn't visible, Claude can't use it.
• 10-app integration limit — Installing the Claude app alone consumes one slot out of ten.
• A first-3-months 50% discount is listed on the official pricing page — if you're planning to go paid, timing the upgrade to that window reduces the initial cost.
🟢 Claude Plans — Which Tier Unlocks Slack Code Sessions?
Based on Claude's official pricing page (claude.com/pricing). The critical threshold: on the Free plan, @Claude in Slack returns only standard chat responses. Triggering a code session requires at least a Pro subscription. This is because Claude Code on the web — the session runtime that powers the Slack integration — is a paid-tier feature.
| Plan | Price | Claude Code | Slack Integration |
|---|---|---|---|
| Free | $0 | ✗ | Chat only |
| Pro | $17–$20/mo | ✓ | ✓ |
| Max 5x | $100/mo | ✓ | ✓ |
| Max 20x | $200/mo | ✓ | ✓ |
| Team | $20–$100/seat | ✓ | ✓ |
💵 Full Stack Monthly Cost for an Individual
※ Claude Pro ($17–$20) + Slack Pro ($7.25–$8.75). Slack bills per workspace, so even a solo user pays for one full seat.
📈 Why Pull Claude Into Slack at All?
The core argument is simple: the work context already lives in Slack. The traditional workflow — read a bug report in Slack → switch to IDE → copy-paste context into an AI assistant → apply the result → report back in Slack — involves repeated context-switching and manual transfer at every handoff. Each step is a place where intent degrades. Claude Code in Slack removes that middle layer entirely: the thread is the session input, and the PR link comes back to the same thread.
⏱️ Reported Task Time Reductions
※ Source: Medium DevOps case study. Absolute times are environment-dependent, but the order-of-magnitude compression — tasks collapsing into single-digit minutes — is the consistently reported result.
TechCrunch framed this shift as Slack evolving from a communication tool into a development execution surface — the chat window becomes a command interface. This also enables fully unattended automation patterns: scanning each morning for unreviewed PRs, running a code review session, and posting a summary back to Slack with no manual step involved.
🎯 Is It Worth Enabling as an Individual?
▶ Solo Developer
Claude Pro at $20/mo already justifies itself through Claude Code alone. Adding Slack Pro at $8.75 brings the total to ~$29/mo. That said, for solo work the Slack integration adds limited incremental value. The productivity gains come primarily from eliminating copy-paste context loss between teammates — if project context isn't accumulating in Slack, that benefit doesn't materialize. Claude Code on the web or the CLI will generally give better interaction fidelity and response speed for individual workflows.
🟢 Teams of 2–5 (Peak ROI Scenario)
For teams already running day-to-day coordination through Slack, Claude Code in Slack creates an "async coding delegation channel" at near-zero marginal overhead. The Team plan ($20/base seat) shares session visibility across the organization, giving everyone a clear record of what tasks were delegated and what came out. This is where the integration's value-to-cost ratio is highest.
🔴 Limitations to Keep in Mind
• No GitLab or Bitbucket support — a hard blocker for teams not on GitHub.
• Rate limits are tied to the individual account, not the integration — concentrated Slack usage throttles that user's other active sessions.
• For deep, multi-file refactoring, the Slack thread interface is a poor substitute for the claude.ai/code web UI. The Slack integration excels at triggering and reporting; it is not suited for sustained, complex sessions.
🧠 One-Line Summary
The value of Slack-Claude integration is not a new feature — it is the elimination of context relocation. Because the team's bug reports, discussions, and logs already live in Slack, they feed directly into Claude as session input, with no copy-paste or tab-switching required. For individuals, the most sensible path is Free Slack + Claude Pro to start, then upgrade Slack to Pro only when the 90-day message history cap becomes a genuine pain point.
🔗 References
• Anthropic Claude Code in Slack — Official Documentation
• TechCrunch — Claude Code Comes to Slack
• Medium — 10x DevOps Productivity with Claude Code (Korean)
This post is for informational purposes only. Pricing and features are subject to change per vendor policy. Verify current terms on official pages before making any subscription decision.
Collecting and organizing materials from a software engineering perspective, with a final review before publishing.
This post is based on publicly available data and sources. Last updated: June 8, 2026
댓글
댓글 쓰기