[Desktop/macOS] Forked tasks retain parent metadata but lose “Continued from chat” link

What version of the Codex App are you using (From “About Codex” dialog)?

26.730.61639

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

Forking a Codex task preserves the inherited history and the parent relationship in session metadata, but the forked task no longer renders any indication that it was continued from another task.

I previously saw a clickable “Continued from chat” divider/link in forked tasks. In the current build, neither the branch point nor the task header shows a parent link. This is not conversation-data loss: the child still records the correct parent ID and contains the inherited history.

What steps can reproduce the bug?

1. Open an existing Codex task.
2. Use Continue in new chat / fork to create a child task.
3. Continue the child so the parent and child visibly diverge.
4. Open the child and inspect the branch point.
5. Observe that no “Continued from chat” divider or parent-navigation link appears.

Concrete reproduction:

• Parent task: Coordinate Build 5 email and auth
• ID: 019fdf43-8de6-79a3-91d1-f3986bbdd42e
• Forked task: Chrome as default?
• ID: 019fdf9a-0d73-7212-8158-f5dd9f558f13

The child session metadata correctly records forked_from_id = 019fdf43-8de6-79a3-91d1-f3986bbdd42e.

What is the expected behavior?

The forked task should display the clickable “Continued from chat” divider linking back to its source task. The relationship should remain visible after reopening the task, since the parent ID is still persisted.

Additional information

Feedback diagnostics were uploaded through the Codex feedback flow.

Feedback ID: 019fe192-b9ba-7bd1-aa0e-d11d114031c8

Local inspection found that:

• The fork's persisted forked_from_id is correct.
• The installed frontend still includes the localConversation.forkedFromConversation component with the default label “Continued from chat.”
• Current task-list/read projections do not expose the lineage marker needed to render that component.

This suggests a metadata-to-history projection or hydration regression rather than a failed fork.

Possibly related to #37588: both involve persisted task metadata failing to reach the appropriate UI surface, although #37588 concerns title persistence during archival and this report concerns fork-lineage navigation.

No screenshots are attached because the available screenshots include unrelated private task content; the textual reproduction and Feedback diagnostics contain the relevant evidence.