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

# Sign in to the CLI

> Authenticate interactively and understand what setup changes locally.

Use browser sign-in for interactive CLI work:

```bash theme={"theme":{"light":"github-light","dark":"vesper"}}
almanac login
```

The CLI prints a URL and one-time code, waits for browser approval, then stores a
refreshable local session.

```text theme={"theme":{"light":"github-light","dark":"vesper"}}
open      https://…
code      ABCD-EFGH
waiting   approve the Almanac login in your browser
logged in you@example.com
```

## Setup versus login

`almanac setup` installs concise Almanac guidance for supported coding agents and
then signs you in when needed. `almanac login` only handles authentication.
Neither command creates a workspace or wiki, inspects your repository, or uploads
files.

## Check or clear the session

```bash theme={"theme":{"light":"github-light","dark":"vesper"}}
almanac whoami
almanac logout
```

Logout removes local Almanac credentials. It does not revoke API keys or other
sessions. Programs should use a [workspace API key](/api/authentication) instead.

<Card title="Next: build a wiki" icon="notebook-tabs" href="/quickstart">
  Create, link, upload, follow the job, and verify the result.
</Card>