Skip to main content
Browser agents fail in ways text-only agents do not: blocked pages, unexpected dialogs, changed layouts, downloads, redirects, auth walls, and slow pages. Webcompute keeps the run inspectable. Webcompute Debug UI showing a live browser on Apple's Mac mini page with network events and the recording timeline visible The Debug UI gives operators a live browser view plus browser status, page metadata, recording state, event timeline, inspector panels, and browser-moment sharing. When recording is enabled, the same surface can replay captured browser frames after the run moves on or closes.

​
Debug UI anatomy

Use Debug UI when the live browser state matters. Share a browser moment when another person or agent needs the same page state and timestamp. Use recordings when the run has already moved on or closed. Use artifacts and downloads when the workflow produced files that another system needs to review.

​
What you can inspect

Live browser sessions

Open a live Debug UI and share exact browser moments with humans or agents.

Recordings

Replay what happened after the run.

Artifacts and downloads

Capture files, reports, PDFs, and evidence.

Status, events, and logs

Connect browser state and timeline evidence to application logs.

Blockers and CAPTCHA

Return clear blocker state instead of pretending success.

​
Typical debug loop

1

Check the result status

Start with completed, blocked, needs_confirmation, failed, or cancelled.
2

Read the step summaries

Look at page titles, URLs, observations, and errors from the browser steps.
3

Open evidence

Use Debug UI for live inspection, browser-moment sharing for handoffs, recordings for replay, and artifacts for downloaded files.
4

Tighten the workflow

Add domain policy, structured output, approvals, timeouts, or deterministic checks where the run was ambiguous.

​
What to keep with the job

Store enough evidence to explain the outcome without leaking credentials:
  • Job ID and browser ID.
  • Result status.
  • Final page URL and title.
  • Bounded observation metadata.
  • Artifact, download, file, or recording IDs.
  • Redacted error code, name, and message.
  • Blocker or CAPTCHA state when present.
Do not store signed Debug UI URLs, signed CDP URLs, raw provider keys, cookies, or full page observations in shared logs.
Treat signed Debug UI and CDP URLs as bearer credentials.
Reference: results and evidence, production observability, and errors.