A failed journey should explain itself.

Trace keeps the record around a run: what the browser saw, what the agent did, and which artifacts were produced. It gives integration failures a shared surface for engineering, QA, and agents to inspect.

Get started Read the docs

Molar Trace

Checkout / evidenceIllustrative trace

Expected outcome

Order confirmedReceipt sent to test inbox

Observed outcome

Order pendingPayment callback not applied

00:08Payment confirmed200

00:09POST /webhooks/payment500

00:10Order status assertionFailed

ScreenshotNetworkConsoleSteps

Step level context

Follow task status, trace identifiers, screenshots, and artifact manifests from the same run.

Sensitive by design

Trace access is organization scoped, and artifact reads use authenticated or expiring references rather than an open bucket.

Agent readable

MCP tools expose trace listing, retrieval, bounded slices, diffs, and replay triggers for authorized clients.

Evidence for integration failures

See where a checkout changed from payment method to confirmation, where a verification email stopped arriving, or which callback assertion failed. The record makes a rerun more deliberate.

Screenshots and trace events
Network and console context where captured
Organization scoped artifact access

Go to documentation

Live evidenceIllustrative workflow

checkout.acme.test / confirmation

Order confirmedReceipt sent to test inboxpayment_intent.succeeded

Run trace 00:08—00:10

Open checkoutScreenshot captured200

Confirm paymentPOST /webhooks/payment200

Receive receiptTest inbox matchedready

Network and console evidence attached

Replay oriented investigation

Trace provides the structured record needed to investigate and reproduce supported failures. Replay availability depends on the workflow and deployment.

Talk through your use case

Checkout journeyIllustrative workflow

checkout.acme.test

PaymentAcme Pro plan4242 4242 4242 424208 / 28 · Test card

Signed callbackPayment webhookPOST /webhooks/payment signature verified

Order #1042ConfirmedReceipt → test inbox

A few things
you might be wondering.

Have a specific workflow in mind?
Let’s talk it through

Does Trace include video?

Screenshots and trace artifacts are available in supported runs. Video and HLS replay embedding are still in beta; contact us about your workflow.

Can agents read a Trace?

Yes, the hosted composite MCP endpoint exposes organization scoped Trace tools, subject to credentials and scopes.

Can Trace expose customer secrets?

Trace treats DOM, network, and console content as sensitive. Access is scoped and artifacts are served through authorization checks.

Inspect a run.

Choose a concrete workflow. We’ll help you get the right setup for your application.

Get started Talk to the team