What version of the Codex App are you using (From “About Codex” dialog)?
26.623.31921
What subscription do you have?
Plus
What platform is your computer?
Darwin 24.6.0 arm64 arm
What issue are you seeing?
In the newest update to the Codex app now when reading Plans they only open in the /side panel. This is not good UX. If I want to read the Plan and suggest a change in the "No, and tell Codex what to do differently..." box, this shrinks, and prevents text input.
Also, now while Codex writes plans, it now also appears as if text streaming has stopped, and this makes the app feel like it is hung or non-responsive.
Please just revert this to the old behavior of being able to expand Plans and read them in the thread. Plans are Codexes most powerful feature and this makes it worse for no reason.
Plans do not belong there.
What steps can reproduce the bug?
- Have Codex write a Plan
- Click the Plan -> Nothing happens during generation -> Feels like app has stalled.
- Codex finishes writing Plan -> Opens unwanted side panel
- With unwanted side panel open -> Attempt to write text in the "No, and tell..." box -> box is not wide enough to support input text.
What is the expected behavior?
No response
Additional information
No response
What version of the Codex App are you using (From “About Codex” dialog)?
26.623.31921
What subscription do you have?
Plus
What platform is your computer?
Darwin 24.6.0 arm64 arm
What issue are you seeing?
In the newest update to the Codex app now when reading Plans they only open in the /side panel. This is not good UX. If I want to read the Plan and suggest a change in the "No, and tell Codex what to do differently..." box, this shrinks, and prevents text input.
Also, now while Codex writes plans, it now also appears as if text streaming has stopped, and this makes the app feel like it is hung or non-responsive.
Please just revert this to the old behavior of being able to expand Plans and read them in the thread. Plans are Codexes most powerful feature and this makes it worse for no reason.
Plans do not belong there.
What steps can reproduce the bug?
What is the expected behavior?
No response
Additional information
No response