Allow a Codex Desktop thread to spawn visible, running child threads

Request

I want my Chief of Staff thread in Codex to spawn new threads that I can see in Codex and see working.

Current problem

A main/home Codex Desktop thread can decide that work should be routed to a separate lane, but there is not a reliable visible flow for that thread to create and start another user-owned Codex Desktop thread.

What I am seeing today:

• codex exec can create/resume CLI sessions with thread IDs, but those sessions may not appear as normal threads in the Codex Desktop sidebar/search/history.
• codex://threads/new?prompt=... can open a new Desktop thread composer, but it does not let the managing thread create, title, start, organize, and monitor a child thread end-to-end.
• There is no clear way for a main thread to hand off context to another visible thread, pin/rename it, and then show whether that thread is actively working, waiting, done, or blocked.

Desired behavior

From an existing Codex Desktop thread, Codex should be able to:

1. Create a new user-owned thread that appears immediately in the Desktop sidebar/history/search.
2. Set the title and initial prompt/context.
3. Attach the right workspace/path, and optionally a branch or worktree.
4. Start the thread running, or queue it visibly so the user can press resume/send.
5. Return a clickable thread link/id to the parent thread.
6. Show basic status in the parent thread, such as running, waiting for user, done, or blocked.
7. Allow the spawned thread to be renamed, pinned, archived, searched, and resumed like any normal Desktop thread.

Why this matters

I want one long-lived "Chief of Staff" thread to act as my context manager. I dictate requests there, and it routes work to the right lane/thread. The important part is that I need to trust that the spawned work is visible in Codex, clickable, and actually running. Hidden CLI sessions are not enough because I cannot easily watch them or find them in the Desktop UI.

Example workflow

1. I tell my Chief of Staff thread: "send this task to the OCB Prep App lane and start it in its own worktree."
2. Codex creates a visible Desktop thread titled something like 📱 OCB - Prep App: Kitchen Helper.
3. The new thread appears in the sidebar immediately.
4. The parent thread gives me a clickable link and says whether the child thread is running or waiting.
5. I can click into that spawned thread and see the work progressing.

Related / possibly overlapping issues

This seems related to requests about CLI-created sessions not appearing as first-class Desktop threads, but this request is broader: it is specifically about Desktop parent-thread orchestration into visible, user-owned, running child threads.