SOLWYN
Commands

whoami

Inspect the selected credential, account role, email verification, and reachable projects.

Terminal
solwyn whoami
solwyn --json whoami

whoami names the credential in use first: Credential: CLI login dev-laptop (read, contain), expires 2026-11-29 for a Solwyn login, or Credential: API key (environment) for a key. Check it before a role-restricted change.

With a login, whoami also reads your identity, the current account and the projects you can reach. solwyn.whoami.v1 keeps email_verified, first name and marketing-email subscription state, account ID, role, seats and projects. auth_type is login or project_key, and credential carries the kind, source, location, label, scope and expires_at. source and auth_source are keyring, file or environment, and the table's Stored in row names the store and path. For a SOLWYN_TOKEN login, whoami reads the label, scope and expiry from the API. configured_project is the selected project (--project, SOLWYN_PROJECT or .solwyn.env) for a login as well as for an API key.

When the keychain is the store in use but the credentials file still holds credentials for this API, whoami says so on stderr and suggests solwyn logout, which clears both stores. When the file is in use, it never probes the keychain.

With an API key, it returns the local credential source and configured project with no network call. It does not prove the key is valid or invent a user, account role or verified email, and never reveals raw key material. Use doctor for an authenticated read. MCP provides get_whoami in both profiles. Its configured_project is the server's launch project, the one the metering tools spend from, and stays that project if .solwyn.env changes later, until the server restarts.

Exit codes: 0 success, 1 API/invalid response, 2 usage, 3 auth. For user commands, SOLWYN_TOKEN comes first, then the stored login, then SOLWYN_API_KEY and the stored API key, so a key no longer hides a login. See Scoped login for the order and SOLWYN_AUTH.

If you were removed from the account, logging in again won't help. Create a personal account in the dashboard at app.solwyn.ai/no-account, then run solwyn login. Email verification and changes use the dashboard.