Feature request: `--name <label>` to name a thread at start (codex / codex exec / codex fork)

What variant of Codex are you using?

Codex CLI (0.154.0, Linux aarch64)

What feature would you like to see?

A start-time flag to name the thread, e.g. codex --name <label> / codex exec --name <label> (and codex fork --name), equivalent to running /rename <label> after the first turn.

Use case

I run several Codex TUI workers in parallel from an orchestrator (one per task, each in its own terminal pane). The orchestrator later needs to address a specific worker — codex queue --thread <label>, thread/queue/add, codex resume <label>, and the codex agents dashboard all support names — but today a name can only be attached after the first turn (/rename in the TUI, or thread/name/set over the app-server), and only by first discovering the thread's UUID.

Current workaround (works, but fragile):

1. wait until the worker's first turn has run (before that /rename has nothing to persist; the thread is not yet in thread/list);
2. thread/list filtered by cwd + thread/loaded/list to find the UUID (not unique when a previous worker's thread is still loaded in the daemon);
3. thread/name/set.

A flag at start would make the name available from the moment the thread is created, so the orchestrator can use its own task id as the address without a discovery step.

Proposed behaviour

• --name <text> on codex (interactive), codex exec, codex fork; applied when the thread is first persisted, same semantics as /rename (overrides automatic thread naming; empty/whitespace rejected).
• codex queue --thread <name> currently refuses with "Cannot verify a unique session label across server pages" when the thread list is paginated; with an explicit --name that is a common case, so it would help if name lookup scanned all pages (or the check were limited to loaded threads) — happy to file that separately if preferred.

Additional information

Related: #35069 (no way to see the name after /rename — the TUI footer now shows the UUID in 0.154), #30995 (resume by name across cwds), #44093 (automatic naming).

Start by tracing argument handling for the interactive codex, codex exec, and codex fork entry points, then follow thread creation until the first persistence step. Confirm how /rename validates and stores names, and make the flag available with the same validation and override behavior across all three commands. Done means a supplied name is persisted at thread creation, while empty or whitespace-only names are rejected.