Codex / Claude Code workflow

Let your coding agent inspect, click, and debug Chrome

DevSnoop gives HTTP-capable agents a local browser API. They can inspect rendered UI, interact with it, read console and network failures, then hand back a screenshot-backed report.

Agent prompt

Paste into Codex or Claude Code

Use DevSnoop to check https://dev-devsnoop.theblue.social.
Find the active tab, summarize the page, click through the install flow,
then report console errors, failed network requests, and what changed visually.

Behind the scenes

What the agent does for you

You still prompt in plain English. DevSnoop turns that request into browser actions and debugging checks the agent can report back.

1list_tabs

Find the right Chrome tab without depending on focus.

2page_summary

Read landmarks, headings, forms, buttons, and stable selectors.

3click

Open the install path exactly like a user would.

4get_logs

Return console errors and exceptions as structured JSON.

5get_network

Filter failed requests and status codes without opening DevTools.

6screenshot

Capture the page for final visual verification.

Local HTTP call

Optional technical detail for people who want to see the bridge.

show

Agents call localhost. The native host forwards packaged commands to Chrome through the extension.

bash
curl -s -X POST http://127.0.0.1:9400/ \
  -H 'Content-Type: application/json' \
  -d '{"command":"page_summary","params":{"depth":3}}'

Agent report

  • Opened tab 18: DevSnoop local tunnel
  • Found primary CTA: Add to Chrome
  • Clicked install link with UTM content demo_codex_claude
  • No console errors after route change
  • No failed network requests
  • Saved screenshot to /tmp/devsnoop-screenshots/demo-install.png

What you get back

A short summary of what the agent found.

Concrete selectors or page states it acted on.

Console and network failures when something breaks.

A screenshot path when visual confirmation matters.