Recover state and disconnect safely

Pluribus keeps local workflow identity and canonical project state separate. The private data directory preserves local bindings; the paired workspace holds the project, people, intended use, requests, responses, and review state.

Restart and recover

Restart ComfyUI with the same private data directory, reopen the workflow, and verify that the project and opaque source bindings recover.

For file-level recovery to work, the workflow must have been saved after its first Pluribus scan or project binding. That save preserves the private stable workflow key in ComfyUI metadata.

Reconnect the same owner

Pairing the same owner account again should restore its existing individual workspace and projects rather than create duplicates. After reconnecting:

1. Open the saved workflow.
2. Run Find people for the active graph.
3. Confirm the project, source links, intended-use version, and statuses match canonical state.
4. Stop if the panel asks a returning owner to create an unrelated workspace.

Disconnect safely

Choose Disconnect and wait for the server to confirm revocation. Do not treat an offline or timed-out disconnect as complete.

If the service is unavailable, the plugin keeps the local token so revocation can be retried. After successful revocation, the credential is removed while private workflow/source bindings remain for identity continuity.

Retaining those private bindings does not keep the device authorized. A later connection requires a new paired credential.

Protect the ComfyUI server

Keep ComfyUI bound to loopback or protect the entire server with trusted authentication. The plugin's same-origin local routes act with the paired device token, so the plugin inherits ComfyUI's network boundary.

An unauthenticated LAN or public ComfyUI deployment could expose project reads and plugin mutations to other clients that can reach the server.

For recovery failures and ambiguous disconnects, see Troubleshooting.