Dashboard/Scout/wiki/ux/browser-workbench-recovery-2026-05-22.md
Scout

wiki/ux/browser-workbench-recovery-2026-05-22.md

Browser Workbench Recovery

Date: 2026-05-22

What Was Built

Scout's /app now has a real browser workbench recovery slice:

  • scout-browser execution mode launches a Playwright-controlled browser.
  • The backend captures screenshot, DOM, rendered text, links, console errors, network failures, status code, and session metadata.
  • Captured browser evidence is written to the selected working directory.
  • The live UI gives the Browser Workbench the main workspace instead of a tiny card.
  • Active runs survive navigation through an Active Run banner and Return to Run action.
  • The left rail is widened so labels are readable.
  • Estée Lauder hard-site behavior is now truthful: if Scout Browser sees Access Denied, the run is marked failed with blocked evidence and saved artifacts.

Current UX State

Run Setup

Run Setup remains the left configuration surface:

  • use case selector,
  • target URL,
  • execution mode,
  • crawl settings,
  • working directory,
  • Start Execution,
  • Clear Run,
  • Developer Details accordion.

Live Execution

When a run starts:

  • run ID is visible immediately,
  • status badge updates,
  • Browser Workbench becomes the main panel,
  • timeline and event log remain visible as side context,
  • Active Run banner appears when the user navigates away.

Results Review

Results Review still shows:

  • Overview,
  • Browser,
  • Records,
  • Sources,
  • Blocked,
  • Artifacts,
  • Logs.

The selected-record drawer remains available after terminal runs.

Product Workflow Status

Target Current behavior
Lacoste Live product run can produce product records.
Nike Live product run can produce at least partial product records/evidence.
L.L.Bean Live product run can produce product records.
Estée Lauder Crawl/Scout Browser paths currently produce blocked evidence rather than product records.
Patagonia Current live validation passes through blocked/fallback evidence, not rich product records.
Home Depot Current live validation passes through blocked/fallback evidence, not rich product records.

Honest Limitations

  • Scout Browser does not bypass all bot protection. Estée Lauder blocks the isolated Scout browser session even though the user's normal browser can view the page.
  • User Browser mode is not implemented yet; it needs Chrome CDP or a browser-extension bridge.
  • DOM-to-product extraction from Scout Browser evidence is not complete.
  • Interactive browser controls are visible but intentionally disabled with explanations until the browser-control API is built.

Next UX Build Step

Build the User Browser bridge UX and backend contract:

  1. Connect to a user-approved Chrome CDP session or browser extension.
  2. Capture the active tab screenshot/DOM/text from the user's actual browser session.
  3. Show clear consent/security state in Settings.
  4. Feed captured evidence into the same records/sources/blocked/artifacts pipeline.
  5. Enable manual Capture and Extract controls for browser-workbench sessions.