Integrations

Claude Code

Use tokenolo as a drop-in local proxy for Claude Code.

tokenolo is a drop-in local proxy for Claude Code. It's a middleware layer that sits between you and the agent — no rewiring, no new model, no change to how you work. You keep the same commands; tokenolo trims redundant filler from the input before it's sent, then gets out of the way.

How it fits

Claude Code assembles a prompt plus the surrounding context it would send to the model. tokenolo reads that input, removes redundant filler from your own messages (removal-only, so the text is always a subsequence of what you wrote), and forwards everything else — system prompt, tools, tool output, files, history — untouched.

prompt → Claude Code → tokenolo wrap → filler removed → model

The request goes to the model under your own key; nothing routes through a tokenolo server.

Setup

Note: the CLI is pre-release — confirm exact commands with tokenolo --help.

Install tokenolo on the machine where you run Claude Code:
```
npm i -g tokenolo
```
Sign in. Create a free account at app.tokenolo.com/signup — no card required — generate an API key, then authenticate:
```
tokenolo login --key tk_live_…
```
Wrap Claude Code. Launch it through tokenolo — this starts a local proxy on 127.0.0.1 and points Claude Code at it, so the filler in each message is trimmed on the way to the model:
```
tokenolo wrap claude
```
Work as usual. Same commands you already use. tokenolo trims filler from each message on the way in, forwards the rest untouched, then steps aside.

What you get

Private by design — your code never leaves your machine; requests go to the model under your own key, and nothing is stored.
Cache-safe — byte-stable edits keep your prompt cache valid across turns.
Zero rewiring — drop-in. No new model, no workflow change.

Next steps

tokenolo wrap — the command reference.
What gets optimized — what tokenolo trims and what it forwards untouched.