Charlie Marsh bf2aee99c5 Avoid rollout reads for configured TUI sessions (#39731) ...

## Why

A newly started thread may not have materialized its rollout before the TUI
receives `ThreadStarted`. Trying to infer session state from that path can wait
through rollout reader retries even when a lifecycle response already provided
the authoritative session.

## What changed

- Preserve session state already stored for a known thread instead of inferring
  it again from `ThreadStarted`.
- Continue updating agent-picker metadata from the notification.
- Restrict fallback session inference to newly observed `ThreadStarted`
  notifications that do not already have session state.

## Testing

Added a startup test that verifies a known thread routes `ThreadStarted`
immediately, retains its configured session, buffers the notification, and
updates agent metadata when the rollout does not exist yet.

GitOrigin-RevId: 7ed98fb46df17566c4a61ac677f60fc8d94f7321

2026-08-20 15:42:40 +00:00

..

frames

…

src

Avoid rollout reads for configured TUI sessions (#39731)

2026-08-20 15:42:40 +00:00

tests

Remove the TUI test dependency on codex-cli (#38746)

2026-08-15 11:01:30 +00:00

BUILD.bazel

build: run buildifier from just fmt (#28125)

2026-06-13 21:43:39 -07:00

Cargo.toml

Remove the TUI test dependency on codex-cli (#38746)

2026-08-15 11:01:30 +00:00

prompt_for_init_command.md

Reduce TUI legacy core dependencies (#26711)

2026-06-09 13:26:00 -07:00

styles.md

…

tooltips.txt

Advertise the Desktop app in graphical Linux sessions (#39656)

2026-08-20 07:58:28 +00:00