Claude sees what
DevTools sees.
Screenshots show pixels. PilotGentic shows Claude the page's actual state — console errors, network traffic, and the live DOM — so “why is my app broken?” gets a real answer.
What Claude gets
State, not screenshots
Console capture
Errors, warnings, and logs from any open tab — Claude reads the exact stack trace, not a screenshot of it.
Network inspection
Requests and responses as they happen: status codes, payloads, timing. Debug an API without opening DevTools.
JS execution
Run JavaScript in the page's own world — query state, click React components, read variables invisible to pixels.
Tab discovery
See every open tab across Chrome profiles and target the right one — no guessing which window has the bug.
> why is checkout broken?
→ reading console… TypeError: cart.items is undefined (cart.js:214)
→ reading network… POST /api/cart → 500
→ the API returns an error body, cart.js never checks it. Here's the fix:
The Chrome extension
Bridged to the desktop, and it maintains itself
The extension relays page state to the Mac app over native messaging, and it reloads itself when it updates — no manual re-install, no lost tab. Desktop and PG Page buttons jump you between the browser and the app in one click.
- ✓Extension self-reload — updates apply in place
- ✓Desktop button — jump to the Mac app from any page
- ✓PG Page button — open the PilotGentic page instantly
- ✓Native messaging — direct browser-to-app channel
Stop describing bugs. Show them.
Browser debugging is part of the free tier — alongside 475+ other MCP tools.