---
title: Log in
description: Sign in to Wiblo from the terminal with the OAuth device flow.
cli_command: wiblo login
canonical_url: https://wiblo.app/docs/developers/cli/authentication/login
last_updated: 2026-08-25T13:42:39+02:00
md_url: https://wiblo.app/docs/developers/cli/authentication/login.md
---

# Log in

`$ wiblo login`

## Usage

```bash
wiblo login
```

Login starts an OAuth device flow: the CLI prints a verification URL and a short user code, opens your browser (unless you are in CI or an agent environment), and waits while you approve the sign-in. On approval it stores a personal token and greets you:

```text
$ wiblo login
> Visit https://wiblo.app/cli and enter code: WDJB-MJHT
✓ Signed in as matt@example.com
```

The stored session lives in `auth.json` — see [Configuration](/docs/developers/cli/configuration).

## Flags

`wiblo login` takes no flags of its own, and it is the one command where `--token` is rejected — a supplied token and a sign-in flow contradict each other.

## Behaviour

- Approval happens in the browser against your signed-in Wiblo session; the CLI never sees your password.
- In CI or agent environments the browser is not auto-opened — the URL and code are printed for you to hand to a human.
- Non-interactive runs that cannot wait report `device_flow_pending` as JSON and exit `1`.
- If you were already signed in, login replaces the stored session with the new one.