Context savings for coding agents — Claude Code · Codex CLI · opencode — measured, never modeled.
One line. The installer auto-detects the coding agents on your machine and
activates parsec for each — no build step, no npm, no sudo; nothing is written
outside ~/.parsec and the tools' own config dirs:
curl -fsSL https://raw.githubusercontent.com/daseinlabs/plugins/main/install.sh | bashWindows (PowerShell; or run the curl | bash line inside WSL):
powershell -c "irm https://raw.githubusercontent.com/daseinlabs/plugins/main/install.ps1 | iex"Signed in at app.getparsec.ai? The dashboard's first-run screen emits the same lines with your API key baked in, so the install reports savings from its first request with no separate key step:
curl -fsSL https://raw.githubusercontent.com/daseinlabs/plugins/main/install.sh | bash -s -- --key psc_…powershell -c "Set-Item Env:PARSEC_API_KEY psc_…; irm https://raw.githubusercontent.com/daseinlabs/plugins/main/install.ps1 | iex"The install ends by signing you in: a browser tab opens at app.getparsec.ai, you sign in and click Connect, and the key is handed straight back to this machine — nothing to paste. Skipped it? Any of these opens the same handoff later:
- Sign in to parsec… in the parsec menu-bar / tray app
parsec loginfrom any shell/parsec:logininside a Claude Code session
A machine with no browser (SSH, CI) is the one case that needs a key by hand:
mint one on the dashboard's account page and run parsec key set psc_… there.
Until a key is set, parsec saves nothing. Your tools keep working exactly as before; parsec stays pure passthrough until it is entitled.
Prefer to pick instead of auto-detecting? … | bash -s -- claude,
… | bash -s -- codex, or … | bash -s -- opencode.
- Claude Code: the full plugin — scout tools, hooks, skills, status-line savings (see What you get below).
- Codex CLI: every codex session routes through parsec with your existing
ChatGPT sign-in (the token never leaves your machine). API-key mode instead:
… | bash -s -- codex --byok. Type$and pickparsec-savingsfor the ledger. - opencode: Anthropic API-key providers;
/parsec-savingsshows the ledger.
Undo anytime: parsec disable codex|opencode,
claude plugin uninstall parsec.
Claude Code only, via the plugin marketplace?
claude plugin marketplace add https://github.com/daseinlabs/plugins
claude plugin install parsec@parsec-marketplaceOr interactively: /plugin → Marketplaces → add daseinlabs/plugins.
Use the full HTTPS URL rather than the owner/repo shorthand — the shorthand
clones over SSH, which fails for anyone without a GitHub SSH key.
Already have the plugin and want the other tools too? Just run
parsec setup codex (or parsec setup opencode) — no download needed.
Explore with a map, not a bulk read. Scout tools — repo_map,
file_outline, find_symbol — plus a parsec:explore subagent that answers
"how does X work" from signatures and line-anchored key lines instead of
dumping whole files into your context.
Stop paying for the same bytes twice. A PreToolUse hook denies re-reads of
file ranges already in context and breaks repeated identical commands, with an
insist valve for when the file really did change.
Compact without losing the plot. /parsec:trim stages a better /compact:
a deterministic trim keeping only the parts of the session that were actually
re-read, edited, or used later, plus a standing-directives block so your
rulings keep governing after compaction. Run it, then /clear — the trimmed
context is injected into the next session automatically.
See the number. Every save is written to a local ledger — rolled up in the
Claude Code status line, codex's $parsec-savings, and opencode's
/parsec-savings. In Claude Code, ask for it any time:
| Skill | What it does |
|---|---|
/parsec:savings |
Measured savings — by request, conversation, and session |
/parsec:trim |
A better /compact: stage a deterministic trim of the transcript (what was actually re-read, edited, or used later) plus your standing directives, injected automatically after /clear. --level 1–5 sets aggressiveness (default 3) |
/parsec:setup |
Activate parsec: routing env, status line, proxy — or retry a failed first run |
/parsec:proxy |
Restart the local proxy if it was killed mid-session |
/parsec:login |
Sign in (browser handoff) — or show / clear the stored account key |
/parsec:share |
Opt-in telemetry: preview the exact bytes, or turn it off |
/parsec:uninstall |
Clean removal — routing, proxy, local data, plugin |
Savings numbers are a per-request count_tokens counterfactual against
actually-billed usage — never a modeled baseline, never an extrapolation. Hook
rows are blocked re-reads × the on-disk bytes of the denied range. If the ledger
is empty, the report says so.
- Telemetry is off by default. The product is fully functional with it off — consent by degradation is not consent.
- Model traffic never touches our cloud. Requests ride your own credentials, straight from your own machine to your model provider.
/parsec:share --previewdumps the exact bytes that would ever be uploaded, locally and human-readable, before anything is sent.
darwin-arm64 · linux-x64 · win-x64. Intel macOS is not yet supported.
plugins/parsec — the plugin's markdown/JSON surfaces plus the prebuilt
per-platform parsec binaries, along with the installers that ship beside
them.
This repo is assembled and force-pushed by CI on every release of the private monorepo. Do not commit here by hand — history is intentionally squashed to keep clones small.
getparsec.ai · dashboard · built by Dasein Labs