aurat.Open workspace
DEVELOPER PREVIEW 0.2

Replay the run.
Catch the regression.

Your agent changed.
Know exactly what broke before you merge.

Explore the workspace Start with the CLI
Node.js 22+Local replayYour existing stack
Pearlescent sculptural path folding back into a replay loop01 — BEHAVIOR, REPEATED.
aurat.Scout / Narration validationACTUAL REGRESSION PROOF
REGRESSION CAUGHT

A number is not a summary.

The model returned summary: 42. Scout accepted it.
Aurat caught the invalid outcome.

EXPECTED
{ "rejected": true }
ACTUAL · ORIGINAL SOURCE
{ "rejected": false }
Same fixtures after the fix: 4 / 4 passInspect the run
A PLAUSIBLE ANSWER ISN'T ENOUGH

The answer can look right.
The workflow can still be wrong.

A ticket created twice.

A required step skipped.

A tool given the wrong argument.

Aurat tests the application around the model. Capture a known workflow, define its expected behavior, and make the next change with evidence.

01 / A TIGHTER FEEDBACK LOOP

From a real run
to a reliable test.

Keep your model SDK and tracing stack.
Add a repeatable check where you ship.

Record the behavior: original pearl sculpture
CONTROLLED CAPTURE
aurat proxy --mode record

// Model traffic + wrapped tools
// Review fixtures before committing.
02 / PROOF OVER PROMISES

A real code defect.
Four unchanged fixtures.

We ran Aurat against Scout's existing narration module. Three malformed responses exposed missing type validation.

Two pearl paths, one continuous and one interrupted at a fracture
1/44/4
Original sourceAfter validation fix

Same requests. Same recorded responses. The actual Scout function executes in both cases.

Read the reproduction Source-discovered defect with synthetic model responses. Not a claimed customer production incident.
03 / EVERY FAILURE HAS CONTEXT

Know what changed.
And why it matters.

Open a run, inspect the failed invariant, and compare it with a passing baseline. Model and tool coverage make missing interactions visible.

  • Readable assertion failures
  • Scenario-level evidence and events
  • Versioned reports from your own CI
Explore real report data
Precisely aligned translucent evidence sheets
Two pearl segments connected into one bridge
YOUR CODE. YOUR CI.

A small addition
to the way you work.

Start locally. Commit your scenarios. Run them in GitHub Actions, then bring the report into your workspace.

Read the integration guide
A precision pearl orbit around a sculptural replay form
MAKE THE NEXT CHANGE WITH EVIDENCE

Ship the change.
Keep the behavior.

Explore Aurat