docs(README): add how-it-works + architecture diagrams and "why the extension" comparison
- assets/how-it-works.png: CLI → extension (native messaging) → your real Chrome - assets/architecture.png: tab groups / service worker / native messaging / CLI - comparison table vs raw-CDP-port tools (web-access) and chrome.debugger (Claude in Chrome): the extension never triggers Chrome 136+'s "Allow remote debugging?" consent dialog, keeps Runtime.enable off (rebrowser clean), scores 0% on CreepJS, and gives per-session tab groups for concurrent agents.
This commit is contained in:
Binary file not shown.
|
After Width: | Height: | Size: 1.2 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.2 MiB |
Reference in New Issue
Block a user