How to Disable Claude Code's 1M Context Window to Reduce Token Usage

Claude Code users can disable the 1M context window feature that may be increasing token usage beyond expectations. According to a Reddit discussion, Anthropic's recent usage limit tightening has led to faster quota consumption, with the company pointing to the 1M context window as a contributing factor.
Configuration Options
The source provides two methods to control context window behavior:
Option 1: Disable 1M Context Completely
Add this to your ~/.claude/settings.json file:
{
"env": {
"CLAUDE_CODE_DISABLE_1M_CONTEXT": "1"
}
}This removes the 1M model variants from the model picker entirely. The configuration is officially documented in Claude Code docs under "Model configuration → Extended context."
Option 2: Cap Your Context Window
For more flexibility, you can cap the auto-compact window instead:
{
"env": {
"CLAUDE_CODE_AUTO_COMPACT_WINDOW": "200000"
}
}Anthropic recommends this approach in their recent investigation post. The example value of 200,000 tokens provides a specific cap while maintaining some extended context capability.
The Reddit post notes that these are temporary solutions and expresses skepticism about whether the 1M context window is the complete explanation for increased token usage. Users experiencing unexpected quota consumption may want to test these configurations to see if they make a difference in their specific workflows.
📖 Read the full source: r/ClaudeAI
👀 See Also

AI Agents Exposed My Sloppy Prompts: Clarity Beats Smarter Models
A Reddit post reveals that AI agents don't magically fix unclear tasks — they just make the feedback immediate. The real problem was the user's own lack of clarity.

Four local files to maintain Claude's context in long projects
A Reddit user recommends maintaining four Markdown files—claude.md, memory.md, restart.md, and backlog.md—as external memory for Claude to counteract context window compression in extended conversations.

Tell AI to Define Its Own Terms from First Principles for Better Outputs and Auditable Reasoning
A user on r/ClaudeAI found that adding a single instruction to break down undefined terms to atomic meaning before proceeding produces more specific outputs and enables debugging via a traceable reasoning chain.

Multi-Agent Orchestration in OpenClaw: Centralize Rules, Spawn Sub-Agents
An OpenClaw user describes moving from duplicated workspace instructions to a single main agent that spawns sub-agents, enforcing architectural rules (e.g., persist structured data as .JSON) across all agent workspaces.