› 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" (in the Latchkey dashboard, enable this repo, then create a key under Settings, API keys and agents, with Allow running CLI jobs on, and export it as LATCHKEY_TOKEN). 3) Write .latchkey/workflows/ci.yml that runs on push and pull_request, with one job on runs-on: small whose steps are this repo's install, lint and test commands as run: steps (no uses: steps; checkout is automatic). 4) Commit and push, then watch the Latchkey check on that commit; if it fails, reproduce the failing step with latchkey run, fix it and push again.
30-day free trial · No credit card · From $0.0025/min
01 · RUN
Run CI before you push
Agents run any command on a fresh Linux VM and get the real exit code back. Commit a workflow file and Latchkey runs it on every push.
“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.”
About 18.5 dev-hours of reruns avoided. Nothing here needs approval.
“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.”
