I built this because I treat CI as the last line of defense. Agents also need validation. They should use CI, and they shouldn't bother you unless everything is green!
GH Actions is usually in the top-5 expenses for dev-teams. Add agents to that mix? It'll easily double. It's the wrong tool for the right job: Slow boot, slow cache, retrieving logs is token expensive for agents, the list goes on...
So I built a tool with one amazing feature: live-reload for failures. Agent-CI is a local CI runner.
I tweaked the control pane and mounts to provide 0ms caching, insanely fast boots. When a step fails it pauses, provides the agent with the failure, and waits for the agent to fix and retry just that step.
It uses the standard GH Actions image (via Docker), but emulates the control pane via a local HTTP server. You don't have to change any of your existing GH workflows.
Hi HN,
I built this because I treat CI as the last line of defense. Agents also need validation. They should use CI, and they shouldn't bother you unless everything is green!
GH Actions is usually in the top-5 expenses for dev-teams. Add agents to that mix? It'll easily double. It's the wrong tool for the right job: Slow boot, slow cache, retrieving logs is token expensive for agents, the list goes on...
So I built a tool with one amazing feature: live-reload for failures. Agent-CI is a local CI runner.
I tweaked the control pane and mounts to provide 0ms caching, insanely fast boots. When a step fails it pauses, provides the agent with the failure, and waits for the agent to fix and retry just that step.
It uses the standard GH Actions image (via Docker), but emulates the control pane via a local HTTP server. You don't have to change any of your existing GH workflows.
Repo: https://github.com/redwoodjs/agent-ci, that includes a demo in the README.