Repository navigation
incorrect context window % left in /status in oss mode #10858
Description
What version of Codex CLI is running?
codex-cli 0.98.0
What subscription do you have?
Team
Which model were you using?
gpt-oss:20b
What platform is your computer?
Ubuntu 22
What terminal emulator and version are you using (if applicable)?
No response
What issue are you seeing?
Incorrect ctx window "XX% left" in /status: "Context window: 89% left (14.9K used / 38K) ".
╭─────────────────────────────────────────────────────────────────────────────────╮
│ >_ OpenAI Codex (v0.98.0) │
│ │
│ Visit https://chatgpt.com/codex/settings/usage for up-to-date │
│ information on rate limits and credits │
│ │
│ Model: gpt-oss:20b (reasoning high, summaries off) │
│ Model provider: gpt-oss - http://x.x.x.x:11434/v1 │
│ Directory: /lib │
│ Approval: never │
│ Sandbox: danger-full-access │
│ Agents.md: ../AGENTS.md │
│ Account: xxxxxxx@xxxxxx (Team) │
│ Collaboration mode: Default │
│ Session: 019c3193-7aaf-70d0-a0b7-f13340366d63 │
│ │
│ Context window: 89% left (14.9K used / 38K) │
╰─────────────────────────────────────────────────────────────────────────────────╯
What steps can reproduce the bug?
- ollama
- version is 0.15.4
- on macOS, M1 32GB
- export OLLAMA_CONTEXT_LENGTH=40000
> ollama ps
NAME ID SIZE PROCESSOR CONTEXT UNTIL
gpt-oss:20b 17052f91a42e 14 GB 100% GPU 40000 Forever
- codex --oss
- on Ubuntu
- codex config:
model = "openai/gpt-oss-20b"
model_temperature = 0.0
model_context_window = 40000
model_reasoning_effort = "high"
model_verbosity = "medium"
model_reasoning_summary = "none"
model_supports_reasoning_summaries = false
model_provider = "ollama"
oss_provider = "ollama"
- try to use context
- /status
What is the expected behavior?
Correct percentage of context used.
Additional information
I suspect this also affects auto-compact.
Activity
[-]incorrect context % left in /status in oss mode[/-][+]incorrect context window % left in /status in oss mode[/+]dkhokhlov commentedon Feb 6, 2026
Findings:
The status card's "XX% left" value comes from
percent_of_context_window_remaining, which subtracts a 12,000-token baseline before calculating the percentage, creating an apparent mismatch with raw numbersThe method computes an "effective" window by subtracting
BASELINE_TOKENS(12,000) from both the total window and used tokens:effective_window = context_window - 12,000used = (tokens_in_context_window - 12,000).max(0)percent = (effective_window - used) / effective_window * 100Why 89% left appears with 40K window and ~14.9K used
With a 40,000-token window and ~14,900 tokens used:
Looks like it needs to be fixed in UI and auto-compact.
swma24 commentedon Apr 8, 2026
I can reproduce this in current Codex CLI and confirmed the root cause is a mixed metric in /status.
Example observed output:
Why this happens:
So the line combines two different denominators, which makes it look incorrect.
I prepared a fix that aligns both values to the same effective-window basis in the status card:
Patch branch (fork):
Validation run locally:
If useful, I can open an invited upstream PR from this branch.