Dual sessions branching from a single session after another session sends a message to it
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No source files or tests are named. Start by tracing session interruption and automatic compaction handling, then investigate the race when a message arrives during compaction. Done means the interrupted session does not split into pre- and post-compaction sessions running concurrently; a reliable reproduction or regression test is needed.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.715.31925
What subscription do you have?
max
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
SessionA: 019f793c-0bfb-7221-adb4-c72c5d59f66c
was running, and another sessionB: 019f7b8c-8323-7533-ade2-5d03bdf35c77
Interrupts it with a message.
SessionA had compacted, and the pre-compaction session received the message and started to go on its own
while the post-compacted session kept on going.
The codex UI looked like it had 2 sessions going simulatenously split by the Context automatically compacted message.
What steps can reproduce the bug?
Not sure, I think it happened because the message was sent while the compaction was happening but cannot verify.
What is the expected behavior?
No split
Additional information
No response
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
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.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·