Recorded workflow evidence

The client disconnected. The browser work stayed.

Real Hronaut window, synthetic local page, MCP SDK test clients, original 1× timing.

Observed result

Continuity did not grant authority to the next connection.

The page state remained in the named workspace after Client A disconnected. A new MCP connection could not inherit access from the workspace identifier alone. The original private resume key restored access to that same visible workspace.

The exact sequence

Four checks in 23 seconds.

  1. 1

    Save state

    A checkbox change is visible on the synthetic local page inside the Hronaut workspace.

  2. 2

    Disconnect Client A

    The MCP client disconnects while the Hronaut window, tab, and changed page state remain visible.

  3. 3

    Deny implicit inheritance

    A new connection cannot take over the workspace by supplying its identifier without the private resume key.

  4. 4

    Resume explicitly

    The private resume key restores the original workspace and the saved checkbox state is still present.

Evidence boundary

This recording proves one source-build reconnect path.

It uses a Hronaut 2.4.24 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 product release may be newer than the recorded build. Treat the version label and limits as part of the evidence, not as fine print.

Transcript

Read the complete on-screen narration.

  1. The client disconnects. The browser work stays.
  2. Change saved in the workspace.
  3. Client A disconnects. The browser work stays.
  4. A new connection cannot inherit access.
  5. The private resume key restores the same workspace.
  6. Keep the workspace. Resume with its private key.

Watch the public Hronaut YouTube Short ↗

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.