What version of the Codex App are you using?
26.715.21425 (build 5488)
What subscription do you have?
Not included; this appears plan-independent.
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
When a separate Codex goal/thread is actively running, its small spinner is easy to miss because its color and contrast do not draw enough attention from the surrounding UI. A user with dry eyes or reduced visual acuity initially could not tell that the newly created background goal had started and was still running.
The animation alone is insufficient when the indicator is peripheral, small, or viewed under visual strain. There does not appear to be a setting for a more salient active-work color.
What steps can reproduce the bug?
- Start a goal in a separate Codex chat/worktree.
- Return to the originating chat or thread list.
- Observe the running-thread spinner in peripheral view.
- The indicator can visually blend into the surrounding controls, making it unclear whether the child thread is active.
What is the expected behavior?
Active background work should have a clearly distinguishable, accessible status indicator. Ideally Codex would provide:
- a configurable active/running accent color;
- a high-contrast accessibility option;
- status conveyed by more than color/animation alone, such as a persistent
Running label or stronger shape/badge;
- sufficient contrast in both light and dark themes.
Additional information
This is an attention and accessibility issue rather than a task-execution failure. Related issue #20817 discusses surfacing chats requiring attention, but does not appear to cover customizable/high-contrast running-state presentation.
What version of the Codex App are you using?
26.715.21425 (build 5488)
What subscription do you have?
Not included; this appears plan-independent.
What platform is your computer?
Darwin 25.5.0 arm64 armWhat issue are you seeing?
When a separate Codex goal/thread is actively running, its small spinner is easy to miss because its color and contrast do not draw enough attention from the surrounding UI. A user with dry eyes or reduced visual acuity initially could not tell that the newly created background goal had started and was still running.
The animation alone is insufficient when the indicator is peripheral, small, or viewed under visual strain. There does not appear to be a setting for a more salient active-work color.
What steps can reproduce the bug?
What is the expected behavior?
Active background work should have a clearly distinguishable, accessible status indicator. Ideally Codex would provide:
Runninglabel or stronger shape/badge;Additional information
This is an attention and accessibility issue rather than a task-execution failure. Related issue #20817 discusses surfacing chats requiring attention, but does not appear to cover customizable/high-contrast running-state presentation.