feat: add DevTools commands (network, console, eval) #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds Chrome DevTools-like functionality to the browser CLI, making agent-browse a more complete replacement for Chrome DevTools MCP while maintaining the natural language interaction benefits.
New Commands
browser network [filter]browser network-get <id>browser console [filter]browser eval "<js>"browser clearImplementation Details
.devtools-network.json,.devtools-console.json)Network.enableandRuntime.enableExample Usage
Why This Matters
This addresses a gap where agent-browse excels at natural language browser interaction but lacks debugging capabilities. Users previously needed Chrome DevTools MCP for network/console inspection, which is significantly more context-heavy (~30k tokens per snapshot vs ~100 tokens for these commands).
Test Plan
browser networklists captured requestsbrowser network <filter>filters by URL/method/typebrowser consolelists captured messagesbrowser console <filter>filters by type/textbrowser evalevaluates JS and returns resultbrowser clearclears persisted data🤖 Generated with Claude Code