Claude Desktop remote.

Why this needs no setup

Claude Desktop connects with its own SSH client, which honors your SSH config but does not present the SSH certificates Prized's terminal ssh authenticates with. Prized closes that gap: prized login registers this machine's SSH public key with your workspace, and every box accepts it as a restricted fallback. Terminal ssh never uses the fallback.

Connect the box

1. Log in once on this machine (prized login, part of the normal quickstart). Boxes pick up the device key within seconds.
2. In Claude Desktop, add the box as an SSH host by its hostname, for example box-3fa9. The stanza Prized installs supplies the tunnel and the key; if the app asks for an identity file, use ~/.config/prized/id_prized.

ssh box-3fa9
# confirms the connection from a terminal first

What the fallback key can do

The key the app authenticates with is deliberately narrower than a certificate:

The key is accepted only from inside your authenticated Prized tunnel, so a copy of the key file is useless on its own.

Removing a device

Delete the device's CLI token, or remove the member from the workspace; every box drops the key within seconds. A device silent for 45 days ages out on its own and re-registers when it next connects.

Caveats

• Wake the box first. The app's plain ssh does not wake a suspended box. Resume it from the dashboard or run prized ssh once, then connect.
• The app stops when your machine sleeps. For an agent that keeps working with the laptop closed, run Claude Code on the box in a session instead.
• Password prompt? The box has not synced the key yet: make sure prized login ran here, give it a minute, retry; prized doctor checks the rest.