AI News HubLIVE
In-site rewrite2 min read

Sipcode: Keep Claude Code's context clean for sharper answers

Sipcode is a PreToolUse hook for Claude Code that cleans context by capping verbose output and deduplicating same-session re-reads. Anthropic research shows 29% quality lift and 40% fewer agent errors. Benchmark achieves 62.6% median tool-output savings. MIT licensed, privacy-focused.

SourceProduct Hunt AIAuthor: Anuj ojha

Sipcode: Keep Claude Code's context clean for sharper answers | Product Hunt

Sipcode

Launching today

Keep Claude Code's context clean for sharper answers

2 followers

Keep Claude Code's context clean for sharper answers

2 followers

Visit website

LLM Developer Tools

Context hygiene for Claude Code. Caps verbose tool output and dedupes same-session re-reads so the model sees signal, not noise. Anthropic measures 29% quality lift from cleaner context. Proof: 62.6% median tool-output savings on a locked 20-task benchmark. MIT.

Overview

Reviews

Alternatives

Built with

Team

More

Free

Launch tags:Open Source•Developer Tools•Artificial Intelligence

Launch Team / Built With

Subscribe

Promoted

Maker

📌

Hey PH. I'm Anuj, solo indie dev. Built Sipcode because I kept watching Claude Code re-read the same files 6-8 times per session and re-print 4,000-line npm install logs into its context. Each unnecessary token in the window pushes signal out and makes the next answer worse. That is the reliability problem I built it to fix.

It is a PreToolUse hook for Claude Code. Caps verbose output (git log, npm install, grep, tsc), dedupes same-session re-reads of unchanged files, exposes 15 MCP tools so Claude can read its own context-hygiene stats. Anthropic's own research: cleaner context lifts quality 29% and cuts agent errors 40%. That is the mechanism Sipcode targets.

Tokens saved are the PROOF the context got cleaner. Locked 20-task benchmark: 62.6% median tool-output savings, $67.43 per corpus run, reproducible on any machine. The benchmark task list is checked into the repo.

Honest disclosure that became the launch story: last week my drift tool said 624,940 tokens wasted in a single session. My proxy --stats credited only 7,553 saved. 83x undercount, my own tool lying to me. Root cause was mid-session installs leaving the first half of the session uncached. Shipped v1.6.15 with Verified Warm-Fill 24h later, drift now reads "no drift detected." Shipped v1.6.16 today with cache-defer and grep-cap fixes. Three releases in nine days.

MIT, zero network calls in normal use (privacy test fails the build if anyone imports node:http in src/). Happy to answer anything technical, especially the Warm-Fill correctness proof or the benchmark methodology.

If Sipcode saves you a session, a star on the repo at github.com/Anuj7411/sipcode would mean a lot to a solo project trying to find the people who would actually benefit from this.

Report

7h ago