Persist draft message after interrupt followed by fork/resume session
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
0.152.1
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?
If I draft a message but interrupt by pressing Ctrl-C, the message will persist if I do not switch session but lost after a fork/resume, even if I later resume the same original session. This is inconvenient as sometimes users would draft a message half-way and realize that the work might be better done in a forked session or new session but after forking the message draft is lost.
What steps can reproduce the bug?
Draft a messag, interrupt by pressing Ctrl-C, and then fork or resume.
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in Codex CLI 0.152.1: draft a message, press Ctrl-C, then fork or resume the session. Trace how the draft is retained across those transitions; done means the interrupted draft remains available even after forking and resuming the original session.
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
- 58/100