Error: "state db missing rollout path" received when running codex exec resume <SESSION_ID> "..."

What version of Codex CLI is running?

codex-cli 0.99.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.3-codex

What platform is your computer?

Darwin 23.5.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

iTerm

What issue are you seeing?

I see the error:

2026-02-12T20:29:52.847775Z ERROR codex_core::rollout::list: state db missing rollout path for thread 019c538b-8d9d-78d1-891c-a9b09f3f47b6

When I try and resume a session that I've just created via codex exec

What steps can reproduce the bug?

Following a fresh wipe:

rm -rf ~/.codex

Once I log-in to Codex, I run:

codex exec "hi"

The output is:

OpenAI Codex v0.99.0 (research preview)
--------
workdir: /Users/timlonsdale/Code/halls
model: gpt-5.3-codex
provider: openai
approval: never
sandbox: workspace-write [workdir, /tmp, $TMPDIR]
reasoning effort: none
reasoning summaries: auto
session id: 019c538b-8d9d-78d1-891c-a9b09f3f47b6
--------
user
hi
mcp startup: no servers
codex
Hi.
tokens used
1,368
Hi.

I try and resume the conversation via:

codex exec resume 019c538b-8d9d-78d1-891c-a9b09f3f47b6 "hi"

And I see the following output:

2026-02-12T20:29:52.847775Z ERROR codex_core::rollout::list: state db missing rollout path for thread 019c538b-8d9d-78d1-891c-a9b09f3f47b6
OpenAI Codex v0.99.0 (research preview)
--------
workdir: /Users/timlonsdale/Code/halls
model: gpt-5.3-codex
provider: openai
approval: never
sandbox: workspace-write [workdir, /tmp, $TMPDIR]
reasoning effort: none
reasoning summaries: auto
session id: 019c538b-8d9d-78d1-891c-a9b09f3f47b6
--------
user
hi
mcp startup: no servers
codex
Hi.
tokens used
3,863
Hi.

Specifically, I see the error:

2026-02-12T20:29:52.847775Z ERROR codex_core::rollout::list: state db missing rollout path for thread 019c538b-8d9d-78d1-891c-a9b09f3f47b6

I have confirmed that ~/.codex/sessions/2026/02/12/rollout-2026-02-12T20-29-40-019c538b-8d9d-78d1-891c-a9b09f3f47b6.jsonl exists as a file

What is the expected behavior?

I expect to not see any error

Additional information

rollout-2026-02-12T20-29-40-019c538b-8d9d-78d1-891c-a9b09f3f47b6.txt