Delegated sessions show unresolved placeholder in Codex Desktop

Open Beginner friendly
#321 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
desktop

Research direction

Start at the Codex Companion delegation flow and the session-creation path that assigns names. Trace how the delegated task identifier reaches the Codex session list, then reproduce with two or more delegated tasks. Done means each session shows a distinct meaningful task identifier instead of the unresolved placeholder.

Written by the indexing model from the issue text.

Description

Description:
When Codex Companion delegates tasks, the resulting sessions appear in the Codex session list with the generic name Codex Companion Task: <task> l... instead of replacing <task> with an actual representative identifier.

Current behavior:
All delegated sessions show identical, unresolved names like Codex Companion Task: <task> l..., making them indistinguishable from each other.

Expected behavior:
Each session should display a meaningful name such as Codex Companion Task: fix-auth-bug or Codex Companion Task: #1234, so the user can identify each task at a glance.

Impact:
When multiple tasks are running in parallel (as shown in the screenshot, up to 5 simultaneous sessions), it is impossible to tell them apart without opening each one individually.

Possible cause:
The <task> placeholder is not being interpolated when naming the session, or the task identifier is not being passed correctly at session creation time.

Steps to reproduce:

  1. Delegate 2 or more tasks using Codex Companion
  2. Observe the active sessions list in Codex
Image
Dominant language
JavaScript
Stars
33.4k
Forks
2.3k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from openai/codex-plugin-cc

All issues in openai/codex-plugin-cc

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.