1M context credits consumed without user selecting 1M mode

Bug Report

Summary: The error Usage credits required for 1M context was triggered mid-session without the user ever selecting the 1M context mode.

What happened

During a normal Claude Code session (Jarvis project, Phase 12 implementation), the following error appeared:

API Error: Usage credits required for 1M context · turn on usage credits at claude.ai/settings/usage, or use --model to switch to standard context

This caused the session to be interrupted and usage credits to be consumed.

What I expected

The 1M context window should only activate when explicitly selected by the user. I have used Claude Code for a while and am aware of this mode — I deliberately avoid it.

Context

• Model shown in UI at time of error: Sonnet 4.6 · Max (but I did not select Max — it appears session state may have persisted from a previous session without my knowledge)
• Model in CLI: Opus 4.8 · Low
• Plan: Max plan subscriber
• The error appeared after a few exchanges in a long-running project session

Hypothesis

It seems like a previous session's model selection (Sonnet 4.6 Max / 1M) may have persisted silently into a new session, causing the 1M context to activate without the user being aware or consenting.

Request

Please investigate whether:

1. Session state can silently switch users to 1M context without explicit action
2. There is a clear warning/confirmation step before 1M context is activated (and credits charged)

This feels like a billing issue that penalizes users who are careful about their plan usage. A confirmation prompt before switching to a paid context mode would prevent this.

---
Reported via Claude Code CLI — Date: 2026-06-01