Frequently asked questions
Common questions about how DevSnoop works and how it fits into your agent workflow.
Chrome's DevTools MCP is useful, but it gives your agent Chrome internals. I built DevSnoop because I wanted the browser commands I use while coding.
- Read the page as semantic structure, not a dump of protocol data.
- Return stable CSS selectors the agent can reuse for clicks, fills, and checks.
- List tabs and target a specific Chrome
tabIDinstead of guessing which tab is "the sixth one." - Inspect, act, run
diff, then check console and network failures in the same flow.
The practical difference: DevSnoop gives the agent less to interpret and more it can use directly. Fewer retries, fewer tokens, less babysitting.
page_summary reads the full page — layout regions, interactive elements, semantic structure. Use it when your agent lands on a new page or needs complete context. diff is a lightweight snapshot comparison that tells your agent what changed since it last looked. Use it after clicks, form fills, or navigation to confirm the result — without re-reading the entire page.Any coding agent that can make HTTP requests to a local API can control the browser. No MCP configuration required.
No. DevSnoop uses a simple HTTP API on
localhost:9400. Your agent sends JSON, gets JSON back. DevSnoop provides a SKILL.md file that teaches your coding agent the full API — no setup beyond installing the extension and native host.No. Everything runs locally — the extension talks to a native host on your machine via Chrome's Native Messaging. Page data never leaves your computer.
No. One-time purchase, use forever. No per-request fees, no token metering, no seats.