abadge login

abadge login starts a device authorization flow, opens your browser to approve the request, and stores the resulting operator session in daemon memory — never on disk.

Usage

abadge login
abadge login --api-url http://localhost:8787
abadge login --no-open-browser

Flags

Flag	Description
`--api-url <url>`	Override the API base URL. Persisted to `~/.abadge/config.json`.
`--no-open-browser`	Skip auto-opening the verification URL. Print it for manual visit.

What it does

Request a device code

POST /api/auth/device/code returns device_code, user_code, and a verification URL.

Print and open the URL

The CLI prints the user code and tries to open the URL in your default browser. Use --no-open-browser to skip.

Poll for the token

POST /api/auth/device/token is polled until the user approves or denies the request.

Hold the bearer in daemon memory

The operator bearer token is stored in the daemon’s process memory. The config file never holds a human bearer token.

Audit auth.login

the login-audit operation appends an auth.login event (best-effort — this step is silent for new signups without org membership).

abadge login does not register any agents automatically. The CLI’s runtime agents (local_cli for abadge run/mount, local_mcp for the MCP server) are created separately with abadge agent add --kind local_cli / --kind local_mcp after you have an active organization.

After logging in

Before you can create items or use abadge run, set up an organization and a local runtime agent:

# Create (or join) an org and make it active
abadge org add --name "Acme"
abadge org use <org-id-or-slug>

# Register the CLI's runtime agent (writes to localAgents.cli)
abadge agent add --kind local_cli --name "dev-laptop"

# Create a profile if your org doesn't have one yet
abadge profile add --name default --storage-mode server_managed
abadge profile use default

Scripting

For unattended flows, abadge login has two subcommands that split the device-code handshake:

Subcommand	Purpose
`abadge login start --json`	Issue a device code and emit `{ device_code, user_code, verification_uri, verification_uri_complete, interval, expires_at }` as JSON (`--json` is required)
`abadge login poll --device-code <code>`	Poll until approved. `--print-token` prints the bearer instead of loading it into the daemon; `--interval <s>` sets the initial poll interval; `--json` emits a JSON result.

These are for integrations that need to render the verification URL in a custom UI. The default abadge login is what humans want.

Audit

auth.login — recorded by the login-audit operation

Getting started

Authentication

Local daemon

Resources

Runtime

Data movement

Usage

Flags

What it does

After logging in

Scripting

Audit

​Usage

​Flags

​What it does

​After logging in

​Scripting

​Audit

​Related

Usage

Flags

What it does

After logging in

Scripting

Audit

Related