Skip to main content
Your CI pipeline already sends failure reports by email. Point those emails at the agent’s address and it handles the rest: it wakes on the event, clones the repository on a fresh Linux machine, reproduces the failure, pushes a fix branch, and replies in the same email thread with a pull request link. Nothing runs on a developer’s laptop, and the machine stops itself when the work is done.

What you need

An agent equipped with an inbox and a token that has the following capabilities:
  • email:read — to receive and read CI failure reports
  • email:send — to reply in the thread with the result
  • compute:run — to create and run commands on a Linux machine
Machines must be enabled in your workspace. The compute:run capability is feature-flagged — contact support if it is not visible on your plan.

Steps

Chat prompt example

Use this prompt in any chat client with Agent Loadout connected:
Chat prompt

TypeScript example

ci-fixer.ts

CLI example

CLI

Required permissions

Pass inject_credential_ids when creating a machine to place a repository token (e.g. a GitHub PAT stored in the vault) into the machine’s environment. The credential value is injected directly — it never passes through the calling script or appears in logs.