rwx run - development without the push and pull

Most "continuous integration" workflows aren't truly continuous.

You make a change locally, commit, push, wait for CI to pull, wait for CI to build, and wait for CI to finally validate. CI is designed to run after your development has reached a conclusion, not during your exploration, iteration, and debugging.

We built RWX to fully integrate CI/CD with your development workflow.

Beginning with version v2, rwx run can now launch a build directly from your terminal - local code changes included:

By syncing your local changes directly to your build environment, rwx run makes it easy to iterate quickly. You can:

Debug platform and architecture issues between your fancy MacBook Pro and your application's stripped-down Alpine Linux container
Chase down pesky bugs with an rwx-breakpoint (or even a few print statements!) without a bunch of "wip" commits
Integration test your change safely with scoped, auditable vault access instead of storing credentials on your laptop
Build new CI/CD automations without jumping through hoops to simulate them locally

How does it work?

RWX is built on top of OverlayFS to enable Docker-like caching. That means CI steps with identical file systems running identical commands don't need to re-run on every build. rwx run takes full advantage of this caching to skip expensive tasks like git clone, dependency installs, and other upstream steps.

When you run rwx run, the CLI determines where your local repository has diverged from its remote and constructs a patch file.

Subsequent builds start at the git patch application. Steps that haven't changed — including cloning your repository and all upstream tasks — are pulled from the cache.

You get immediate feedback, even on large projects. You can iterate frictionlessly, without waiting for full rebuilds or CI pipelines to catch up.