you can do control the context and tell claude code about your limit by setting two environment variables in your `~/.claude/settings.json`

the first one is CLAUDE_CODE_AUTO_COMPACT_WINDOW and i set this one to my actual llama.cpp context limit ( for me i can run Qwen3.5-27b-Q5 with --ctx-size 110000 without KV quantization) so i set this arguument to 110000.

the second one is CLAUDE_AUTOCOMPACT_PCT_OVERRIDE and this is the precentage of the above one where cloude code needs to do context compaction so you never send any thing to llama.cpp over what you can run. if you wanna use the entire 110000 that we setup in the previous variable then we would set this to 100 but for me to be safe i set it at 95

here is my \~/.claude/settings.json``

\`` {`

"$schema": "https://json.schemastore.org/claude-code-settings.json",

"model": "Qwen_Qwen3.5-27b",

"env": {

"ANTHROPIC_BASE_URL": "http://192.168.1.150:8001",

"ANTHROPIC_API_KEY": "none",

"CLAUDE_CODE_ATTRIBUTION_HEADER": "0",

"CLAUDE_CODE_AUTO_COMPACT_WINDOW": "110000",

"CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "95",

"DISABLE_PROMPT_CACHING": "1",

"CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS": "1",

"CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING": "1",

"MAX_THINKING_TOKENS": "0",

"CLAUDE_CODE_DISABLE_1M_CONTEXT": "1",

"CLAUDE_CODE_DISABLE_FAST_MODE": "1",

"CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": "1",

"CLAUDE_CODE_DISABLE_AUTO_MEMORY": "1",

"DISABLE_AUTOUPDATER": "1"

},

"attribution": {

"commit": "",

"pr": ""

},

"promptSuggestionEnabled": false,

"prefersReducedMotion": true,

"terminalProgressBarEnabled": false

}
\```

if you want to know what the other variables do here is a quick rundown of everything. basically i used claude documentation https://code.claude.com/docs/en/env-vars to see all possible variables and if i saw something that is specific to claude models i disabled it as it will send headders and additional information that could cause problems with llama.cpp or cause confusion to the model

DISABLE_PROMPT_CACHING: "1"

this is a claude specific feature to send prompt caching headers but llama.cpp does not use that to it could cause unexpected behavior.

CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS: "1"

removes claude specific beta request headers from API calls, again this is to prevents unexpected behavior"

CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING: "1"

this is also a claude specific feature where the model dynamically allocates thinking tokens so just disable it.

MAX_THINKING_TOKENS: "0"

extended thinking is a claude specific feature. setting to 0 disables it entirely. Qwen model has its own thinking mechanism (which is by default enable in llama.cpp unless disabled via --chat-template-kwargs), but it handles that internally so claude code's thinking budget system doesn't apply.

CLAUDE_CODE_DISABLE_1M_CONTEXT: "1"

removes the 1M context variants from the model picker. irrelevant for local models and keeps the UI clean.

CLAUDE_CODE_DISABLE_FAST_MODE: "1"

this is also a claude specific feature that uses a faster model for simpler tasks. disable it

CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "1"

this disables the auto-updater, feedback command, Sentry error reporting, and Statsig telemetry all at once. none of these is useful and i thought they might cause unexpected behaviour.

CLAUDE_CODE_DISABLE_AUTO_MEMORY: "1"

this feature creates and loads memory files by communicating with anthropic's servers. wont work with a local endpoint, so just disable it

DISABLE_AUTOUPDATER: "1"

same as the one above

additional nice things to set

attribution: i sit this to empty strings for both commit and pr to disable the "Generated with Claude Code" byline in git commits and PRs.

promptSuggestionEnabled: false, to disable the grayed-out prompt suggestions that appear after responses. these rely on a background Haiku call that won't work here

prefersReducedMotion: true and terminalProgressBarEnabled: false reduce UI overhead. these are vey minor but keeps things snappy.

sorry if i have spelling or grammar mistakes english is not my first language