parsec for Claude Code
Double Claude Code's limit, while improving accuracy
Measured on 100 SWE-bench Verified tasks with headless Claude Code: Parsec cut input tokens 54% and total cost 39% while solving 62 tasks against the no-compression baseline's 57. See the benchmark
Claude Code gets the full plugin: scout tools, the no-reread hook, skills, and status-line savings. Uninstall anytime with claude plugin uninstall parsec.
testimonials
What engineers say
“I love this. In the past week I saved $2.5K in api credits and 6B in tokens. I blasted my plan and never hit the limit.”
“By turn thirty our agents were dragging the entire transcript into every request. parsec was the first tool that trimmed it without asking me to trust a summary I couldn't inspect.”
“The ledger is what convinced me. Every request shows the counterfactual next to what was actually sent — I didn't have to believe a dashboard, I could read the receipts.”
Pricing
Pro
Start herePlugin + local proxy
$40/mo Free
- The full learned curator via the hosted scoring API
- Tool-schema prune
- Governor
Team
Hosted BYOK gateway in our cloud
Coming soon
- API keys only — never subscription tokens
- Zero local install
- Centralized reporting
Enterprise
Deployed in your cloud
Talk to us
- The whole stack — scoring API included — runs in your VPC
- Licensed checkpoints, containerized
- Fine-tuning on your traces, without them leaving your network
FAQ
Which coding agents does it work with?
Claude Code, OpenAI Codex CLI, and opencode — one local proxy serves all three, and every ledger row records which tool it came from. Claude Code gets the full plugin surface: status line, hooks, and skills. Codex routes through parsec with your existing ChatGPT sign-in (or an API key), and opencode works with Anthropic API-key providers. One honesty caveat: OpenAI has no count_tokens endpoint, so Codex rows record actually-billed usage without the measured-savings counterfactual — we do not estimate what we cannot measure.
Does my code go to your servers?
On the Pro tier, the local proxy sends chunk text and structural features to our scoring API over TLS and gets keep/cut scores back — your model requests never route through us; they leave your machine with your own credentials. On the free tier, tokens are sent to us but never stored. The one exception is the hosted Team gateway, where you explicitly choose to run the proxy in our cloud with a BYOK API key. On Enterprise the direction reverses: the scoring API is deployed inside your own cloud, so no chunk text reaches us at all.
Can I use my Claude subscription (Max plan) or ChatGPT plan?
Yes. Traffic leaves your machine with your own OAuth token, same as stock Claude Code — the rewriting happens locally. Codex works the same way with your ChatGPT sign-in. We never route subscription tokens through our cloud; the hosted gateway is BYOK API keys only.
What happens when your API is down?
The proxy fails open. Your request passes through uncompressed, so a scoring outage never blocks a session. Fail-open events are counted and visible, not silently swallowed.
How are savings calculated?
Per request, the proxy runs a count_tokens probe on the original body and compares it against what was actually billed. That measured counterfactual is the only source of savings numbers — never a modeled baseline. The ledger is kept locally, alongside your traffic.
Does it train on my data?
No by default. Telemetry is opt-in and tiered, and the default is off. You can preview exactly what would upload before opting in, and purge requests are honored.