Connect saved machines concurrently in the chat workspace

This commit is contained in:
2026-11-08 22:21:17 +00:00
parent 663d5fb5c9
commit e4904395f0
44 changed files with 2574 additions and 60 deletions
+41
View File
@@ -0,0 +1,41 @@
# Concurrent saved-machine chats
The chat destination now owns independent connections to every saved logical
machine. It combines their sessions using namespaced UI identities, retaining
native IDs only on each machine's protocol connection. Models, permissions,
messages, task/automation metadata, exports, uploads and file browsing stay on
the originating connection. A disconnected machine never falls back to another.
Cached rows remain visible while a machine retries; removing a profile drops its
rows and rejects late responses. Retained adapters are revoked immediately when
a connection changes, before asynchronous socket cleanup finishes.
Browsers keep the hosting-origin socket and register other machines through the
authenticated same-origin relay. Peer credentials remain in server memory; native
profiles use independent credential snapshots. Successful Settings sign-in/out
refreshes only that machine's connection. Failed passwords preserve existing
credentials, and late sign-in replies cannot authenticate edited/removed profiles.
Each row/thread shows its own editable machine alias. Creating a chat with
multiple machines loads harnesses/directories from the chosen machine without
changing the pipelines/runs default or closing other chat panes. One machine
skips the picker. Primary authentication failure no longer hides healthy peers.
The combined workspace migrates previous primary panes once and then persists
independently of the pipelines/runs default. Scoped drafts/unsent intents retain
native storage keys, and hidden/read list choices migrate without ID collisions.
Protocol-owned session IDs are rewritten; opaque tool input/results and user form
answers are preserved verbatim. Read acknowledgements split by machine.
Verification at source freeze: 47 focused integration tests pass (out.85WaSh),
including all previously failing application fixtures, native loopback cookie
isolation, late authentication, pool cancellation races, ID collisions, primary
auth isolation, machine-first creation and persistence migration. Analyzer clean
(8aaMr2). An earlier broad chat/core/application run had 1128 passes and 11
failures; callback validation and legacy fixtures were fixed, and all failing
areas passed the focused rerun. A final broad rerun and real two-server browser
capture are the manager's remaining acceptance checks. No production sessions,
services or physical devices were changed here.
The legacy correlated application fixtures now explicitly answer automation
metadata as unavailable and disable native update probes. They previously left
those independent requests unanswered, blocking history or leaving timers alive.