Menü
Use when opening, inspecting, clicking, filling, snapshotting, or otherwise automating web pages for this repo, including local dev servers and browser-based verification.
| name | browser-automation |
| description | Use when opening, inspecting, clicking, filling, snapshotting, or otherwise automating web pages for this repo, including local dev servers and browser-based verification. |
Use agent-browser for web automation in this repo. Run:
agent-browser --help
Core workflow:
agent-browser open <url>
agent-browser snapshot -i
agent-browser click @e1
agent-browser fill @e2 "text"
Re-run agent-browser snapshot -i after page changes so element refs stay
current.
Use browser automation for behavior that needs a rendered page, real DOM state, or interactive verification. Prefer focused Bun tests for pure logic and non-browser integration behavior.
Use when preparing, splitting, reviewing, or creating git commits in this repo, especially after larger implementations that should be broken into independently verified commits.
Use when changing loops, collection processing, invalidation logic, tree/diff traversal, path scanning, virtualized rendering calculations, or any code where repeated scans or boolean control flow affect performance or correctness.
Use when adding or running tests, checking snapshots, choosing between Bun tests and Playwright, running lint/format/typecheck, or deciding the verification scope for a change.
Use when running repo scripts, adding or changing dependencies, editing package.json files, installing packages, or deciding how Bun workspace commands should be invoked in this monorepo.
Use when adding or changing packages/apps, TypeScript configs, workspace dependencies, package references, exports, or monorepo project-reference relationships.
Use when working with the repo's bun run wt helper, Pierre-managed worktrees, dev-server port offsets, stale server cleanup, Playwright fixtures, or Chrome debug instances. Do not use this as a substitute for host-provided workspace isolation.