Playwright Use

4. Open the page through http://127.0.0.1:8765/....
5. Once the page is no longer needed, stop the temporary server unless the user still needs it.

Page Readiness

• After navigation, do a lightweight readiness check before acting.
• Prefer title, document.readyState, visible buttons, or small DOM checks over immediate screenshots.
• Use screenshots sparingly. They are for confirmation, evidence, or final reporting, not for every step.

Interaction Strategy

Start with normal browser interactions:

• browser_navigate
• browser_click
• browser_fill
• browser_wait_for
• browser_snapshot

If normal interactions fail repeatedly because of overlays, viewport problems, canvas rendering, or unstable refs, switch quickly instead of repeating the same failed action.

Canvas / WebGL / Three.js / Game Pages

For canvas-heavy or animated pages:

• do not rely on screenshots as the main control strategy
• do not keep reusing stale snapshot refs after rerenders
• prefer targeted browser_evaluate or browser_run_code against app state, exposed globals, or known UI handlers

When you switch to script-driven interaction, keep it focused:

• inspect the current app state
• call the smallest useful function or click handler
• verify the resulting state change before moving on

Common Failure Patterns

• file:// blocked: switch to localhost
• click timeout or pointer interception: inspect overlays, viewport, and visible state
• stale ref errors: capture a fresh snapshot or use direct state inspection
• repeated screenshot timeout: stop using screenshots as your primary probe
• browser page/context closed: reopen the target page and rebuild current state before continuing

Decision Heuristic

• Standard website or form: browser actions first
• Local HTML demo or app: localhost first, then browser actions
• Canvas/game/non-DOM UI: browser actions if they work, otherwise targeted script interaction