CLAUDE_CODE_FORCE_GLOBAL_CACHE
Updated by Alex Sorokoletov
CLAUDE_CODE_FORCE_GLOBAL_CACHE is a Claude Code environment variable: Previously forced use of a global cache directory. Likely superseded by improved cache management that no longer needs a manual override. Removed between v2.1.87 and v2.1.88, so current releases ignore it. It is not in the official reference.
| Status | Removed between v2.1.87 and v2.1.88 |
|---|---|
| Added | Present since v2.1.69 or earlier |
| Category | Shell and tools |
| Official docs | Not listed |
How to set it
For one session, export it in the shell that starts Claude Code:
export CLAUDE_CODE_FORCE_GLOBAL_CACHE=<value>
claudeTo apply it to every session, add it to the env object of a settings file:
// ~/.claude/settings.json
{
"env": {
"CLAUDE_CODE_FORCE_GLOBAL_CACHE": "<value>"
}
}Release notes that mention it
Related variables
CLAUDE_CODE_WEBFETCH_CACHE_TTL_MSBASH_MAX_OUTPUT_LENGTH: Max bash output character length.CLAUDE_BASH_MAINTAIN_PROJECT_WORKING_DIR: Maintain consistent working directory across commands.CLAUDE_BASH_NO_LOGIN: Replaced by CLAUDE_CODE_SHELL_PREFIX.CLAUDE_CODE_BASH_EDIT_DIFFCLAUDE_CODE_DISABLE_ADVISOR_TOOL: Disables what appears to be an internal advisory tool.CLAUDE_CODE_DISABLE_BG_SHELL_PRESSURE_REAPCLAUDE_CODE_DISABLE_INLINE_SHELL_RM_PROMPT: Turns off the new prompt that catches a dangerous rm inside an inline bash -c or sh -c script.
Frequently asked questions
What does CLAUDE_CODE_FORCE_GLOBAL_CACHE do?
Previously forced use of a global cache directory. Likely superseded by improved cache management that no longer needs a manual override.
Which Claude Code version has CLAUDE_CODE_FORCE_GLOBAL_CACHE?
Removed between v2.1.87 and v2.1.88, so current releases ignore it.
How do I set CLAUDE_CODE_FORCE_GLOBAL_CACHE?
Export it before starting Claude Code (export CLAUDE_CODE_FORCE_GLOBAL_CACHE=value), or add it to the "env" object in ~/.claude/settings.json to apply it to every session.
All variables, searchable: Claude Code environment variables.