[BUG] GPT-5.5 Codex uses incorrect context window #41

Activity

1. jaszhix

   added

   bugSomething isn't workingSomething isn't working

   on May 9, 2026
2. taltas

   closed this as completedin #42on May 9, 2026
3. easonLiangWorldedtech

   added a commit that references this issue on Oct 10, 2026

   fix(write-to-file): cover the pre-streaming window and discard withou…

   ...

   19e8512
4. jaszhix commented on Oct 10, 2026

   

   jaszhix

   on Oct 10, 2026

   ContributorAuthor

   More actions

   @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.
5. easonLiangWorldedtech

   added a commit that references this issue on Oct 10, 2026

   fix(write-to-file): keep rollback honest when the discard itself fails

   ...

   8084eab
6. easonLiangWorldedtech commented on Oct 10, 2026

   

   easonLiangWorldedtech

   on Oct 10, 2026

   Last edited by easonLiangWorldedtech

   Contributor

   More actions

   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.