// docs

Run safety and dry runs

Use environment labels, confirmations, write detection, and dry-run controls before risky work.

LaraBench is designed for real apps, including staging and production. That means safety needs to be visible before you press Run, not after something has changed.

  • Environment badges show whether the selected connection is local, staging, or production.
  • Production runs require confirmation.
  • Write detection makes warnings stronger when code looks mutating.
  • Dry-run mode can roll back a run and avoid persisting inserts, updates, or deletes.
  • Schema-change blocking keeps migration-like operations out of dry-run experiments.
The runner keeps connection context and safety controls near the Run button.