Authentication
Log in, log out, and inspect your account with login, logout, and whoami
voxal uses a browser-based login: no local web server and no copy-pasting tokens. The same flow works whether your browser is on this machine, another machine, or your phone.
voxal login
voxal login [--no-browser]Logs you in and saves a token to your machine so later commands are authenticated.
How it works
- The CLI opens the voxal sign-in page in your browser and prints a copyable link in case it cannot open one for you.
- You sign in. The page authorizes this machine.
- The CLI receives a token, saves it, and confirms you are signed in.
Login times out after 10 minutes.
Flags
| Flag | Description |
|---|---|
--no-browser (alias --manual) | Print the link instead of opening a browser. Use this when the browser is on another device, such as a phone or a remote box. |
voxal logout
voxal logoutSigns you out of this machine. The token is revoked, so a leaked copy of your local config is useless afterward, and then it is removed locally.
voxal whoami
voxal whoamiShows your email, plan, project usage (for example 2/3 projects), and your projects with
their last-deployed dates.
account you@example.com
plan Free, 2/3 projects
projects
myapp deployed 2d ago
space-game deployed 5h agoCommands that need a login but find none will tell you to run voxal login. You can also
authenticate a single command with --token <token>, which is how CI deploys work. See
voxal deploy.