Computers

A computer is a paired machine that executes sessions with its own installed CLIs and files. Paired machines run sessions on your own hardware, with the cloud used only when you choose it.

Pairing

Settings → Computers → Add computer:

1. CrossMind issues a one-time pairing token.
2. Install the daemon (or the desktop app, which ships one) on the target machine and paste the token; the browser approval page confirms the pair.
3. The machine appears Online with the runtimes it detected (Claude Code, Codex, Cursor CLI, ZCode, …).

The daemon connects outbound; no port forwarding. Removing a computer revokes its token. Re-pairing the same machine — say after a reinstall — reuses its existing entry instead of creating a duplicate.

What the host page shows

Each computer’s detail page shows:

• Runtimes: installed vs. installable CLIs, with versions.
• Subscription usage: for subscription-backed runtimes (Claude’s 5-hour/weekly windows, Codex, ZCode balance) so you can see headroom before routing work.
• Uptime & identity: how long the daemon has been connected and which machine it is.
• Daemon version: with an update offer when a release differs from what’s installed. Connected daemons also keep themselves current: when a new release ships, the backend nudges them on their next reconnect and each applies the update in an idle window, so the offer is a shortcut rather than a chore.

Routing work

Sessions reach computers via the runtime order: the cloud host always exists (no setup, uses plan quota); your machines contribute host:runtime targets. Pin an agent or a task to a specific computer when the work must run there (local files, licensed CLIs).

Cloud vs your machines

	Cloud	Your computers
Setup	None	Daemon install
Cost	Plan quota	Your CLI subscriptions
Files	Agent workspace	Your local directories
Best for	Always-on scheduled work	Private data, local tools