Skip to content

docs: never drive the user's live browser for UI verification#56

Merged
bin101 merged 1 commit into
mainfrom
chore/browser-verification-guardrail
Jul 9, 2026
Merged

docs: never drive the user's live browser for UI verification#56
bin101 merged 1 commit into
mainfrom
chore/browser-verification-guardrail

Conversation

@bin101

@bin101 bin101 commented Jul 9, 2026

Copy link
Copy Markdown
Owner

Summary

  • During verification of the stats-loading fix, Claude opened new windows in the user's real, currently-running Safari/Chrome (via AppleScript) to screenshot/inspect the page β€” interrupting the user's actual in-progress work in those apps.
  • Documents that UI verification must use an isolated/headless browser-agent tool, and that verification should be reported as BLOCKED (with an explicit note) rather than falling back to automating the user's live desktop browser.

Test plan

  • N/A β€” docs-only change

πŸ€– Generated with Claude Code

A "verify the fix" step opened new windows in the user's real,
running Safari/Chrome via AppleScript to screenshot the stats page,
interrupting their actual in-progress work in those apps. Document
that UI verification must use an isolated browser-agent/headless
browser and report BLOCKED instead of falling back to the user's
live desktop session.
@bin101
bin101 merged commit d6dd401 into main Jul 9, 2026
1 check passed
@bin101
bin101 deleted the chore/browser-verification-guardrail branch July 9, 2026 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant