Skip to content
BlogProduct

Octavo 1.6: cloud agents that show the change

Octavo Team · 4 min read

Octavo 1.6 is out for the desktop editor, the Octavo CLI and Octavo Cloud. This release is about the moment a cloud agent finishes. Each cloud agent now returns a pull request with a summary, test results and screenshots or a short screen recording of the change.

A diff tells you what changed in the code. For a checkout form, a settings page or an onboarding flow, you also need to know what changed for the person using it. Until now, that meant checking out the branch and running the app yourself. In 1.6 the agent does that step and attaches what it saw.

What comes back

A cloud agent works on its own branch and ends with a pull request. In 1.6 that pull request carries:

  • A short summary of what the agent changed and why.
  • The test commands it ran and their results.
  • Screenshots or a short screen recording of the change in the running app.
  • The full diff, ready for line-by-line review.

Ask a cloud agent to fix a flaky checkout test in atlas-web, and the pull request shows the fix, a passing test run and a recording of the payment flow: the pointer presses Pay and the confirmation screen loads. You see the result first, then read the code with that result in mind.

How the agent checks its work

Each cloud agent runs in its own VM with your repository, dependencies and tools. That environment is what makes the check possible. The agent installs dependencies, runs the tests that cover the change, reads any failures and fixes them before it opens the pull request. Then it starts your app in the VM, walks through the change and captures screenshots or a recording.

In the desktop editor, the agent does the same kind of check in the built-in browser while you watch. A cloud agent works while you are somewhere else, so the recording is how you see what it checked.

You can start one from the Octavo CLI in the repository you are working in:

cd atlas-weboctavo cloud "Fix the flaky checkout test"

What you still check

The recording answers one question: does the change do what you asked? The test results answer a second: did anything else break? The diff is where you decide whether this is code you want to keep, from names and structure to the edge cases no test covers yet. All three arrive together in one pull request, and the decision to merge stays with you.

Start where the task arrives

A cloud agent can start from the Octavo Cloud web app, from the desktop app, from the CLI with octavo cloud, from a Slack thread where someone mentions @Octavo, from a comment on a GitHub issue or pull request, or from a Linear issue. Every route ends the same way: a branch and a pull request with a summary, test results and screenshots or a recording.

Say a teammate reports in #billing-eng that invoice exports time out for large workspaces. Someone replies “@Octavo can you take this? Keep the CSV format the same.” A cloud agent starts on ledger-api, and when it finishes it posts the pull request link in the same thread, with its test results attached.

You can run many cloud agents at the same time. Each one has its own VM, so one agent’s dependencies, processes and test runs stay out of another’s way.

Move work between your machine and the cloud

Some tasks start small in the editor and turn into a long round of dependency upgrades and test runs. Move that task to a cloud agent and keep working locally on something else. When the cloud agent finishes, its pull request carries the same summary, test results and recording as any other. If you want to continue the work on your machine, bring the task back to the editor or the CLI.

Fixes from Octavo Review

Octavo Review comments inline on logic bugs, security issues and regressions, each with a suggested fix. When the fix needs more than a one-line suggestion, press Fix in Octavo. A cloud agent makes the change on the branch under review and runs the tests, and you confirm the fix before you resolve the comment.

Roll out Octavo 1.6

Octavo 1.6 ships for macOS, Windows and Linux, in the editor and the Octavo CLI. Your security team approves the build before it reaches engineers, as the rollout page describes. Cloud agents run in Octavo Cloud, or in your own VPC on Enterprise. The features page explains how they work, and the changelog has the full list of changes in 1.6.