How-To: Enable additional cache-fix settings in VS Code beyond the extension UI #43
cnighswonger
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The VS Code extension only exposes 4 settings in the GUI (Debug, Image Keep Last, Output Efficiency Replacement, Strip Git Status), but the interceptor has many more toggles available as environment variables.
Setting env vars in VS Code
Add to your VS Code
settings.json:{ "terminal.integrated.env.linux": { "CACHE_FIX_DEBUG": "1", "CACHE_FIX_STRIP_GIT_STATUS": "1", "CACHE_FIX_NORMALIZE_IDENTITY": "1", "CACHE_FIX_NORMALIZE_CWD": "1", "CACHE_FIX_NORMALIZE_SMOOSH": "1", "CACHE_FIX_PREFIXDIFF": "1" } }Use
terminal.integrated.env.osxfor Mac,terminal.integrated.env.windowsfor Windows.Per-extension skip toggles
Disable individual fixes if they cause issues:
Opt-in features
These are OFF by default and must be explicitly enabled:
CACHE_FIX_NORMALIZE_IDENTITY=1CACHE_FIX_NORMALIZE_CWD=1CACHE_FIX_NORMALIZE_SMOOSH=1CACHE_FIX_STRIP_GIT_STATUS=1CACHE_FIX_PREFIXDIFF=1CACHE_FIX_IMAGE_KEEP_LAST=NImportant: v2.1.113 compatibility
CC v2.1.113 switched from Node.js to a compiled Bun binary. The
--importpreload mechanism that the interceptor and VS Code extension depend on no longer works on that version.Workaround: Pin Claude Code to v2.1.112 or earlier:
We are building a proxy-based replacement that will work with all CC versions including v2.1.113+. See #40 for the design.
Beta Was this translation helpful? Give feedback.
All reactions