openai / openai/codex-plugin-cc

Delegated sessions are not renamed with a representative identifier in Codex

Open
#283 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
33.3k
Forks
2.3k
PR merge metrics
No merged PRs in 30d

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

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.

Research direction

Start by tracing where Codex Companion creates sessions for delegated tasks and how the session name containing the placeholder is assembled. Reproduce the issue with two or more delegated tasks, then verify that each session displays a meaningful task identifier in the Codex session list.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.