No guessing what happened
Green, failed, a mistake or still running: one exit code each, so agents and scripts act on it directly.
Run CI on the Mac you already own. No queue, no runner bill, nothing runs twice.
Early access What works todayMade for tinkerers who can't stop building.lirra turns the Mac on your desk into CI that answers before your agent moves on.
Your agent tests the tree it has right now, uncommitted edits included. No more "fix CI" commits.
Unchanged work comes back instantly from the cache. The push after a green run is green in a second.
Each step starts from the files the last one wrote. npm ci runs once per lockfile, not on every push.
A few lines instead of a log dump, ending with the exact next command. Your agent reads the failure, fixes it and goes green, without burning its context or your attention.
How agents use lirraGreen, failed, a mistake or still running: one exit code each, so agents and scripts act on it directly.
Every answer ends with the command to run next, ids already filled in. Over MCP, the tool and its arguments.
Every result is keyed on exactly what its task read, so work done once is never done again, by your agent or by CI. And the plan stays open while it runs.
How caching worksKeys leave out the commit and the branch. When your agent's tree is pushed, CI finds every task done and goes green in seconds.
What has started is frozen; what hasn't can still change. Agents add or cancel work while the run is in flight, and generators grow it from what they find.
The Mac on your desk keeps fresh VMs warm and ready in a second. Run as much as you like: your secrets never leave it.
The security modelYour agent spends most of its time reading and thinking, and your cores sit idle while it does. lirra puts that idle time to work, on hardware you've already paid for.
Join your MacBook to the Mac mini over Tailscale, on a Thunderbolt cable beside it or from across town.
Everything lirra does is an operation you can call from the CLI or over REST, and agents get theirs as MCP tools: the same inputs, outputs and next steps everywhere. Script it, build on it, or hand it to your agent.
API, MCP and servicesrunexecwaitresultslogsretrycanceladdplanwhyapproveruns.listruns.statsevents.listpools.listcapacity.statushosts.addimages.buildlayers.gcsecrets.granttokens.createstatusHosted CI bills by the minute and waits for a push. lirra runs on your Mac, before you commit.
Per GitHub's and RWX's public docs, November 2026. What lirra does today
lirra import github reads your workflows, splits their jobs into cacheable tasks and writes .lirra/ci.yml. The first run is the slowest you'll ever have.
Or write one by handOne command on the Mac you already have. Your agents take it from there.
$ curl -fsSL https://lirra.dev/install | sh Early access builds from source for now. The install guide
curl … | sh Install One binary for Apple silicon, the daemon set up under launchd.lirra doctor Check the Mac Says what's missing, and the exact command that fixes it.lirra run Run Your pipeline, from any checkout. Hand the skill to your agent.