Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bin101 merged 1 commit into from
Jul 9, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,18 @@ Known unavoidable external warnings must be added to the `filterwarnings` ignore
> step, or quality requirement, update this file in the same PR. CLAUDE.md is the single source
> of truth for how this project is built and maintained.

### Browser-based UI verification

When verifying frontend/UI changes visually, always use an isolated, dedicated browser
automation tool (e.g. a headless/dedicated Playwright or browser-agent instance) —
**never** drive the user's currently-running personal browser (Safari, Chrome, etc.) via
AppleScript/UI automation or by opening new windows/tabs in it. Doing so interferes with the
user's actual, in-progress work (open tabs, unsaved state).

If no such isolated browser tool is available in the environment, say so explicitly and
report verification as blocked/skipped rather than falling back to automating the user's
live browser session.

### Docker

```bash
Expand Down
Loading