SoonPatch
Free · runs in Claude Code

Paste a Slack bug.
Claude resolves it.

SoonPatch is an MCP for Claude Code. It finds which of your repos a Slack report is about — across every project on your machine — and fixes it in the session you’re already in.

$curl -fsSL https://soonpatch.com/install-mcp.sh | sh

macOS & Linux · no signup · uses your own Claude Code · docs

claude code
>resolve this: acme.slack.com/archives/C04BUG/p171…
⚙soonpatch_locate14 workspaces
app-backend[branch: main]confidence high
Fix drafted ChatValidationService.php
323- \x{200B}-\x{200F}
323+ keep U+200D zero width joiner
applied in app-backend · review & commit when ready
How it works

One line to install. Then just paste the link.

SoonPatch lives where you already work. No new app, no context-switch — it turns Claude Code into the engineer who triages your Slack.

1Once

Install

One line drops the MCP into Claude Code and registers a skill. No account, no API key, no app to keep open.

2Per report

Paste the Slack link

In any Claude Code session, paste a Slack permalink and say “resolve it.” SoonPatch fetches the full thread — replies and screenshots included.

3Automatic

Locate & fix

It hands Claude a case brief of every repo on your machine, so the model finds the right one — even one you're not in — and drafts the fix in place.

The case brief

It already knows your whole machine.

A single Claude Code session only sees one repo. SoonPatch assembles a case brief of every project you work on and hands it to the model — so one paste reaches the right repo, branch and files, wherever they live.

Every repo you've toucheddiscovered from ~/.claude/projects — not just the one you're in
Branches, worktrees & recent commitsso it reasons about where work actually landed
Recently-changed files & active sessionsthe strongest signal for what a report is really about

Assembled locally, on demand. Nothing is indexed or uploaded.

case brief~/.claude/projects · 14 workspaces
active session
app-backend[branch: main] active located
commits “Sanitize chat input”, “Add emoji map”, …recently changed ChatValidationService.php, EmojiMap.php
also on this machine
mobile-app[branch: release/4.2]
commits “Visit update sheet”, “Push token refresh”, …recently changed chat_screen.dart
web-dashboard[branch: develop]
commits “Changelog modal”, “Date range filter”, …recently changed generate.ts
admin-tools[branch: main]
commits “Sitter badge order”, “Block column”, …
shared copy lives in 3 repos — branch + recent commits broke the tie
Outcomes

Not everything is a bug. SoonPatch knows the difference.

Every message gets the right response, and SoonPatch never auto-merges a guess. You always see the reasoning before you act.

Bugpatch

@soonpatch the modal shows “0 changes” even with commits in range.

generate.ts +6 −4
12- c.authoredAt >= range.since
12+ Date.parse(c.authoredAt)
Patch ready · 2 files · apply when you’re ready
Featurebrief

@soonpatch can we group the changelog by author?

handoff brief
Needs a format decision before any code. Drafted a brief and a ready-to-run prompt for #product instead of guessing.
ready-to-run prompt
“Add a groupBy=author serializer to changelog/generate.ts + a toggle in the modal.”
Questionreply

@soonpatch does the export skip merge commits on purpose?

draft reply
Yes, by design. Flip --include-merges to keep them. No code change needed.
Not a bugverified

@soonpatch the deploy button is greyed out, is that expected?

verified · DeployButton.tsx
disabled={!ciGreen} · gated on CI (2/5 green)
Working as intended · thread closed
Local-first by design

Your code never leaves your machine.

SoonPatch runs locally and drives your own Claude over the code already on your machine. It reads your repos, runs the model with your key, and writes the diff, all on your hardware. No code upload, no third-party indexing.

Source stays on disk; only the prompt and the result move
Runs on the Claude Code you already use. No extra API key, no separate bill
No SoonPatch backend or account. Only anonymous, content-free usage stats — never your code, messages, or repo names (opt out anytime)
Slack messagepasted in, or permalink
SoonPatch · localreads your repos on disk
Drafted patchwritten to your working tree
no code uploaded
Free

No plan. No signup. Just install it.

SoonPatch runs on the Claude Code you already use, so there’s nothing to buy. Paste the one-liner, restart Claude Code, and resolve your next Slack report.

$curl -fsSL https://soonpatch.com/install-mcp.sh | sh

then: claude mcp add --scope user soonpatch -- ~/.soonpatch/bin/soonpatch-mcp

Locate the right repo across every project on your machine
Full Slack threads + screenshots, fetched for you
Investigates and drafts the fix in your Claude Code session
Runs on the Claude Code you already pay for — no extra bill
Local-first: no backend, no account; only anonymous, content-free usage stats (opt-out)
macOS & Linux (static binary, any distro)
FAQ

Questions, answered.

An MCP server for Claude Code. You paste a Slack report and ask Claude to resolve it; SoonPatch hands Claude a case brief of every repo on your machine so it locates the right one and fixes it — without you switching projects.
Claude Code, and Slack connected in it. SoonPatch doesn't fetch Slack itself — your Claude Code reads the thread, then hands it to SoonPatch. Connect Slack once with `claude plugin install slack` (then approve the browser login). Already added Slack manually and it won't connect? Clear the stale local entry first: `claude mcp remove slack -s local && claude plugin install slack`. No Slack? You can also paste the thread text in directly.
It's free. SoonPatch runs on the Claude Code you already pay for — there's no SoonPatch subscription, no account, and no separate API key.
It reads the workspaces you've used in Claude Code (from ~/.claude/projects) — their branches, recent commits, recently changed files and active sessions — and gives that case brief to the model. One paste reaches the right repo across your whole machine, even one you're not currently in.
No. SoonPatch runs locally and drives the Claude Code already on your machine, and there's no SoonPatch backend — your source never leaves your box. It makes just two network calls, neither of which sends your code: anonymous, content-free usage stats (an install count and which tools run, never your messages or repo names), and a background check for new versions so it stays up to date without a reinstall. Opt out with SOONPATCH_NO_TELEMETRY=1 (or DO_NOT_TRACK=1) and SOONPATCH_NO_UPDATE=1.
macOS and Linux. The Linux build is a static binary, so it runs on any distro with no dependencies.
No. It investigates and proposes the fix in your session; you review and keep it or discard it with git like any other change. Nothing is pushed or merged for you.

Resolve your next Slack bug from Claude Code.

One line to install. Then paste a Slack link and watch Claude locate the right repo and draft the fix — free, on your own machine.

$curl -fsSL https://soonpatch.com/install-mcp.sh | sh

free · macOS & Linux · runs locally · no signup

Questions or feedback? lucas@soonpatch.com