Documentation
From your cluster to your first task
Alicorn runs in your infrastructure. Your organization deploys the control plane once; every person signs in through its identity provider, and runners on your machines do the work.
Quickstart
1 · Deploy
The control plane is one Helm chart, for AKS, OpenShift or Azure Local. It hosts no model and holds no key: model calls go through a gateway your organization runs.
2 · Sign in
Open the web app, or the desktop app, and sign in through your organization's identity provider. The CLI signs in with a device code:
alicorn signin --api https://alicorn.example.internal \
--issuer https://id.example.internal/realms/alicorn3 · Enrol a runner
A runner is a machine that does agent work: yours, your team's, or one in a client network. Mint an enrolment code on the Runners screen, then on that machine:
alicorn-runner enroll <code> --api https://alicorn.example.internal
alicorn-runner start --workdir ~/src/claims-serviceReference
CLI
| Command | What it does |
|---|---|
alicorn signin | Sign in with a device code |
alicorn signout | Forget the stored sign-in |
alicorn ledger report --project <id> | Interruptions per completed task, by member and stage |
alicorn ledger cost --run <id> | What one agent run used |
alicorn ledger provenance --repo <path> | What ran, what verified it and who decided, for a branch |
alicorn-runner enroll <code> | Register this machine as a runner |
alicorn-runner start | Take work from the control plane |
alicorn-runner mcp | Serve Alicorn's tools to an agent over MCP |