[Bug]: Remote Agents panel shows 9 subagents while host shows 17 for the same thread

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

1. Run a Codex thread with multiple direct subagent spawns in T3 Code on a MacBook Pro.
2. Open that same MacBook-hosted thread through a remote T3 Code session on a Mac Studio.
3. Compare the Agents panels on the two clients.

Observed in the supplied screenshots: the host panel shows 17 idle direct spawns, while the remote panel shows only 9. The exact trigger for the omission has not been isolated; these are observations from an existing session, not a deterministic minimal reproduction.

Expected behavior

The host and remote clients viewing the same thread should expose the same complete direct-spawn roster and consistent aggregate counts once synchronized.

Actual behavior

The remote client shows 9 idle agents and a 12.8M token total. The host client shows 17 idle agents and a 62.3M token total. All 9 entries visible remotely also appear on the host.

The 8 entries absent remotely are: workflow_contract, daemon_catchup, delivery_performance, catchup_health_order, unfetched_next_step, durable_blocker_next_step, guidance_handoff, and incoming_example.

The screenshots were taken at different moments, so elapsed times are not directly comparable. The missing roster entries and different counts are the reported failure; no root cause or fixed nine-agent limit has been established.

Impact

Minor bug or occasional failure

Version or commit

T3 Code (Nightly) 0.0.43-nightly.20260916.1811 on both machines: the MacBook Pro host and the Mac Studio remote client.

Environment

macOS; T3 Code host on MacBook Pro and remote client on Mac Studio; Codex provider.

Logs or stack traces

Screenshots, recordings, or supporting files

SCR-20260916-kkjk.png
download.png

Workaround

No response

Start in apps/web by reproducing the same-thread comparison between the MacBook host and Mac Studio remote client using the supplied screenshots and version details. Trace how the Agents panels receive and aggregate direct-spawn data, then verify that both clients show the complete roster and matching counts once synchronized.