Reconnect TUI app-server sessions automatically (#41916)

## What changed

- Reconnect out-of-process TUI sessions after the app-server transport drops, bootstrap a fresh client, and resume the active thread.
- Preserve cached transcripts, drafts, runtime settings, task-tool capabilities, and live notification routing across the new connection.
- Keep recovered or possibly submitted input paused for manual review instead of resending it, and leave conversations that cannot be resumed available as read-only cached views.
- Show reconnect progress and actionable failure states while still allowing drafts to be edited or copied.

## Testing

- Add app-level coverage for successful recovery, failed and unavailable resumes, input quarantine, and preserved session state.
- Extend the terminal integration test to verify that a draft survives reconnection, the thread is resumed without starting a turn, and notifications arrive through the replacement connection.

GitOrigin-RevId: 5dcb867c89e226a0c545d6313a77424c233cd47a
This commit is contained in:
Eric Traut authored and copyberry committed 2026-08-31 21:36:49 +00:00
1 parent 9a4b78579a
commit 907c34e867
20 files changed
+1082 -46

No files matched your search

+11
View File
@@ -370,6 +370,17 @@ impl App {
return;
}
if !self.chat_widget.has_active_view()
&& self
.current_displayed_thread_id()
.is_some_and(|id| self.thread_unavailable(id))
&& !(key_event.modifiers.contains(KeyModifiers::CONTROL)
&& matches!(key_event.code, KeyCode::Char('c' | 'd')))
{
self.chat_widget.handle_disconnected_key(key_event);
return;
}
if matches!(key_event.code, KeyCode::Esc)
&& matches!(key_event.kind, KeyEventKind::Press | KeyEventKind::Repeat)
{