Claude Code Cache Fix

claude-code-cache-fix

English | 中文 | 한국어 | Français | Português

Cache optimization proxy for Claude Code. Fixes prompt cache bugs that cause excessive quota burn, stabilizes the request prefix, and monitors for silent regressions. Works with all CC versions including the v2.1.113+ Bun binary.

*This README documents current main; release availability is noted per feature.*

What it does to your traffic

A local proxy sits between Claude Code and Anthropic. Before you read further,
here is exactly what that means — the full treatment is in
Security model.

- Binds to 127.0.0.1 by default.
- Forwards Claude Code traffic to Anthropic. On the default path it makes no
  other outbound calls — telemetry is written to local files under
  ~/.claude/, never sent anywhere. Two opt-in features do perform their own
  egress, both off unless you enable them: OAuth refresh
  (CACHE_FIX_OAUTH_REFRESH=on) posts to Anthropic's token endpoint, and
  forward-proxy download acceleration re-issues release downloads to
  downloads.claude.ai / storage.googleapis.com.
- Can read and rewrite POST /v1/messages. That capability *is* the cache
  repair — there is no version of this that works without it.
- It is idempotent: if nothing needs fixing, the request passes through
  unmodified. It normalizes request structure (block order, fingerprint, TTL);
  it does not modify your conversation.
- Each transform is one file in proxy/extensions/, readable in isolation.
- Independently assessed as a legitimate tool
  by @TheAuditorTool (2026-04-14).

Forward-proxy mode (--remote-control) additionally terminates TLS for
api.anthropic.com using a locally-generated CA, which your client must trust.
Everything else is blind-tunnelled. That mode is opt-in and off by default.

Do you need this?

Install or…