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

26.409.20454

What subscription do you have?

Pro 20x(10x)

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

Archiving a main thread does not archive the spawned child/sub-agent threads associated with it.

I archived parent thread 019d6f6f-c048-7283-8871-ef0a87e778ea. The parent thread is marked archived, but its spawned descendants remain live. In local Codex state, that parent has 177 child threads in thread_spawn_edges, and all 177 children still have threads.archived = 0.

Many of those child threads inherit the same original generated title, which leaves a large amount of clutter in the thread list and makes the archive feel incomplete.

What steps can reproduce the bug?

1. Start a thread that uses spawned child/sub-agent threads.
2. Let the child threads complete so they are closed but still present in local state.
3. Archive the parent thread from the Codex app.
4. Inspect the archive/live state afterward.

Observed result:

• the parent thread is archived
• the child threads remain unarchived/live
• descendant rollout/session state is still left behind

What is the expected behavior?

Archiving a parent thread should either:

1. recursively archive its spawned descendants by default, or
2. prompt the user to also archive the spawned child threads.

At minimum, the UI should make it clear that descendant threads remain live after archiving the parent.

Additional information

Example parent thread:

• 019d6f6f-c048-7283-8871-ef0a87e778ea

Local evidence:

• 177 descendants recorded in thread_spawn_edges
• all 177 descendants still had threads.archived = 0
• many descendant threads inherited the same original generated title as the parent

I can provide descendant thread IDs if useful.