Keep Claude Code's context clean for sharper answers and lower cost, automatically.

Website · Compare · Releases

npm i -g sipcode
sipcode init

That is it. Your next Claude Code session will use Sipcode automatically. Verify a few minutes later:

sipcode drift

If the output reads no drift, context health stable, Sipcode is doing its job.

Sipcode is a free command-line tool that sits between you and Claude Code. It does three things:

1. It watches Claude Code's context window and warns you when it starts to bloat (we call this "context rot")
2. It catches duplicate file reads and other waste before they reach Claude, so you pay less for the same answers
3. It gives you receipts. Every saving is measurable in your terminal.

It is open source under the MIT license. It makes zero network calls during normal use. Your data never leaves your laptop.

If you use Claude Code for real work, you have already felt this:

• Long sessions get expensive fast. A two-hour session on Claude Max can burn through your daily plan
• Quality drops as the context window fills. Claude starts re-reading files, repeating itself, losing the thread of what you asked
• You cannot tell what is bloat and what is signal

Sipcode measures the bloat, then removes the parts Claude does not need. The savings are not theoretical. Run sipcode benchmark on any machine and you will see the same 62.6% median reduction on the locked 20-task corpus.

After installing, here are the five commands that show you what Sipcode is doing.

Tells you if your current Claude Code session is drifting from your normal usage pattern. Bloated context, repeated reads, stale signals are all flagged here.

✓ Sipcode drift: no drift, context health stable vs your recent baseline.

Shows what Sipcode caught in the current session, broken down by rewriter.

Sipcode proxy, rewrite stats
  total rewrites:    144
  est. tokens saved: ~288,685 (heuristic)
  signal kept:       67% (med), weighted across all rewrites

Runs the locked 20-task corpus and produces a verifiable savings number. Anyone, anywhere can run this and get 62.6%.

62.6%  median savings on a locked 20-task corpus
       range 37.4% to 80.6%   3,567,170 tokens   $67.43

Daily spend summary. Tokens used, sessions, output ratio, comparison to your 30-day median.

spend so far    $1.20    across 4 sessions
tokens so far   943.8K   output ratio 3.7%

Month-end projection based on your last 14 days.

projected month-end   $17,674   (range $14,139 to $21,208)

Sipcode works on Mac, Linux, and Windows. You need Node.js 18 or newer.

Skip this step if you already have Node.js. Otherwise:

• Mac: brew install node
• Linux (Ubuntu / Debian): sudo apt install nodejs npm
• Windows: Download from nodejs.org

Verify it worked:

node --version

You should see v18.0.0 or higher.

npm i -g sipcode

This downloads Sipcode from npm and makes the sipcode command available everywhere.

If you see permission errors on Mac or Linux, try:

sudo npm i -g sipcode

Verify it installed:

sipcode --version

You should see 1.6.15 or higher.

sipcode init

This command does four things:

1. Creates a small .sipcode/manifest.md file in your current project so Claude knows what your project is about
2. Adds a small block to your CLAUDE.md (or creates one) with rules that keep Claude's replies terse
3. Installs the Sipcode hook into Claude Code, which is the thing that actually saves tokens
4. Marks the date so sipcode impact can show you before-and-after savings later

You will see a checklist as it runs. Each step shows a checkmark when it completes.

Sipcode picks up automatically on the next tool call Claude makes. No restart needed in most cases. To be safe, you can close any existing Claude Code window and open a fresh one.

Now Claude Code will be using Sipcode in the background.

sipcode drift
sipcode proxy --stats

If drift says "no drift" and proxy --stats shows a few dozen rewrites with savings, everything is working.

Yes. MIT license. No tracking. No telemetry sent to us. No paid tier. You can read every line of source code on GitHub.

No. Sipcode makes zero network calls during normal use. Everything runs locally on your machine. We have a privacy test that fails if any network code is imported into the source.

See the comparison page. The short version: Sipcode is the only one with a published reproducible benchmark, zero false-dedup by architecture, and mid-session install support.

When Claude's context window fills up with stale, repeated, or off-topic information, the quality of its answers drops. Sipcode measures this with sipcode drift and removes most of the waste with the proxy hook.

Today, only with Claude Code (since Claude Code is the only tool that exposes the hooks Sipcode needs). Support for other CLIs is something we are exploring.

sipcode proxy --uninstall
npm uninstall -g sipcode

Run any of them with --help for full options.

• Node.js 18 or newer
• Claude Code installed (for the proxy hook). Sipcode also works as standalone CLI tools (benchmark, score, etc.) without Claude Code installed.

MIT. See LICENSE.

Built with care for the indie developers who burn through their Claude Max plan in two hours. The 62.6% benchmark methodology is documented in benchmark/METHODOLOGY.md. Anthropic's published research on context-window quality informs the integrity-scoring approach.