Skip to main content
sesame status is your first debugging tool — it gives you an instant summary of whether your device is registered with the broker, which agents are active, and whether your JWT is still valid or needs refreshing. Run it any time something looks wrong before diving deeper.

Example output

Output fields

A colon-separated hex representation of the SHA-256 digest of your device’s Ed25519 public key. Use this to identify your device in the Sesame dashboard or when contacting support.
The total number of agent identities registered on this device. Each agent has its own keypair and JWT. Use sesame login --new to add more agents, and sesame switch <agent-id> to change which one is active for the current shell.
The agent identity currently used by sesame request. The agent marked (default) is the one set at login time. You can change it temporarily with sesame switch <agent-id>.
Whether the active agent’s JWT is valid, expiring soon, or expired, along with the remaining lifetime. Tokens are valid for 24 hours by default and can be renewed with sesame refresh.

When to run sesame status

  • After sesame login — confirm the registration succeeded and your device fingerprint matches what the Sesame dashboard shows.
  • When requests fail with auth errors — check whether your token has expired or your agent has been deactivated in the dashboard.
  • After sesame switch <agent-id> — verify the active agent changed to the one you expected.
  • Before starting a long-running agent session — make sure tokens are fresh enough to last the session, or run sesame refresh first.
If sesame status shows Token state: expired, run sesame refresh to get a new JWT via challenge-response with your device key. No browser interaction required.

CLI version

To print only the CLI version without the full status output, use:
This is useful for bug reports and confirming that an upgrade took effect.