openai / openai/codex

Forking does not work

Open
#41,685 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug CLI session TUI
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of Codex CLI is running?

0.151

What subscription do you have?

Pro

Which model were you using?

No response

What platform is your computer?

No response

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

No response

Codex doctor report

What issue are you seeing?

Forking no longer works in 0.151. It seems it might be the same bug that was fixed a couple versions ago, but now seems to have returned in 0.151

What steps can reproduce the bug?

Fork a thread by using /fork, then try to resume the session. The attempt at resuming will not work and instead produce the following error message

Error: Failed to resume session from ...jsonl: thread/resume failed during TUI bootstrap: thread/resume failed: thread ... already has an active writer (code -32600)

What is the expected behavior?

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure by forking a thread with /fork and then attempting to resume that session. Start by tracing the /fork and session-resume entry points around the “active writer” error; done means a forked thread can be resumed without the thread/resume failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.