> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sumvin.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign in

> Connect the CLI to your Sumvin account and check who you're signed in as.

export const waitlists = {
  earlyAccess: "",
  payments: "",
  openBanking: "",
  developers: "",
  verifiers: ""
};

<Note>
  **Private preview:** this is rolling out and may not be available on your account yet.{waitlists.earlyAccess ? <> <a href={waitlists.earlyAccess}>Request early access →</a></> : null}
</Note>

<Warning>
  **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](/get-started/connect), 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`.
</Warning>

<Steps>
  <Step title="Sign in">
    ```bash theme={null}
    sumvin login
    ```

    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.

    ```text theme={null}
    To sign in, visit:
      https://…
    and enter the code:
      WDJB-MJHT
    Check the code shown in your browser matches the one above.
    ```

    Check the code in your browser against the one in your terminal, then approve. Once you do, the CLI finishes on its own:

    ```text theme={null}
    Signed in. Token expires 2026-09-29.
    ```

    <Warning>
      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.
    </Warning>
  </Step>

  <Step title="Confirm who you're signed in as">
    ```bash theme={null}
    sumvin whoami
    ```

    ```text theme={null}
    Signed in as sumvin-cli@my-laptop
      Status:     active
      Expires:    2026-09-29 14:02:11 UTC
      Last used:  2026-08-05 09:41:55 UTC
    ```

    This checks with your account directly, so a token that's expired or been revoked shows up honestly rather than as a stale success.
  </Step>

  <Step title="Sign out when you're done">
    ```bash theme={null}
    sumvin logout
    ```

    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.
  </Step>
</Steps>

## 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.

<Tip>**Next:** [Give your agent the CLI](/get-started/cli/with-your-agent), or see the [command reference](/reference/cli/auth).</Tip>