yolo/agent-skills
3
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: prefer agent-browser CLI over claude-in-chrome

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K4F9xsCrdJQXNxNZJiKpYq
This commit is contained in:
naps62
2026-08-03 06:24:05 +00:00
parent 5e95a7337f
commit cb525048a4
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
entry/CLAUDE.md
+4
View File
@@ -10,6 +10,10 @@
- Environment file: `~/.env.claude` (auto-loaded in shell sessions) - Environment file: `~/.env.claude` (auto-loaded in shell sessions)
- For Claude sessions, source it manually if needed: `source ~/.env.claude` - 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/writing.md
@~/.claude/operating.md @~/.claude/operating.md