Free where it builds trust. Paid where it saves time.
Free
$0forever
Generate and lint your config, in your browser.
- Unlimited manifest triage — 100% client-side
- Nine config files: five advisory (AGENTS.md, CLAUDE.md, GEMINI.md, Cursor .mdc rules, copilot-instructions.md) plus four enforced (.cursorignore, .geminiignore, .codeiumignore, Claude Code settings deny rules)
- Lint an existing config against your file tree — graded report + one-click fixes
- Estimated monthly savings counter with live model pricing
- No signup, no upload, no telemetry on your file list
Pro
$9per month
Your repo changes every day — the configs keep up with it.
- Drop-in GitHub Action + git pre-commit hook
- All nine config files regenerate on every push — advisory and enforced alike
- contextpruner lint CLI — check configs locally or fail CI on drift
- contextpruner serve — filter junk out of your agent's search results at runtime, all local (shell shims + MCP tools)
- One API key unlocks the automation, the lint CLI, and the runtime filter
- We never get access to your repo — your own runner makes the commits
- Usage dashboard on your account page: syncs run, tokens kept out, what it's worth
Questions, answered
- Why is the triage free?
- The free tier runs the same pruning engine as the paid API, so you can check the output before paying anything. The subscription adds automation, not better results.
- Can I lint a config I already have?
- Yes, for free, in your browser. Paste an existing AGENTS.md or CLAUDE.md alongside your file tree and ContextPruner grades it — flagging junk it doesn’t skip yet, rules that match nothing, and configs that disagree — then offers one-click fixes. The paid tier adds the contextpruner lint CLI so you can run the same check locally or fail CI when a config drifts.
- What exactly does $9/month buy?
- Staying in sync, on one subscription. A GitHub Action or pre-commit hook regenerates all nine config files — advisory and enforced — on every push, so the configs keep up as your repo changes instead of drifting stale. The contextpruner lint CLI checks your configs against your tree from the command line or in CI. The contextpruner serve command filters junk paths out of your agent’s search results at runtime, so the middle-tier junk that stays advisory never floods a broad search. And your account’s usage dashboard shows what your last sync cut and how many syncs have run. The engine runs on your machine — only your API key is sent, to confirm an active subscription.
- Do I need a separate key for the CLI and the automation?
- No. One subscription, one API key. The same cp_live_ key authorizes everything the paid tier includes — the config automation, the lint CLI, and the contextpruner serve runtime filter alike — so set it as CONTEXTPRUNER_API_KEY wherever you need it. You can hold two keys at once, but that’s for rotating a key without downtime, not because features need separate ones.
- Do you get access to my code?
- No. The paid tier sends file paths, byte sizes, and any keep: declarations from a committed .contextpruner file — never file contents. We return config text, and your own runner commits it with your own credentials. We never hold a repo token.
- What happens if I cancel?
- Your API key deactivates, and the last generated config files stay in your repo. The free tier keeps working forever.