Bi-directionally sync T3 chat threads with provider threads #876
Description
Problem
T3 chat threads currently sync one way with the source provider.
- Threads created in T3 are visible inside the Codex CLI
- Threads and in-progress activity created in the Codex CLI are not visible inside T3 Code
Desired behavior
Thread state should bi-directionally sync with the source provider so T3 and the provider UI/CLI stay aligned.
Specifically:
- Threads created or resumed in Codex CLI should appear in T3
- Progress/events produced in the Codex CLI should be reflected in the corresponding T3 thread
- T3 should stay in sync when work continues outside the web app
Why this matters
Right now T3 can act as a source of threads for Codex CLI, but it cannot reliably reflect work that happens in the CLI afterward. That breaks continuity between the two surfaces and makes T3 an incomplete view of session history and live progress.
Acceptance criteria
- A thread started in T3 is visible in Codex CLI
- A thread started or resumed in Codex CLI is visible in T3
- New messages/progress from either side appear in the other side without manual reconciliation
- T3 can represent ongoing provider-side progress, not just final thread state