RWX runs now support using debian 11, 12, and 13 as the base image with base config rwx/base 1.1.0.
RWX can generate status badges for your runs, to be embedded on GitHub, GitLab, and anywhere else you'd like to embed an svg representing the current status of your runs.
RWX tasks now support running nested virtualization. See the docs.
You can now configure log retention if you want RWX to retain logs beyond the 28 day default. See the docs.
Check out some of the many tools people are already using with RWX, on the new RWX Works With... page.
Have something cool you're doing on RWX that we missed? Let us know.
RWX runs now support using ubuntu:26.04 as the base image with base config rwx/base 1.0.3.
The RWX CLI can now directly install or update the RWX Agent Skill.
- Run
rwx skill installto add the skill to your current project. Best practice is to commit it for your entire team to use. - If you already have the skill installed and the CLI has notified you that an update is available, run
rwx skill updateto update it.
Runs kicked off with rwx dispatch now support a --wait flag, like rwx run and rwx results, to block until the run passes and then print results in your terminal.
If you're not already using dispatch triggers, they're a great way to encapsulate occasional / ad-hoc runs for things like deployments.
We've rolled out several improvements to rwx results:
- View results for a specific commit using
rwx results --commit <sha> - Open the browser view for the latest run for your current branch using
rwx results --open - Get inline suggestions on ways to disambiguate your search when
rwx resultshas multiple possible results (i.e. multiple runs for the same commit) - Look up results for a specific task within a run by passing the
--taskkey along with the run ID
See the full list of supported flags here.