openai / openai/codex

[App] Show source-task relationships in the pinned summary alongside "Created tasks"

Open
#40,270 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app enhancement session subagent
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

App for macOS, version 26.818.41509 (build 6962).

What feature would you like to see?

Summary

Please make the pinned summary a persistent navigator for the current task's source and direct task relationships.

The pinned summary already includes Created tasks and Subagents. The missing side is inbound provenance: after a task is delegated, forked, or started from another task, its source link is easy to lose because that context lives only in transcript or activity UI.

Proposed behavior

Show the applicable relationships in the pinned summary:

  • Surface the source task behind Sent by Codex from another task and make it navigable.
  • Show Parent chat for a subagent's agent thread.
  • Show Continued from chat for a fork's source chat.
  • Keep the existing Created tasks section and its Starting, Working, Done, and Failed statuses.
  • Keep completed agent threads discoverable under Subagents / Done.
  • Show Forked chat relationships created from the current chat.
  • When Voice has moved between tasks, preserve a navigable link to the previous voice task.
  • Show the related task or chat title, relationship, status, and project when relevant.
  • Open the related task or chat when selected.
  • If a relationship list is truncated, provide an expandable way to view older entries.

Please keep the relationship types distinct rather than treating every related task as a parent or child.

Why this helps

ChatGPT Voice can start separate Codex threads, check them, send follow-up instructions, and bring progress or results back to the voice conversation. Codex also has separate subagent and fork workflows.

Today, those relationships are distributed across labels such as Created task, Sent to {title}, Update from {title}, Returned from {title}, Parent chat, and Continued from chat. The pinned summary is the natural persistent place to answer:

  1. Where did this task come from?
  2. What tasks, forks, or agent threads did it create?
  3. Which task sent the current work?
  4. Where should I navigate to review the originating context?

Scope

This is not a request to merge task transcripts or make every relationship a parent/child relationship. Side chats are not the focus.

It is also not a request to use handoff as the umbrella: handoff_thread moves the same task between environments or hosts rather than representing task ancestry or cross-task messaging.

Additional information

The current App distinguishes these relationships internally:

  • Cross-task delegation: sourceThreadId, displayed as Sent by Codex from another task
  • Native subagent ancestry: parentThreadId, displayed as Parent chat
  • Fork ancestry: forkedFromId, displayed as Continued from chat

Please preserve these distinctions while surfacing them together in the pinned summary.

Official documentation:

Related but broader or different:

  • #32017 — durable parent/child task workflows and summarized handoffs
  • #35966 — Voice/text task ownership and coordination
  • #38908 — stale status in the pinned summary

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

Start with the app-server README and trace the relationship fields named in the issue: sourceThreadId, parentThreadId, and forkedFromId. Locate the pinned summary implementation and existing Created tasks and Subagents sections; done means the distinct relationships are surfaced, navigable, status-aware, and expandable where truncated.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.