Failed /BTW fork - Code 32603
Open 💬 2 comments Opened Aug 11, 2026 by JDLondon7
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
0.147.0
What subscription do you have?
Pro
Which model were you using?
5.6 Sol Medium
What platform is your computer?
Linunx -Arm64 - Debian
What terminal emulator and version are you using (if applicable)?
_No response_
Codex doctor report
What issue are you seeing?
Error message
What steps can reproduce the bug?
Uploaded thread: 019fe808-217e-7942-820f-76c818f3bd85
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Code
-32603is the JSON-RPC internal-error code the app-server returns whenthread/forkfails, and/btwruns exactly that. The most common cause on 0.147 is the thread-history projection invariant failing during the paginated fork — diagnosed in #38317 (expected ordinal N, got N-1, fromthread-store/src/local/thread_history_materialization.rs), with the same defect also breaking resume (#38552) and hiding threads fromcodex resume(#38341).If you still have the session, the exact message would confirm it: the error line above the
-32603should readfailed to prepare paginated fork: thread history projection for <thread-id> expected ordinal …. If it says something else, that's worth pasting here — but if it matches, this is a duplicate of #38317 and the fix there (idempotent duplicate-ordinal skip + projection rebuild on invariant failure) covers it.