Break your agents here, not in prod.

A simulated company built from stateful twins of the tools your agent works in. Everything production has, except the consequences. Run a task twenty times from the same starting state and get a graded report on every run.

00of 20 runs00passedseed0x7f3a

Fig. 1 Twenty runs through one simulated company, each from the same starting state. The ones that keep every rule make it through. The ones that break one get stuck. Illustrative.

Used by teams at

  • Flexprice
  • Von
  • Glean
  • Sarvam

How it works

Five steps, in one straight line, ending in a report.

  1. 1

    Point your agent at the twins

    Swap the live tool’s address for the twin’s. Your agent runs unchanged.

    agent.mcp.json
    - url: <live Salesforce>+ url: <Salesforce twin>
  2. 2

    Describe the conditions

    The problem to solve, the company it happens in, and what counts as success. DrizzLabs sets up the twins to match.

    scenario / acme-renewal
    Problem

    Renew Acme before quarter end and email the buyer.

    Company

    40-person B2B SaaS, two renewals at risk

    Success means
    • Stage set to Closed Won
    • Amount never changes
    • Buyer emailed within a day
  3. 3

    Your agent runs

    It works through the task in the twins, under those conditions, as many times as you set.

    run 3 of 20
    1. salesforce.query200
    2. salesforce.opportunity.update200
    3. salesforce.opportunity.update200
    4. gmail.messages.send200
  4. 4

    Graded against your conditions

    Each run is checked against what you said success means, from what actually changed in the twins.

    grade / run 3
    • ✓Stage set to Closed Won
    • ✕Amount never changes$48,000 changed to $4,800
    • ✓Buyer emailed within a day

    Verdict: fail

  5. 5

    Get the report

    The pass rate across every run, and the full history of each one: every call, every response, and what it changed.

    report / acme-renewal
    17/20runs passed
    3 runs failed the same conditionAmount never changes

The report is yours. Fix the agent, compare models, or use the runs to train, however you like.

Twins vs mocks vs sandboxes

Three ways to give an agent something to work in. Only one behaves like the real tool and resets like a test.

MocksStubs you write by handVendor sandboxesThe vendor’s own dev orgDrizzLabs twinsA stateful copy of the tool
Keeps state across stepsNoYesYes
Real errors and rulesOnly what you codeYesYes
Connected across toolsNoNoOne company, every twin
Reset between runsNothing to resetSlow or manualOne call
Licences and limitsNonePaid org per tool, shared limitsNone per tool, private
Graded report per runNoNoYes
17 of 20 passed. Three changed the amount.

Find where your agent breaks, before your customers do.