From cb525048a42c61a94a57a0d2670f2faa59e595db Mon Sep 17 00:00:00 2001 From: naps62 Date: Mon, 3 Aug 2026 06:24:05 +0000 Subject: [PATCH] docs: prefer agent-browser CLI over claude-in-chrome Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01K4F9xsCrdJQXNxNZJiKpYq --- entry/CLAUDE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/entry/CLAUDE.md b/entry/CLAUDE.md index 0a555af..1dbac77 100644 --- a/entry/CLAUDE.md +++ b/entry/CLAUDE.md @@ -10,6 +10,10 @@ - Environment file: `~/.env.claude` (auto-loaded in shell sessions) - For Claude sessions, source it manually if needed: `source ~/.env.claude` +## Browser automation +- Use the `agent-browser` CLI (headless, via Bash) for anything browser-shaped: checking pages, dev servers, screenshots, form flows, console/eval. `agent-browser --help` lists commands; `snapshot` gives an accessibility tree with refs for AI use. +- The claude-in-chrome extension is disabled by default. Only reach for it if the task genuinely needs my real logged-in browser session or open tabs — and if its tools aren't available, ask me to enable it rather than working around it. + @~/.claude/writing.md @~/.claude/operating.md