Recorded workflow evidence
The client disconnected. The browser work stayed.
A 26-second, real-time recording of one continuity check: an MCP client disconnects, its page state survives, a new connection is refused, and the private resume key brings the same workspace back.
Recorded with a Hronaut source build · October 21, 2026
The exact sequence
Four checks in 26 seconds.
Continuity kept the work. It did not hand authority to the next connection.
- 1
Save state
A checkbox change is visible on the synthetic local page inside the Hronaut workspace.
- 2
Disconnect Client A
The MCP client disconnects. The Hronaut window, the tab, and the changed page state stay visible.
- 3
Deny implicit inheritance
A new connection supplies the workspace identifier without the private resume key. It cannot take over the workspace.
- 4
Resume explicitly
The private resume key restores the original workspace, and the saved checkbox state is still there.
Evidence boundary
This recording proves one source-build reconnect path.
It uses a Hronaut source build, a synthetic local page and MCP SDK test clients. It does not test an installer, a named AI-client integration, an application or operating-system restart, a crash, a login, a wallet, an external website or a transaction.
The current release may be newer than the recorded build. Treat the version label and these limits as part of the evidence, not as fine print.
Transcript
Read the on-screen narration.
Show the full transcript (6 lines)
- Disconnect the agent. Keep the browser.
- Agent A creates a workspace and checks an item on a local page. The page saves it.
- Agent A disconnects. Active sessions drop to zero; the tab stays open.
- A new connection lists no workspaces. The workspace ID alone is denied.
- The private resume key restores the same workspace, tab and checked item.
- Keep the workspace. Change the client.
Try the same boundary
Keep the workspace. Change the client task.
Install Hronaut, connect a local MCP client, and start with a disposable public or localhost workflow. Before you rely on it with real accounts, review the security boundary.