Self-healing GitHub Actions runners, plus a CLI and MCP server your coding agents can drive.
Set up Latchkey CI for this repo. 1) Install the CLI: npm install -g @latchkeydev/cli. 2) Add the Latchkey MCP server: claude mcp add --transport http latchkey https://latchkey.dev/mcp --header "Authorization: Bearer $LATCHKEY_TOKEN" (create the key in the Latchkey dashboard under Settings, API keys, with Allow running CLI jobs on, and export it as LATCHKEY_TOKEN). 3) Run the test suite on a fresh runner with latchkey run, fix anything that fails, and run it again.30 days free · No credit card · From $0.0025/min
Agents run any command on a fresh Linux runner and get the real exit code back. One runs-on: line moves your workflows over.
“Our CI spend dropped to a fraction of what we’d budgeted, setup took minutes, not days, and nobody on the team has to be ‘the CI person.’ We ship faster and spend our time on Busbar instead of the plumbing around it.”
Transient failures diagnosed and repaired mid-run: over 10,000 a week.
“One line of YAML and our CI bill dropped by two thirds. Honestly the bigger win is that we stopped losing hours every week to reruns that were never our code’s fault.”
Vincent · CEO, CapyWhat self-heal can't fix goes to your coding agent, with the logs and failing step attached.
Cost recommendations priced in dollars, security and reliability findings beside them, waiting for your yes.
A failing step, diagnosed and repaired mid-run. No human and no agent needed.
A dependency install times out and the job goes red.
The runner matches the failure pattern and retries with backoff.
The step passes and the job carries on. Your agent never sees the failure.
We use cookies to improve your experience. Privacy Policy