Repository navigation
Error when trying to create a side thread #38248
Description
What version of Codex CLI is running?
codex-cli 0.147.0
What subscription do you have?
Plus
Which model were you using?
gpt-5.6-luna
What platform is your computer?
Linux 7.1.5-101.fc43.x86_64 x86_64
What terminal emulator and version are you using (if applicable)?
No response
Codex doctor report
What issue are you seeing?
When I tried to run /side, I got the following error: Failed to start side conversation: thread/fork failed during TUI bootstrap: thread/fork failed: failed to prepare paginated fork: thread-store internal error: thread history projection for 019feda7-ecd3-7bc3-
8ad7-2abd990775cd expected ordinal 4211, got 4210 (code -32603)
What steps can reproduce the bug?
Uploaded thread: 019feda7-ecd3-7bc3-8ad7-2abd990775cd
What is the expected behavior?
When calling /side should just open a side thread.
Additional information
No response
Activity
github-actions commentedon Aug 12, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
glook9001 commentedon Aug 12, 2026
did you tried it over a very very old thread? Better just make a fresh new threads, they change the thread systems very often and dont trust older threads.
rafaself commentedon Aug 12, 2026
No, it's a very recent thread.
glook9001 commentedon Aug 13, 2026
use the /feedback button
anywyas just make a new thread I assume the model, is still useable? or are you unable to use Codex?
nos1609 commentedon Aug 13, 2026
Confirmed that this symptom is the same underlying paginated-history failure as #35746, not limited to
/side.A separate Linux x86_64 / VS Code Web thread on Codex CLI/app-server
0.147.0preserved duplicate resume-boundary ordinals in canonical JSONL, then repeatedly failed projection with:The raw history continued growing while the paginated SQLite projection stayed frozen, so reopening the task made a large later history range disappear from the UI. Restarting the affected app-server did not recover it.
Detailed sanitized evidence and the permitted Thread/Feedback ID are in #35746:
#35746 (comment)
glook9001 commentedon Aug 14, 2026
good catch