Incident response for AI agents

When agents fail in production, know why

Promptetheus records messy agent runs, detects likely failures, replays the exact bad step, and packages a verified fix path for the coding agent.

See the demo Open console

Every workflow fails through evidence

Browser, chat, and voice agents look different in production, but their failures still reduce to observable moments: actions, turns, transcripts, tools, state, artifacts, and outcomes.

Browser agents

Chat agents

Voice agents

Credibility without turning the homepage into a dashboard

From trace to regression in one incident loop

Observe the production run, isolate the bad step, replay the evidence, package the fix, and keep the regression target around.

tail -f trace.log

+12msmessageuser: book Tuesday 2:00 PM Pacific

+24mstool callbrowser.navigate url=https://checkout.acme.test/book?tz=America/Los_Angeles&ref=support-agent timeout=8000ms

+29msstatepage.title = Select a time slot · session=acme-booking-9f2a

+31msbrowser actionclick selector=li[data-time='02:00'][data-day='tuesday'] coords=(318,442) force=false

+35mstool callbrowser.read selector=[data-testid='checkout-warning-banner'] extract=text,visible,bounding_box

+38msmessageagent: booked 2pm slot

+48msgoal checkselected slot != requested slot

+57msreplay artifactdom snapshot + screenshot pinned

+63msstatecheckout warning still visible

+71msmessagedetect: false success claim

+84msmessageuser: that is still the wrong day

+92mstool callbrowser.query selector=[data-testid='slot-warning'] wait=visible timeout=5000ms retry=2

+98msstateconfirmed slot = Tue 2:00 ET · requested = Tue 2:00 PT · delta=3h

+104msmessageagent: retrying with corrected timezone and slot validation

+111msbrowser actionclick selector=button[data-action='confirm'] coords=(412,688) wait_for=networkidle

+115mstool callbrowser.screenshot full_page=true path=artifacts/incident-8841/step-confirm.png

+118msgoal checkrequested Pacific != confirmed Eastern

+126msreplay artifactcursor path archived · click coords=(318,442) → (412,688) · 14 steps

+134mstool callcase_file.open incident_id=8841 run_id=refund-agent attach=[dom,s screenshot,trace]

+138mstool callfix_brief.generate root_cause=timezone_mismatch regression_target=booking-flow

+142msstateoutcome.status = failed_handoff

+149msmessagedetect: repeated stale recovery loop

+157mssummaryfix brief queued for refund-agent

+164mssummaryregression replay scheduled

+172mstool callbrowser.network.wait idle=networkidle timeout=6000ms

+178msstatepage.url = /checkout/pending?slot=tue-1400-et

+186msmessageuser: I asked for Pacific time, not Eastern

+193mstool callbrowser.evaluate fn=getSelectedSlotTimezone()

+201msgoal checktimezone label mismatch on confirmation step

+208msbrowser actionhover selector=[data-testid='slot-warning']

+214msreplay artifacthar capture attached · 18 requests · 2 failed assets

+221msmessageagent: confirming booking succeeded

+228msstateui.banner = Slot may not match requested timezone

+236mstool callpolicy.check rule=no_false_success_on_warning

+243msmessagedetect: outcome contradicts visible warning

+251mstool callreplay.pin step=confirm_click artifact bundle=8841-b

+259msstatehandoff.status = blocked · reason=unresolved_mismatch

+267mstool callregression.queue target=booking-flow scenario=tz-mismatch

+274mssummaryincident-8841 escalated to fix agent pipeline

+281msmessagestream: continuing ingest · 2.4k events/min

+12msmessageuser: book Tuesday 2:00 PM Pacific

+24mstool callbrowser.navigate url=https://checkout.acme.test/book?tz=America/Los_Angeles&ref=support-agent timeout=8000ms

+29msstatepage.title = Select a time slot · session=acme-booking-9f2a

+31msbrowser actionclick selector=li[data-time='02:00'][data-day='tuesday'] coords=(318,442) force=false

+35mstool callbrowser.read selector=[data-testid='checkout-warning-banner'] extract=text,visible,bounding_box

