---
title: Check your session
description: See which account you are signed in as, and which workspace is active.
cli_command: wiblo whoami
canonical_url: https://wiblo.app/docs/developers/cli/authentication/whoami
last_updated: 2026-07-28T17:12:38+02:00
md_url: https://wiblo.app/docs/developers/cli/authentication/whoami.md
---

# Check your session

`$ wiblo whoami`

## Usage

```bash
wiblo whoami
```

```text
$ wiblo whoami
Signed in as Matt Pryce (usr_01J8...)
Active workspace: acme-studio
```

## Flags

| Flag | Description |
| --- | --- |
| `--json` | Print the identity as JSON: `{ "actor": { "type": "user", "id", "email", "name", "role" }, "workspace": ... }` |
| `--workspace` | Report against a specific workspace (slug or id) instead of the active one. |

## Behaviour

- `whoami` is **user-scoped**: it works with personal tokens. A workspace API key answers `403 permission_denied` — machine keys have no user identity.
- With a stored session whose token has gone stale, the CLI silently re-runs login once and retries.
- A workspace selector that matches nothing reports `workspace_not_found` (flag or env) or `current_workspace_invalid` (stale saved workspace).