`/status` isn't kept open after opening a side thread etc
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Reproduce the issue in the Codex App by starting a chat, running /status, opening a side thread with /side hello, and returning to the main thread. Trace the /status and /side entry points to find why the status info box closes, then verify that it remains open after returning to the main thread.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.928.21956
What subscription do you have?
Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
If I open a side thread /status is closed and not kept open as expected
What steps can reproduce the bug?
Start a new chat
Run /status
Run /side hello
Return to main thread and notice that the status info box is closed
What is the expected behavior?
The status info box is kept open
Additional information
N/A
- Dominant language
- Rust
- Stars
- 127k
- Forks
- 19.9k
- Avg merge
- 1m
- Merged PRs (30d)
- 996
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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
-
bug CLI tool-calls windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
openai/codex#49760 · 1 comment ·
Maintainers usually reply within 1 day
-
bug CLI exec
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openai/codex#49350 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
documentation memory
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
bug CLI
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stellar/stellar-cli#2773 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
voidzero-dev/oxc-angular-compiler#511 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
yantrikos/yantrik-os#539 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
documentation station:mac ui-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
rolter-ai/rolter#2490 · 1 comment ·
Maintainers usually reply within 1 day