> ## Documentation Index
> Fetch the complete documentation index at: https://help.the-meridian.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# CLI sessions

A CLI session is a machine signed in to your account with `meridian login`. See the [CLI](/cli). Each one is listed in your account's **Security** section, under **CLI sessions**, and can be revoked on its own.

CLI sessions are deliberately separate from browser sessions: **they stay connected when you sign out of the dashboard.** A laptop running `meridian dev` keeps working after you close the browser, which is the point.

## What each machine shows

| Field | Notes |
| - | - |
| Machine | The hostname the CLI reported when it signed in |
| Connected | When `meridian login` was run |
| Last used | When the token was last exchanged, or **never used** |
| Expires | When the token lapses. A lapsed one is marked **Expired** |

An empty list means no machine is connected yet. Running `meridian login` in a terminal adds one.

## Revoking a machine

**Revoke** signs that machine out immediately. Anyone working on it has to run `meridian login` again before `meridian dev` works, so revoking a laptop mid-session stops its next command rather than its current one.

Revoke when a machine is lost, when someone leaves, or when a token has sat unused long enough that you would rather it did not exist.

## How browser sessions affect them

One browser action reaches CLI sessions: **End all other sessions** revokes every CLI token along with every other browser session. Changing your [password](/password) does the same, since it ends all other sessions as a side effect.

Signing out of the dashboard normally does not. Neither does signing in on a new browser, which ends the previous browser session and leaves CLI tokens alone.

<Note>
  Revoking here removes the machine's access to your Meridian account. It does not touch the [developer database](/database) that machine was using, which belongs to you, not to the token.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.