Skip to content

[Bug]: Delegated Codex tasks appear as user threads in the ChatGPT desktop app's Codex sidebar #38148

Open

Description

@iby

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

  1. Install the ChatGPT desktop app with Codex, using the default ~/.codex home (shared with T3 Code's Codex provider).
  2. In T3 Code, run a task that calls delegate_task with the codex provider.
  3. Open the ChatGPT app's Codex sidebar.

Expected behavior

Delegated children stay out of the ChatGPT sidebar, the same way Codex's own spawned subagents do.

Actual behavior

Each delegated child is listed as an ordinary thread in the ChatGPT app, grouped by project. Over a few days this added dozens of "Act as the review/research/test sub-agent for this task…" threads. Top-level T3 Codex threads and side chats appear too.

In ~/.codex/state_5.sqlite these threads have source = "vscode", originator = "T3 Code", and no thread_spawn_edges parent.

Analysis

  • The ChatGPT app's sidebar hides only threads that are ephemeral, have threadSource chatgpt_hidden or ambient_suggestions, or have a parent thread (source.subagent.thread_spawn.parent_thread_id or parentThreadId).
  • 0.1.10 now sends threadSource: "subagent" for delegated threads ([Bug]: Codex delegate_task children start with no threadSource, so their MCP servers see them as user threads #36520), but the ChatGPT app doesn't filter on that value, and app-server thread/list with default sourceKinds still returns threads tagged that way (checked against existing vscode threads already carrying that tag).
  • thread/start has no parent field, so an app-server client can't currently mark a thread as a child.

Possible fixes

  • Start delegated children so Codex records them as subagents (may need upstream Codex support for a parent or source on thread/start).
  • Or start them ephemeral, at the cost of not resuming them after a restart.
  • Or offer an option to keep delegated Codex threads out of the shared home.

Related: #36520, #23652, #7090

Impact

Minor bug or occasional failure

Version or commit

T3 Code (Beta) 0.1.10

Environment

macOS, T3 Code (Beta) 0.1.10, codex-cli 0.169.0, ChatGPT desktop 26.1111.21308, provider codex (gpt-6.1-sol)

Logs or stack traces

Screenshots, recordings, or supporting files

chatgpt-codex-sidebar-t3-delegated-threads.png

Workaround

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Nov 17, 2026
  2. iby commented on Nov 18, 2026

    @iby
    Author

    Update: the delegated-child part duplicates #29778, which #34829 fixed in 0.1.10 – I missed it when filing. On my machine 0.1.10 archives each finished delegated Codex child with thread/archive 30 minutes after it goes idle (confirmed in Codex's log and thread/list), and per #34829 continuing one unarchives it. The "new ones keep arriving" line and the workaround notes above are out of date.

    What remains:

    • Side chats. A side chat is a fork of its main thread (relationshipToParent: "fork", sideChat: true), not a delegated task, so delegatedChildArchive never matches it. Its Codex thread stays in ChatGPT's list indefinitely, titled with T3's "You are in a side chat beside the main thread…" prompt. A side chat started on 0.1.10 this morning is still unarchived after more than an hour idle, and current main has the same check.
    • Pre-0.1.10 children. The archive only runs when T3 unloads a thread it has loaded, so children from earlier versions stay listed (25 here). codex archive <id> clears them, as in [Bug]: Agent-generated Codex conversations flood ChatGPT desktop Recents #29778; a one-time sweep of delivered children after upgrading would save users finding that.

    Top-level T3 Codex threads also appear in ChatGPT, but that follows from the shared Codex home and isn't what this issue is about. If side chats are meant to stay visible, this can close as a duplicate of #29778.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions