Agentic Run Loops

With the RWX CLI, CI workflows can be kicked off locally without committing and pushing changes. This works by automatically including your local changes when you run rwx run. Between this and RWX's content-based caching, agents can iterate quickly to get CI to pass.

Kicking off a run loop

Below is an example prompt you can give to an agent to kick off a run loop:

Make sure CI passes by running rwx run .rwx/ci.yml --wait --fail-fast, and then commit and push.

You can see a demo in this blog post. When the run finishes (or has an actionable failure while still in progress), the CLI will output easy-to-follow instructions for an agent (or human) to pull logs or artifacts as needed and fix any issues.

Switching between a push-triggered CI run and a local run loop

If you've already pushed your changes and want your agent to monitor CI and ensure a green build, try a prompt like this to get the same actionable output to your agent as soon as it's available:

Monitor CI with rwx results --wait. If anything fails, fix it and kick off a new run with rwx run .rwx/ci.yml --wait.

If you're using the RWX agent skill, you can usually be more brief with these prompts, but the full syntax is shown for reference.

CLI Reference

For more CLI documentation, see the references for rwx run and rwx results.