Subagents sidebar shows worker GUIDs instead of readable names

Resolved 💬 1 comment Opened May 27, 2026 by deffenda Closed May 27, 2026

What version of Codex CLI is running?

codex-cli 0.134.0

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

In the Codex app sidebar, the Environment panel's Subagents section displays worker names as raw GUID-like identifiers instead of readable worker names or roles.

Example visible entries are truncated GUIDs such as:

019e692e-0664-7312-af12-03faf...
019e692e-07f8-76f1-90e2-27fefa...
019e692e-09cc-7090-a6c2-c1e9...
019e692e-0c62-76d0-b452-0998...
019e692e-0e4d-7c80-a5b4-91e6...

This makes the subagent list hard to scan because the user cannot tell which worker is responsible for which task. It also appears inconsistent with the expected worker/subagent UX, where workers should have a human-readable display name, role, task title, or at least a compact stable label.

The screenshot in the original report shows the Codex app left sidebar with Environment > Subagents, where every worker row is labeled with a GUID-like string.

What steps can reproduce the bug?

  1. Open Codex app / desktop UI.
  2. Start a task that spawns multiple worker subagents.
  3. Open or inspect the left sidebar Environment panel.
  4. Look at the Subagents section.
  5. Observe that each worker is displayed as a GUID-like string instead of a readable worker name.

What is the expected behavior?

The Subagents section should show readable names for workers, such as:

  • the worker's assigned role or task title;
  • a generated human-readable worker nickname;
  • a short stable label like Worker 1, Worker 2, etc.; or
  • both a readable label and the raw ID only in a details/tooltip/debug view.

Raw GUIDs should not be the primary visible label in normal UI.

Additional information

This may be related to broader subagent display-name UX, but this report is specifically about the Codex app/sidebar showing raw GUID-like worker IDs as the primary visible worker names.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