Use cases and demo
The runtime is for work where looking like it worked is not enough: documents that must be verified, forms that must not leak a secret, and browsers where you are already signed in.
Overview#
The runtime is for work where looking like it worked is not enough: documents that must be verified, forms that must not leak a secret, and browsers where you are already signed in.
| Use case | What proves it |
|---|---|
| Document download | an oracle-verified artifact with type, name and digest |
| Decoy-heavy lists | completion criteria pin the exact document (2026-08, not 2026-07) |
| Forms with secrets | secret fields never enter a snapshot, a decision or a trace |
| Your own logins | Agent Window, explicit tab borrowing, capabilities reported honestly |
| Irreversible steps | approval or human takeover; DONE is not offered mid-dialog |
| Debugging and audit | one JSONL trace per run: decisions, actions, verification, recovery |
| LLM optional | Jev decides when to escalate; the strong model only picks runtime-owned options |
| Deterministic CI | scripted decisions against the same fixture: red means the runtime changed |
npm install @mlola/browser-cli
node node_modules/@mlola/browser-evals/dist/bin.js serve --port 4311 & # the local fixture site
npx mlola browser config show # which provider, model and key it will use
npx mlola browser run --headless \
--goal "Download my latest invoice" --url http://127.0.0.1:4311/billing
npx mlola browser run --browser-extension \
--goal "Download my latest invoice" --url http://127.0.0.1:4311/billing # your own Chrome (daemon + loaded extension)
npx mlola browser eval --suite core # the deterministic acceptance suite, no API key