Give your coding agent
a real iPhone or Android

Your agent writes mobile code it can't run. Inspect connects it to real devices and simulators: find the bug, fix the issue, make sure everything works.

Claude Code — using Inspect
> 
Replay of a real Claude Code session: the layout break found on an iPhone, fixed in the stylesheet, and re-shot to prove it.

Get started in one prompt

Tell your agent
Fetch https://inspect.dev/agent.md and set up mobile debugging for this project.
Works with Claude Code, Codex, Cursor, and any agent with a shell.

Prefer to click around yourself? Download the desktop app

Everything your agent needs

However your agent works, Inspect meets it there — no SDK, no lock-in.

⌨️

CLI

Debug the browser on the device and get back the data your agent needs: console errors, network requests, snapshots — as clean JSON, with errors that explain how to recover.

🔌

MCP

Chrome DevTools MCP connects straight to Inspect's CDP endpoint — MCP-based agents debug real devices with the tools they already have. Puppeteer-compatible clients too.

📚

Skills

npx skills add inspect/inspect — plus workflow guidance served by the CLI itself, version-matched, so your agent's playbook never drifts from the installed tool.

Your agent is blind on mobile

Real bugs live on real hardware — Safari's quirks, WebKit WebViews, Android Chrome, actual network conditions. Inspect speaks Safari's debugging protocol natively and translates it to Chrome DevTools Protocol, and drives Android via ADB — on macOS, Windows, and Linux. No Mac required, no Xcode, no cloud device farm. Simulators and emulators give agents and CI a zero-hardware path; a USB cable gives them the real thing.

Trusted by engineering teams worldwide

Thousands of developers at companies like these ship better mobile experiences with Inspect.

AccentureGiraEventbriteLightspeedPlaidMicrosoftIonicBBVAAffirmFlipkartEpicorYandex

Start free. Pay for unlimited time.

Finding your device is always free, no login. Talking to it — opening a URL, snapshots, console errors, failed requests — runs inside a debug session, and a free account gets two 15-minute sessions a day. Nothing is locked away. Pro removes the limit: $29 for a week when you're fixing one bug, $79/year when mobile is your job.

See Plans

Why Inspect?

Which agents work with Inspect?

Any agent that can run shell commands: Claude Code, Codex, Cursor, Windsurf, custom agents. Point it at inspect.dev/agent.md and it sets itself up. Tools built on Chrome DevTools MCP or Puppeteer connect to Inspect's CDP endpoint directly.

Do I need a Mac? An iPhone?

Neither. Inspect debugs real iOS devices from Windows and Linux too — it speaks Safari's debugging protocol directly, no Xcode involved — and debugs Chrome and WebViews on Android everywhere. No device handy? Your agent can boot an iOS simulator or Android emulator and debug with zero hardware.

What's free?

All of it — the limit is time, not features. Finding and diagnosing your device never costs anything: list devices and targets, run doctor, check status. Everything that talks to the device runs inside a debug session, and a free account gets two 15-minute sessions a day, no login. Pro removes the limit: $29 for a week, $79/year.

How is this different from ios-webkit-debug-proxy?

Inspect is its spiritual successor, several layers up: a full WebKit-to-Chrome-DevTools-Protocol translation, a daemon your agent drives with typed commands and JSON output, console and network capture, and DevTools handoff — not just a raw protocol socket.

Your agent writes the fix. Let it see the bug.