Support and recovery

Sign in and manage accounts, workspaces, devices, and client connections.

Account recovery

Keep the independent account recovery credential in a password manager. Sign in with it, or use an existing authenticated product browser session to rotate it. Rotation can optionally sign out other browser sessions without changing device credentials or OAuth grants. A claimed device credential cannot replace account login. There is no email-based recovery or automatic identity merge.

Reconnect an existing device

Run the remote command with the same installation state and server settings. Reuse valid credentials; do not delete private state to fix a temporary outage. Request a new pairing code with pair when needed. Codes are short-lived and single use; already claimed devices require their authenticated owner account.

Workspace and device access

A product workspace role permits only workspace administration or membership. Native access additionally requires an explicit grant from the device owner. Shared roles are confined to approved Linux workspace directories and exclude shell, process, browser, and transfer operations. Select the intended product workspace before new client consent. Role changes and restored memberships require fresh consent; removing a workspace membership does not erase a separate direct device share in a personal workspace.

Inspect an uncertain operation

Use the operation identifier with operation_get, or inspect its native process handle while authorized. A timeout or cancellation request does not prove that the native effect did not occur. Inspect the outcome before retrying a mutation.

Revoke or restore access

Revoke one device, membership, or client connection through the account page. Restoring a device does not restore old OAuth permissions for it. Restart its saved runtime and authorize new consent. Unrelated devices and connections remain separate.

Installation and updates

Install Node.js 22.12 or newer. Update through the public package command while retaining private installation state, then explicitly reinstall persistent runtime source if used. Stop the old runtime before replacing it against the same state directory. Installation commands.

Billing

No payment provider or paid plans are configured. Current plan status. This self-service page does not promise a staffed response time.