Docs / Getting started

Log in and activate a machine

Updated

TL;DR — `tokenade login` opens tokenade.net, you approve the device, and a signed license is cached in `~/.tokenade/license.key`. Use `--no-browser` on a server.

To activate Tokenade on a machine, run tokenade login and approve the request in your browser. Tokenade needs an active account on every machine where it runs: until the machine is activated, it does not compact anything.

tokenade login

No account yet? Create one at tokenade.net/signup. The free plan needs no card; see pricing for plan limits.

How the device flow works

tokenade login asks tokenade.net for a one-time code, prints the approval URL and the code, and opens the URL in your default browser:

To activate Tokenade, authorize this machine in your browser:

https://tokenade.net/activate?code=ABCD-EF23

(verification code: ABCD-EF23)

Waiting for you to authorize… (Ctrl-C to cancel)

Sign in on that page if needed, check that the code matches, and approve within 10 minutes (the code's lifetime). The terminal checks every 3 seconds and finishes on its own:

✓ This machine is now activated.
plan: free · quota: … tokens saved (this month)
manage machines / upgrade at https://tokenade.net/dashboard

If no coding agent is wired yet, login then runs tokenade install for you ("Wiring up your coding agents so the savings actually kick in"). If agents are already configured, it says so and changes nothing.

On a server or over SSH

Use --no-browser to skip opening a browser. Tokenade prints the URL; open it on any device (your laptop, your phone), approve, and the server picks up the approval.

tokenade login --no-browser
FlagEffect
--no-browserDon't auto-open a browser, just print the URL
--help, -hShow the help

When login fails

MessageWhat to do
✗ Authorization was declined in the browser.Run tokenade login again and approve
✗ This request expired. Run tokenade login again.The code expires after 10 minutes; start over
✗ Timed out waiting for authorization.Same: run tokenade login again
✗ Machine limit reached: …Your plan's machine cap is reached (Enterprise seats); free a slot at tokenade.net/dashboard or add seats

The license file

A successful login caches a signed, machine-bound license at ~/.tokenade/license.key (%USERPROFILE%\.tokenade\license.key on Windows). The license is signed by tokenade.net and verified locally, so Tokenade does not need the network on each call.

  • The cached license is valid for about 30 days and is renewed automatically by the background usage reporter. You never re-run login for that.
  • tokenade healthcheck shows the state on its license active row, with your plan and this month's usage.

Staying connected

Tokenade reports anonymous usage counts to tokenade.net (see What Tokenade sends and stores). A short outage is fine: you can work offline. If reports keep failing for more than 72 hours, Tokenade pauses, the same way it does when a quota is used up. It resumes on its own at the first successful sync once tokenade.net is reachable again.

Machines

  • Free and Pro: unlimited machines.
  • Enterprise: seat-based, 3 machines per seat.

Run tokenade login once on each machine. You see and manage all of them at tokenade.net/dashboard.

Unlinking a machine

There is no logout command. To unlink a machine, either:

  • Remove it from the dashboard. At its next report, the server answers 403 with MACHINE_REVOKED, Tokenade deletes the cached license and quota, and stops compacting until you run tokenade login again.
  • Uninstall Tokenade on it. tokenade uninstall deletes ~/.tokenade/, including license.key. To also free the machine from your account, delete it at tokenade.net/dashboard. See Upgrade and uninstall.

Referral codes

If someone gave you a referral code, pass it at install time:

tokenade install --ref <code>