Skip to content

v4.3.0 — Remote Control through the proxy

Latest
Latest

Choose a tag to compare

View all tags
@vsits-proxy-builder vsits-proxy-builder released this 17 Jul 18:32
· 48 commits to main since this release
v4.3.0
4b0722c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Remote Control through the proxy

Claude Code ≥ 2.1.196 disables Remote Control / mobile session visibility (and /schedule, claude.ai MCP connectors) whenever ANTHROPIC_BASE_URL is set — which is exactly how reverse-proxy mode routes the client. v4.3.0 adds an opt-in forward-proxy mode that keeps Claude Code first-party so those features keep working, while the proxy still sees and transforms /v1/messages.

All changes are additive and backward-compatible. Every new mode is opt-in; defaults are unchanged. Upgrading with prior defaults gives you identical reverse-proxy behavior.

Highlights

  • Opt-in forward-proxy mode (CACHE_FIX_FORWARD_PROXY=on) — the proxy handles HTTP CONNECT and MITMs only api.anthropic.com with a locally-generated CA, blind-tunneling everything else. The client wires HTTPS_PROXY + NODE_EXTRA_CA_CERTS and leaves ANTHROPIC_BASE_URL unset, so Remote Control / mobile session visibility keeps working. (#251, implements #248 — thanks @codeslake)
  • cache-fix-proxy --remote-control — one-command launcher that does the forward-proxy wiring for you. (#254)
  • Honor CLAUDE_CONFIG_DIR for all on-disk proxy state, so multiple config roots don't clobber each other's credentials/state. (#246 — thanks @codeslake)
  • Accurate statusline TTL tier — the cache-TTL indicator now reads the measured ephemeral_1h/ephemeral_5m split instead of guessing, fixing two mislabel cases. (#252, fixes #247 — thanks @codeslake)

Notes

  • Forward-proxy mode is load-bearing (TLS termination, a generated MITM CA, a credential-bearing wire path). It went through independent (Codex) review, human review, and live end-to-end validation (Remote Control restored, phone connected).
  • Remote Control does a trusted-device enrollment on first connect that can need a few /remote-control retries — a Claude Code step, not a proxy failure. See the README Forward-proxy section, which also documents the shared-service crash-semantics tradeoff.

Upgrade: npm install -g claude-code-cache-fix@4.3.0

Full details in CHANGELOG.md.

Contributors

codeslake
Assets 2
Loading