# Latchkey CI: Keep Running CI Even When GitHub Is Down (Which It Is)

> Source: <https://latchkey.dev/>
> Published: 2026-10-19 16:50:03+00:00

`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.`
A dependency install times out and the job goes red.

Latchkey matches the failure pattern and retries the step with backoff.

The step passes and the job carries on. Your agent never sees the failure.