tofupilot login

Last updated on November 19, 2026

The login command authenticates the CLI. The default flow opens a browser to log in as a user; the --token flag switches to a headless setup token that registers the machine as a station.

login
tofupilot login

A user login on a machine that is a station turns it back into a development machine, as tofupilot logout --station does: the station service stops, its queued runs upload as the station, and its login, pulled deployments and desktop icon are removed. While a station process is still running, the login succeeds and keeps the station, and says what to stop. Log in with --token again to make it a station.

--url <URL>

Override the dashboard URL, which defaults to https://www.tofupilot.app, so you can log in against a self-hosted dashboard.

self-hosted login
tofupilot login --url https://tofupilot.acme.internal

--org <SLUG>

When you already know the organization slug, pass --org to skip interactive organization selection.

org login
tofupilot login --org acme

--token <TOKEN>

To authenticate as a station with a one-hour setup token issued by the dashboard, pass --token. The flow is headless, so no browser is required, and the flag conflicts with --org.

headless station install
tofupilot login --token <setup-token-from-dashboard>

--ca-cert <PATH>

On a self-hosted instance behind a private CA, pass the CA bundle (PEM, root plus intermediates) to trust. The path is saved with the credentials and reused by every later command and by the station daemon. A file that cannot be read, or that holds anything but CA certificates, makes the login fail. Re-logging in to the same server without the flag keeps the saved CA; an empty value clears it; TOFUPILOT_CA_CERT=<path> overrides it for one command.

private CA from a file
tofupilot login --url https://tofupilot.acme.internal --ca-cert /etc/tofupilot/ca/ca-root.pem

--ca-cert-sha256 <HEX>

The form the dashboard install command uses when the instance publishes its CA. The CLI fetches /api/instance/ca.pem from the instance, refuses it unless its SHA-256 matches, stores it under ~/.tofupilot/ca/ and logs in with full certificate verification. Requires an https:// URL and cannot be combined with --ca-cert. See Private CA.

private CA pinned by fingerprint
tofupilot login --url https://tofupilot.acme.internal --token <setup-token> --ca-cert-sha256 <fingerprint-from-the-dashboard>

How is this guide?

On this page