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 with a live browser viewport, active page metadata, recording state, and runtime status The Debug UI gives operators a live browser view plus browser status, page metadata, recording state, event timeline, and inspector panels.

​
Debug UI anatomy

AreaWhat it answers
Live browser viewportWhat page is the browser actually showing now?
Active page metadataWhich URL, title, and page ID is Webcompute operating on?
Runtime readinessIs the browser ready, configuring, recovering, stopped, or blocked?
Recording stateIs replay evidence being captured for later review?
Event timelineWhat navigation, action, download, dialog, blocker, or error happened over time?
Inspector panelsWhich status, artifacts, downloads, dialogs, pages, or capabilities can you inspect next?
Use Debug UI when the live browser state matters. 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 when you need to see the current page.

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, 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: what Webcompute returns, production observability, and errors.