Private preview: this is rolling out and may not be available on your account yet.
The CLI is for developers. It’s mainly for people building and experimenting on Sumvin. The recommended way to use Sumvin is the MCP connector, or the API if you’re building (docs coming).An agent running in your terminal can approve Stamped Mandates that the CLI signs for you. Never give an unattended agent --yes. Sign in
The CLI never sees your password. It gives you a short code and a link, opens your browser to a sign-in page, and waits.Check the code in your browser against the one in your terminal, then approve. Once you do, the CLI finishes on its own:If your browser doesn’t open automatically, the CLI also prints a complete link with both codes built in. That link is a live credential for this sign-in — treat it like a password. Don’t paste it into a chat, a log, or a shared channel.
Confirm who you're signed in as
This checks with your account directly, so a token that’s expired or been revoked shows up honestly rather than as a stale success. Sign out when you're done
This revokes the token on your account and removes it from this machine. Running it when you’re already signed out does nothing harmful — it confirms you’re signed out. Where your sign-in lives
Signing in stores a token on this machine, valid for 90 days. It’s saved to a file only your user account can read, and it’s revoked immediately, everywhere, the moment you run sumvin logout — not just on this machine.
If you’re already signed in and run sumvin login again, the CLI asks before replacing your current token.
