Read this tutorial on Signadot docs .

Devin writes code and runs unit tests in its own cloud VM. What it can't easily check there is whether a change to one microservice still works with the services it talks to. That usually waits for a staging deploy, after the pull request is open.

With the Signadot CLI and the Signadot MCP server in its environment, Devin closes that loop itself. It runs the changed service in its VM, creates a sandbox that routes tagged cluster traffic to that process, runs your end-to-end tests in the cluster as a Signadot Job , and reports back only after they pass.

In this tutorial, Devin changes the route service of HotROD , a demo ride-sharing app, and validates it with HotROD's Playwright suite.

Time: about 30 minutes, including about 8 minutes for Devin's session.

Example files: signadot/examples/devin-tutorial

How it works

Two things make this work from a cloud VM:

No cluster credentials. The CLI's ControlPlaneProxy connection tunnels through the Signadot control plane.…