openai / openai/codex

Codex App: plan is rendered as plain assistant output when a side task is active

Open
#38,129 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug plan subagent windows-os
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.803.5235.0

What subscription do you have?

Unknown (not visible in the current task context)

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

When a side task / child task is active and shown alongside the main task, the plan in the main conversation is rendered differently from a plan in a task without side tasks.

Instead of using the normal structured plan UI and styling, Codex directly outputs the plan as ordinary assistant message content. This makes plan presentation inconsistent depending on whether the task has a side task.

What steps can reproduce the bug?
  1. Open a task in the Codex App and ask Codex to create or update a multi-step plan.
  2. Observe that the plan is displayed with the normal structured plan UI.
  3. Start a side task / child task so that it appears alongside the main task.
  4. In the main task, ask Codex to create, list, or update the plan again.
  5. Observe that the plan is directly emitted as plain assistant output instead of being rendered with the normal plan styling.
What is the expected behavior?

Plans should use the same structured plan component and styling in both cases, regardless of whether a side task / child task is active.

Additional information

This appears to be a presentation/rendering inconsistency in the Codex App rather than a difference in the plan content itself.

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 issue in the Codex App on Windows with a main task and an active side task. Trace the plan rendering path for the main conversation and compare it with the normal structured plan display. Done means plans use the same structured component and styling whether or not a child task is active.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.