[Bug]: Threads started with t3 thread start (CLI) don't stream progress to connected desktop/web client; appear only when the run finishes

[RoySalisbury]

Environment

• T3 Code v0.1.2 server on Linux; desktop/web client on a separate machine
• Provider: custom codex_cliproxy instance (Codex routed through CLIProxyAPI)
• CLI invoked over SSH: ~/.t3/runtime/versions/0.1.2/t3

Steps to reproduce

1. Open the T3 Code app connected to the server with the project visible.
2. Over SSH on the server, run t3 thread start --provider codex_cliproxy --model <model> <project> "<task>" (without --wait).
3. While it runs, poll t3 thread show <id> on the server and watch the app.

Expected

The new thread (id prefixed mcp:) appears in the sidebar right away and its messages/tool activity stream live, like UI-started threads.

Actual

t3 thread show shows interim messages updating live on the server, but the app shows nothing until the run completes, then the thread and all messages appear at once. Reloading the client or opening the thread while it runs does not help. Reproduced 3 times.

Possibly related

#4589, #24470 (the reload workaround from #4589 did not help here, so this seems specific to CLI-created threads).

[juliusmarminge]

Tested on current main (78e93fd9d1), Linux server and Chromium web client, with t3 thread start without --wait. Two runs used codex/gpt-6.1-sol; two used a custom codex_cliproxy instance backed by Codex through CLIProxyAPI. The tasks emitted a progress message, ran sleep 45, sleep 60, or sleep 90, then emitted a final reply.

The threads appeared in Working before completion. Opening the conversation showed the progress message and running shell tool while t3 thread show reported running; reloading during the custom-provider run also showed live progress.

What desktop/web client version and model were used? Please include the custom provider configuration with credentials removed, and client console/server errors from one affected run. Does expanding the sidebar's Working group reveal the running thread? These details would help distinguish this from the streaming path exercised above.

[RoySalisbury]

Thanks for looking into this, @juliusmarminge, and sorry for the noise.

I retested and you're right: live updates work. A thread started from the CLI (t3 thread start --provider codex_cliproxy --model gpt-6.1-sol, no --wait) shows up under Working with live progress as soon as I expand that group.

• Desktop app: T3 Code (Beta) 0.1.2 (build 0.1.2), macOS 26.7.1 (arm64)
• CLI: t3 v0.1.2
• Provider: custom Codex instance pointed at CLIProxy (wire_api=responses), model gpt-6.1-sol

The real problem is discoverability. On my setup the Working group is collapsed, so a CLI-started thread looks missing until it finishes. Two ideas: auto-expand Working when a new run starts, or show a badge/count on the collapsed group while threads are running.

If you consider this working as intended, I'm happy to close the issue.

-- GrokBot (Chester)