Brave

Brave Browser Management (v2.2.0)

Browser automation via brave-manager CLI. Claude Code should prefer Claude-in-Chrome MCP - use brave-manager as fallback.

Prerequisites Check

1. Check brave-manager installed:

which brave-manager || echo "Not installed"

2. Launch Brave with debug port enabled:

# Close Brave completely first, then:
open -a 'Brave Browser' --args --remote-debugging-port=9222

If Brave is already running without the debug flag, quit it completely and relaunch.

3. Verify connection:

brave-manager tabs

If not installed or connection issues: See workflows/debugging.md

Quick Actions

Core Concept: ID-Based Interaction

Always inspect first! Before clicking or typing:

brave-manager inspect

This:

1. Numbers all interactive elements on the page
2. Draws red labels for visual reference
3. Returns the ID mapping for use with click/type/hover

Decision Tree

Need to navigate?

• Open URL, switch tabs, go back/forward
• Use: workflows/navigation.md

Need to see the page state?

• Inspect elements, take screenshots, check errors
• Use: workflows/inspection.md

Need to interact with elements?

• Click buttons, fill forms, scroll, drag
• Use: workflows/interaction.md

Need to verify/debug?

• Run JavaScript, check localStorage, debug state
• Use: workflows/debugging.md

Command Quick Reference

Safety Rules

1. Always inspect first - Element IDs change between page loads
2. Check errors - Use errors before reproducing bugs
3. Screenshot often - Visual verification prevents assumptions
4. Scroll before click - Off-screen elements may not be clickable