Skip to main content
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.
Every command below accepts the global flags: --api-url, --json, --debug, --help.

sumvin login

Signs in using a device code: the CLI shows you a code and a link, you approve in your browser, and the CLI stores a token on this machine once you do.
Flags Output states
  • A fresh sign-in prints a code and a link, then Signed in. Token expires <date>. once you approve.
  • If you’re already signed in, the CLI asks before replacing your current session.
  • If the code expires before you approve, the CLI reports the sign-in as expired and you re-run it.

sumvin logout

Revokes the stored token on your account, then removes it from this machine, in that order.
Output states
  • Signed in: Signed out.
  • Already signed out: Already signed out. — this is not an error; running logout when there’s nothing to sign out of is a no-op.
  • If your account can’t be reached, the local copy is still removed. Revoke the token from the Sumvin app as well if that matters to you.

sumvin whoami

Shows the session you’re currently signed in with, checked live against your account rather than read from a local file.
Output states
  • Signed in: name, status (active, revoked, or expired), expiry, and when it was last used.
  • Not signed in, or the stored session no longer works: You're not signed in.

Exit codes

All three commands use 0 for success and 1 for failure — there is no “answer is no” case here, only “the run worked” or “it didn’t.”