Sign in where you work.

Browser access begins with a single-use email link. The CLI has its own approval flow, so you can connect a machine or attach to a cloud pane from a terminal.

Browser sign-in

Enter your email on the sign-in page. Open the single-use link in that email to continue. Your browser session is separate from a CLI credential.

CLI sign-in

Run terminalbox login and enter your email. Keep the requesting terminal open, approve sign-in in the browser, and enter the one-time code displayed there. The code is bound to that request and expires after five minutes. The saved CLI credential expires after 30 days.

~/.local/bin/terminalbox login
~/.local/bin/terminalbox host status

Use terminalbox login --email you@example.com to supply the email directly. An existing API token can be used with terminalbox login --token TOKEN; keep tokens private.

API tokens

Create and revoke tokens under Dashboard → Settings → API tokens. Use a token only where that token's scope permits; browser account and billing settings remain in the web app. If a device is lost or a token is exposed, revoke it in Settings.

Desktop client

The macOS desktop client is still a prototype. It uses a separate native sign-in scope and can operate cloud panes, connected machines, and managed sessions in development builds. Browser account administration remains a handoff. The current app is not a signed, notarized public release.