parsec

Double your Claude Code limit, while improving accuracy

claude plugin marketplace add https://github.com/daseinlabs/claude-plugins
Read how it works
Backed byANTLER

demo

Installation

~ — claude code

claude plugin marketplace add https://github.com/daseinlabs/claude-plugins
marketplace added: parsec-marketplace
claude plugin install parsec@parsec-marketplace
parsec installed — prebuilt binary, no postinstall
claude
parsec active — local proxy running, requests go straight to Anthropic
/parsec:savings
12.4k input tokens not sent this session
across 31 requests — each measured via count_tokens

Illustrative session.

how it works

Local proxy, hosted brain

  1. Install the plugin

    One command in Claude Code — no base-URL surgery, no wire config. Agents, hooks, and the savings status line arrive as plugin surfaces.

  2. A local proxy curates each turn

    Chunking, freezing, and splicing happen on your machine. The hosted brain returns keep/cut scores; the proxy applies the cut, and your request rides your own credentials to Anthropic.

  3. Savings are measured, not modeled

    Every request runs a free count_tokens probe of the original body against what was actually billed. No modeled baseline, no extrapolation — if the ledger is empty, the report says so.

the product

What it looks like

Find your saved costs in app.getparsec.ai and the savings in your session.

app.getparsec.ai

usage & savings

Total cost saved
$7.41
1.4M input tokens not sent · measured on 391 of 402 requests
Spend
$18.63
billed at list price
Fail-open
0
served passthrough

By model

ModelRequestsTokens savedCost saved
claude-opus-5118486k$5.12
claude-sonnet-5284913k$2.29
The savings ledger — measured per request
claude

Read src/lib/platform.ts

re-read denied: file already in context (insist once to override)

parsec 12.4k saved

The plugin surface — guardrails and savings in-session

Illustrative — rendered UI, not screenshots; numbers shown are examples.

measurement honesty

Measured, never modeled

Before curation touches anything, the proxy calls Anthropic's free count_tokens on the original request body — the exact bytes you would have sent.

After the response comes back, it records what you were actually billed. The savings number is the difference between the two, computed per request.

Every row lands in a local ledger — ~/.parsec/ledger.jsonl — that you can open and read yourself.

If the probe fails, the row records a hole — never an invented number.

{
  "counterfactual_input_tokens": 21968,
  "billed_input_tokens": 1204,
  "cache_read_tokens": 9861,
  "model": "claude-sonnet-5",
  "request_id": "req_011CQx…",
  "fail_open": false
}
One row of the local savings ledger — illustrative values.

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.”

Nicholas SwaminathanFounderDasein

“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.”

Mara OkonkwoStaff engineerDraywick Labs

“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.”

Anders ViethInfrastructure leadLarkspur Systems

tiers

Start free. The learned curator is the upgrade.

Free

Start here

The plugin

Free

  • Exploration maps
  • No-reread hook
  • Savings status line
  • Runs on your plan or key

Pro

Plugin + local proxy

Coming soon

  • The full learned curator via the hosted scoring API
  • Tool-schema prune
  • Governor
Contact

Team

Hosted BYOK gateway in our cloud

Coming soon

  • API keys only — never subscription tokens
  • Zero local install
  • Centralized reporting
Contact

Enterprise

Self-host

Talk to us

  • Licensed checkpoints
  • Containerized stack
  • On-prem fine-tuning on your traces
Contact

faq

Straight answers

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.

Can I use my Claude subscription (Max plan)?

Yes. Traffic leaves your machine with your own OAuth token, same as stock Claude Code — the rewriting happens locally. 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.

get started

Two commands from here

claude plugin marketplace add https://github.com/daseinlabs/claude-plugins

claude plugin install parsec@parsec-marketplace

Open the dashboardSource on GitHub