// Run GitHub Actions workflows locally with pause-on-failure for AI-agent-driven CI iteration
Run local CI via the in-tree dev build of agent-ci (`pnpm agent-ci-dev`) to verify changes to this repo before completing work. Runs `pnpm agent-ci-dev run --all` in the background, watches the log for step failures, and retries failed runners after fixes. Use before reporting work as complete, or whenever the user asks to validate, run CI, or check that changes pass. Distinct from the published `agent-ci` skill, which targets downstream users via `npx @redwoodjs/agent-ci`.
Run GitHub Actions CI locally with Agent CI to validate changes before pushing. Use when testing, running checks, or validating code changes.
| name | agent-ci |
| description | Run GitHub Actions workflows locally with pause-on-failure for AI-agent-driven CI iteration |
| keywords | ["github-actions","local-ci","pause-on-failure","ai-agent","runner"] |
Runs the official GitHub Actions runner binary locally (in Docker), emulating GitHub's cloud API. Cache is bind-mounted (instant). When a step fails, the container pauses — you can fix and retry the failed step without restarting.
act)npx @redwoodjs/agent-ci run --workflow <path>on triggers match the current branch/event, just like GitHub): npx @redwoodjs/agent-ci run --allnpx @redwoodjs/agent-ci retry --name <runner>npx @redwoodjs/agent-ci abort --name <runner>Pass --json (or set AGENT_CI_JSON=1) to emit an NDJSON event stream on stdout — one JSON object per line, with run.start/paused/finish, job.start/finish, step.start/finish, and diagnostic events. run.start carries schemaVersion: 1. Pair with --pause-on-failure: when stdout isn't a TTY the launcher detaches and the foreground process exits 77 the instant a run.paused event fires, so callers can react cleanly without parsing plaintext.
npx @redwoodjs/agent-ci run locally first--from-start when only the last step failed — use retry with no flags to re-run only the failed stepAI_AGENT=1 env variable disables animated output for cleaner agent logs--no-matrix to collapse matrix jobs into a single run — your local machine is likely faster than GitHub's runners, so parallelizing across matrix combinations is unnecessary