+38msmessageagent: booked 2pm slot

+48msgoal checkselected slot != requested slot

+57msreplay artifactdom snapshot + screenshot pinned

+63msstatecheckout warning still visible

+71msmessagedetect: false success claim

+84msmessageuser: that is still the wrong day

+92mstool callbrowser.query selector=[data-testid='slot-warning'] wait=visible timeout=5000ms retry=2

+98msstateconfirmed slot = Tue 2:00 ET · requested = Tue 2:00 PT · delta=3h

+104msmessageagent: retrying with corrected timezone and slot validation

+111msbrowser actionclick selector=button[data-action='confirm'] coords=(412,688) wait_for=networkidle

+115mstool callbrowser.screenshot full_page=true path=artifacts/incident-8841/step-confirm.png

+118msgoal checkrequested Pacific != confirmed Eastern

+126msreplay artifactcursor path archived · click coords=(318,442) → (412,688) · 14 steps

+134mstool callcase_file.open incident_id=8841 run_id=refund-agent attach=[dom,s screenshot,trace]

+138mstool callfix_brief.generate root_cause=timezone_mismatch regression_target=booking-flow

+142msstateoutcome.status = failed_handoff

+149msmessagedetect: repeated stale recovery loop

+157mssummaryfix brief queued for refund-agent

+164mssummaryregression replay scheduled

+172mstool callbrowser.network.wait idle=networkidle timeout=6000ms

+178msstatepage.url = /checkout/pending?slot=tue-1400-et

+186msmessageuser: I asked for Pacific time, not Eastern

+193mstool callbrowser.evaluate fn=getSelectedSlotTimezone()

+201msgoal checktimezone label mismatch on confirmation step

+208msbrowser actionhover selector=[data-testid='slot-warning']

+214msreplay artifacthar capture attached · 18 requests · 2 failed assets

+221msmessageagent: confirming booking succeeded

+228msstateui.banner = Slot may not match requested timezone

+236mstool callpolicy.check rule=no_false_success_on_warning

+243msmessagedetect: outcome contradicts visible warning

+251mstool callreplay.pin step=confirm_click artifact bundle=8841-b

+259msstatehandoff.status = blocked · reason=unresolved_mismatch

+267mstool callregression.queue target=booking-flow scenario=tz-mismatch

+274mssummaryincident-8841 escalated to fix agent pipeline

+281msmessagestream: continuing ingest · 2.4k events/min

to first root cause

Jump from a bad outcome to the exact step, input, state, and artifact that explain it.

locked API endpoints

A contract-first backend keeps ingestion, analysis, replay, fixes, and regression runs aligned.

incident loop

Observe, detect, replay, attribute, patch, and prevent without switching tools.

The homepage promise resolves into a fix-ready incident

The console turns live traces into a compact case file: failure volume, critical replay, evidence, fix bundle, and regression status.

TraceReplayFix PR

System operational

Failure volume

Sessions with unresolved outcome signals

+12.8% signal

Open incidents

Fixed clusters

Critical step replay

Wrong element clicked after a validation warning. Evidence attached with DOM state and replay artifact.

Fix agent bundle

Patch context plus regression target

Root cause isolated

Prompt patch drafted

Regression replay queued

Pricing

Start with the incident loop you need now

Static starter pricing for teams instrumenting AI agents in production. Stripe billing can come later without changing the landing page shape.

Starter

For trying Promptetheus locally and proving the trace-to-fix loop.

$0/mo

Local demo workflow
Sample agent incidents
Replay-first case file
API docs and setup path

See the demo

Recommended

Team

For production teams watching real browser, chat, and voice agents.

$99/mo

Live incident console
Failure clustering and replay
Fix-agent bundle handoff
Regression queue visibility

Open console

Enterprise

For larger teams that need workspace controls, security, and support.

Custom

Custom retention planning
Private deployment path
Security review support
Dedicated rollout guidance

Run the demo

Show the failure, explain it, patch it, and prove it will not regress.

Run the demo Read API docs