Repository navigation
Open
Labels
bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.
Description
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
- Install the ChatGPT desktop app with Codex, using the default
~/.codexhome (shared with T3 Code's Codex provider). - In T3 Code, run a task that calls
delegate_taskwith thecodexprovider. - 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
threadSourcechatgpt_hiddenorambient_suggestions, or have a parent thread (source.subagent.thread_spawn.parent_thread_idorparentThreadId). - 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-serverthread/listwith defaultsourceKindsstill returns threads tagged that way (checked against existingvscodethreads already carrying that tag). thread/starthas 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
- Archiving the threads in ChatGPT hides them, but archived sessions then drop out of T3's usage page ([Bug]: Usage page never scans Codex archived_sessions/, so archived sessions' usage silently disappears #7090), and new ones keep arriving.
- A separate
CODEX_HOMEfor the Codex provider loses the shared config, hooks and bundled plugins, and hides all of T3's Codex threads, not just delegated ones. - A shadow home still shares the thread store, so the threads still appear (see [Bug]: Codex instances with a shadow home lose Computer Use and other bundled plugins #23652).
Metadata
Metadata
Assignees
Labels
bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.
Activity
iby commentedon Nov 18, 2026
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/archive30 minutes after it goes idle (confirmed in Codex's log andthread/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:
relationshipToParent: "fork",sideChat: true), not a delegated task, sodelegatedChildArchivenever 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 currentmainhas the same check.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.