Repository navigation
[BUG] GPT-5.5 Codex uses incorrect context window #41
Description
Activity
- added a commit that references this issue
on Oct 10, 2026 @easonLiangWorldedtech Just letting you know, you keep misattributing project history to an issue that is totally unrelated and spamming my email in the process.
The rule is recorded in easonLiangWorldedtech#41 (#41 (comment)):
an await that happens after per-task state is registered belongs inside the boundary that
releases it, including awaits that look like read-only setup.- added a commit that references this issue
on Oct 10, 2026 Apologies for the noise - the five notes above were split-1066 chain history misfiled on this issue by a fork-issue numbering trap: my fork's issue #41 and this issue easonLiangWorldedtech#41 share the same number, and GitHub rewrites fork-issue references to the parent repo's issue, so the notes (and their notifications) landed here.
They have been moved to their proper homes:
- Scope re-cut for U6 -> [split-1066] U6 - fix(write-to-file): run the diff cleanup when handleError rejects #1937
- Rule: a provider-state await belongs inside the cleanup-owned boundary -> [Tracking] split-1066 chain: rules, port sources, chain-level rows #1989
- closeAllDiffViews() ordering follow-up -> [split-1066] U7 - fix(write-to-file): clean partial state on missing-param and rooignore denial #1938
- Chain-level Persistence Integrity row -> [Tracking] split-1066 chain: rules, port sources, chain-level rows #1989
- Port sources recorded for fix(write-to-file): run diff cleanup when handleError rejects (split 5/6 of #1066) #1932 -> [split-1066] U6 - fix(write-to-file): run the diff cleanup when handleError rejects #1937
Each comment above now carries a pointer to its new home (edits only - no new notifications). No further chain notes will be posted here; this issue stays about the gpt-5.5 Codex context window.
Problem (one or two sentences)
gpt-5.5in the Codex provider is configured with a1050000token context window, which GPT-5.5 does not support in Codex. This can cause Zoo to overestimate the usable context window for Codex requests.Context (who is affected and when)
This affects users selecting
gpt-5.5through the OpenAI Codex provider. It matters when longer tasks approach the provider's real context limit, since Zoo's context management uses the configuredcontextWindowvalue to decide when to condense or truncate conversation history.Reproduction steps
Expected result
gpt-5.5in the Codex provider should use the documented Codex context window of400000tokens.Actual result
gpt-5.5is configured withcontextWindow: 1_050_000, which matches a larger API-style limit and not the Codex provider limit.Variations tried (optional)
No response
App Version
zoo-code @ e58fd9b
API Provider (optional)
None
Model Used (optional)
No response
Roo Code Task Links (optional)
No response
Relevant logs or errors (optional)