Skip to main content
Albus is designed to be set up by an agent. The CLI’s browser sign-in is the only step an agent cannot do for you, and it hands that step back to you as a URL.

Paste this

Into Codex, Claude Code, Cursor, or any agent that can run shell commands and fetch a URL:
That page is the whole procedure: install, albus status, albus login --no-browser, verify with albus whoami, one test run, then the SDK. It states the rules that matter — caller-chosen session ids, idempotency keys, secret references, the 20-run alpha cap — so the agent writes correct code instead of guessing.

Then ask for what you actually want

If you already have things installed

An agent that starts from a machine where you are signed in only needs the docs, not the setup:

What to give an agent, in general

Any documentation page is available as markdown by appending .md — that is what you want an agent fetching, not the rendered page. Prefer naming the specific page over the whole corpus: an agent given llms-full.txt spends its context on pages irrelevant to the task.