Only written permission puts a name on this page.
agi models statusevery local server it can reach, and the models on eacha base URL that is not loopback never gets a request built for itagi --daemonreads ~/.agiworkforce/triggers.jsoncron schedules, webhook endpoints, filesystem watcherstools held: read_file, search_files, list_directoryanything mutating is denied outright
A scenario that only lists benefits would be an advertisement.
None of these is a customer. Each is a configuration we have built, named down to the command that proves it: the surface it runs on, the mechanics underneath, the plan limit it meets, and the work it hands back to you. All three run on the CLI. The CLI is coming soon. The link under each scenario goes to the page that describes the behaviour in full.
A team whose source cannot reach a third party
An NDA forbids sending this repository to an external model provider, which disqualifies most AI coding tools on the question of where inference happens, long before anyone gets to judge how well they answer.
- Model pickerThe CLI discovers each loopback runtime (Ollama and LM Studio) and lists whatever models that server answers with.
- Server discoveryagi models status names every local server it can reach and the models sitting on each. A base URL that is not loopback never gets a request built for it.
- BillingNo AGI account takes part, and a finished run reports no cost for a local model because there was nothing to bill.
- Plan tierThe Local Mode plan tier is priced at zero and puts no cap on work you run against your own hardware.
What it does not do. AGI supplies neither the hardware nor the weights, and a model you host will lose to a frontier hosted model on the hardest problems. That is capability traded for containment, and it is a trade you have to want.
CLI · Coming soon · No AGI account takes part
A firm that charges model spend back to a client
Every engagement has to carry its own AI cost, and the firm will not put a platform vendor between itself and the invoice it has to justify line by line to the client paying it.
- Key storageThe CLI writes the key into the operating system credential store, or into owner-only files on Linux or when the keyring is turned off, so one engagement’s key stays on the one machine that engagement runs from.
- Request routingRequests reach the provider endpoint directly, so the usage lands on the firm’s own provider account and shows up on the firm’s own invoice.
- Cost estimateThe CLI estimates cost from the same catalog rate card it ships with, so the arithmetic behind a cost line is inspectable before a run starts.
- Budget cap--max-budget-usd ends a run once estimated spend passes a ceiling you set, which keeps a runaway loop off a client’s bill.
- Plan tierThe Local Mode + BYOK plan tier is priced at zero, which leaves the provider invoice as the only bill in the arrangement.
What it does not do. Per-client attribution comes out of your provider’s own billing tooling, one key or project per engagement. The number the CLI prints is an estimate from a local rate table; AGI never sees your invoice and writes no per-client spend report for you.
CLI · Coming soon · No AGI charge on this route
A provider repeating the same checks across client estates
Overnight alert triage, certificate expiry sweeps, and ticket intake repeat across dozens of client environments, and doing them by hand makes coverage a function of headcount.
- Trigger sourcesagi --daemon reads ~/.agiworkforce/triggers.json and runs what it finds there: cron schedules, webhook endpoints, and filesystem watchers.
- Tool scopeAn unattended session holds three tools: read_file, search_files, and list_directory. Anything mutating is denied outright, because no one is sitting at the prompt to refuse it.
- Audit logEach firing writes one JSON record into ~/.agiworkforce/daemon-logs, restricted to its owner, with known secret patterns redacted out of the prompt and the response first.
- Plan tierRun this on managed cloud instead and the gates change: AGI Work needs Pro or above, and scheduled tasks are capped per plan at 2 on Basic and 5 on Pro.
What it does not do. A trigger can read and report; it cannot edit a file or run a shell command, so remediation still lands on an engineer. You also have to write the runbook each trigger follows, because AGI will not discover your clients’ processes on your behalf.
CLI · Coming soon · No AGI account required for this route
A name appears here only after someone has put it in writing.
We publish a customer name only with written permission, and we do not fall back on anonymised descriptions specific enough to identify someone who never agreed to be identified. Until a customer says yes in writing, this page stays exactly as you are reading it.
We will ask you before your name ever appears here.
AGI Web is available now. The CLI is coming soon. The download page shows what is published. If AGI earns a place in how you work and you are willing to say so in writing, this page will finally carry something other than worked examples.
Nothing on this page is a customer reference.