For engineering teams

Fixes that arrive with the context

Developers get a ticket in VS Code that explains itself: which SLO burned, which change caused it, what operations already did, and a drafted fix with tests.

Book a pilot See how it works

“Ops sends a screenshot of a graph. We spend a day finding the commit.”

Less hunting, more fixing.

Only real causes reach the developer. The trail from SLO to commit is in the editor, and drafted patches are reviewed and merged like any other pull request.

VS Code · card-auth-apiPR #412 drafted

card-auth/authorise.tsauthorise.test.ts

41export async function authorise(txn: CardTxn) {42  return issuer.post('/authorise', txn, {43-    retry: { attempts: 6, backoff: 'none' }, // #482143+    retry: { attempts: 2, backoff: 'jitter' },44+    idempotencyKey: txn.id,45-    timeout: 5_000,45+    timeout: 800,46  });47}

Suggested tests✓authorise retries at most twice, with jitter✓retries reuse the idempotency key✓times out under 800 ms

Before, and with SteadyNines.

	Before	With SteadyNines
How you hear about it	A chat message and a graph	A VS Code ticket with the trail
Finding the cause	Search dashboards and deploy logs	Linked deploy and commit, with evidence
Writing the fix	From scratch	Drafted patch and tests to review

The AI Engineer