Benjamin Carlsson 6f47fcb0be Route TUI request replies to their originating connection and thread (#53436) ...

## Why

Pending requests can outlive a session switch, and different threads or connections can reuse request IDs. Replies and resolution notifications must stay associated with the request that prompted them.

## What changed

- Retain the original app-server reply handle for pending and buffered requests, including requests replayed after thread attachment or session reset.
- Scope user input, MCP elicitation, and user verification bookkeeping by thread, and send user input answers to the requesting thread.
- Keep background resolution notifications from dismissing foreground prompts.
- Consume failed replies to closed connections and clear pending replay state without falling through to another request route.

## Testing

Add WebSocket regression tests for direct and buffered approvals with colliding request IDs and replies to closed connections. Extend coverage for foreground prompt preservation and thread-scoped user verification cancellation.

GitOrigin-RevId: 541acb9910e92f6f2e83c27d2a2384185d4f8fec

2026-10-12 17:39:17 +00:00

..

assets

Normalize formatting in docs, web assets, and sample scripts (#52256)

2026-10-08 20:11:43 +00:00

src

Route TUI request replies to their originating connection and thread (#53436)

2026-10-12 17:39:17 +00:00

tests

Limit daemon feature compatibility checks to explicit CLI overrides (#52648)

2026-10-09 17:15:58 +00:00

BUILD.bazel

Add an animated Codex logo to fresh conversations and onboarding (#46752)

2026-09-20 03:02:48 +00:00

Cargo.toml

Classify voice session failures and record terminal outcomes (#52756)

2026-10-10 02:54:59 +00:00

styles.md

Normalize formatting in docs, web assets, and sample scripts (#52256)

2026-10-08 20:11:43 +00:00