On this page
If you need a Copilot browser tools alternative because the agent drove the page, reported success, and the change was still broken, Reticle adds a verdict decided from network, app state and console, replayed with no model. If you want Copilot to open and click your app in VS Code with nothing to install, its built-in browser tools are the default.
What Copilot browser tools do
GitHub announced them as generally available on 2026-07-01: "Agents can now drive a real browser, navigate live web apps, and feed what they find back into the chat" (changelog).
Copilot agents use VS Code's integrated browser to open pages, click, type, hover, drag, handle dialogs, read content, capture console errors, take screenshots and run scripted step sequences. They are on by default; admins control them with a setting and domain allow and deny lists. They need a GitHub Copilot subscription (guide). Tabs the agent opens start with fresh sessions and no cookies, and your own tabs are only used if you share them.
What Reticle does
Reticle checks an AI coding agent's change from inside the running web app and returns a verdict with evidence. It reads the network calls, the application state and the console, and on React and Svelte it names the file:line to fix.
Any MCP agent calls it while it works. Flows it drives are saved and replay deterministically, with no model in the loop. It also works on sites you don't own: it drives the page in its own browser and injects its SDK, reading network, console, DOM and routing; app state and file:line need the SDK in your own build. The SDK is open source (Apache-2.0).
Copilot browser tools vs Reticle at a glance
| Copilot browser tools | Reticle | |
|---|---|---|
| What it gives the agent | A real browser: clicks, content, console errors, screenshots | A verdict: pass, fail or cannot tell, with evidence |
| Who decides it worked | The model, reading the page | A declared expected outcome, checked after the step settles |
| Network counts and app state | Not read as a check | Read on every step (state with the SDK in your build) |
| Re-running a check | The agent drives it again | Deterministic replay, 0% flake over 8 replays |
| Setup | On by default in VS Code | MCP config plus a small SDK, or one line to your agent |
| Pricing | Any Copilot subscription | Open-source SDK free; platform starts free |
Where Copilot browser tools are the better choice
- Nothing to install. Every Copilot user in VS Code already has them.
- Admin control in one place. Domain allow and deny lists and a single setting for the organisation.
- Driving and reading pages broadly. Hover, drag, dialogs and scripted steps across any site the agent is allowed to visit.
- A quick visual pass. For "does it render", the agent's own look is fine.
Where Reticle is the better choice
- Correct-looking failures. A double-submitted payment, a 500 hidden under a success toast, a store that disagrees with the page. Reticle checks request counts, state and console against what the step should do, so these fail.
- Repeatable checks. A saved flow re-runs with no model: about 480 tokens to re-verify four flows, about 251 times less than a model re-drive, with the same verdict every time.
- One check across tools. The same flows run from Copilot, Claude Code, Cursor, Codex and CI.
On 88 seeded bugs, Reticle caught 85 with no false alarms (scorecard).
Can you use both?
Yes. Let Copilot's browser do the driving and looking, and let Reticle decide whether the change worked and keep that check for the next commit. The case for checking behaviour, not pixels, is in what AI verification is. Other agent browsers are compared on the MCP browser testing page.
Try Reticle
Paste one line to your agent, and it installs and wires the SDK in your app:
Follow https://raw.githubusercontent.com/reticlehq/reticle/main/SKILL.md
FAQ
Can GitHub Copilot test my web app?
Yes. GitHub Copilot can test your web app in VS Code with its browser tools, generally available since July 2026: the agent opens pages, clicks, types, reads console errors and takes screenshots. The model judges what it sees, so a change that looks right but sends the wrong request can still pass without a separate check.
What is an alternative to Copilot's browser tools?
An alternative to Copilot's browser tools is Reticle, which gives the agent a verdict instead of a view. It checks network, app state and console against the expected outcome and replays saved flows with no model. Playwright MCP, Chrome DevTools MCP and Vercel's agent-browser are other ways to drive the page.
Does Reticle work in VS Code?
Yes. Reticle works with any coding agent that speaks MCP, including agents running in VS Code. You add the Reticle MCP server to the agent's configuration, or paste the SKILL.md line and let the agent wire the SDK in your app. The same saved flows also run in CI with one command.
Why Reticle
Your agent says it works. Reticle checks.
- Checks each change inside the running app: network, state and console, not a screenshot.
- Returns a pass or fail with the evidence and the file:line to fix.
- Open-source SDK on your machine, or the platform on every preview and PR.
No credit card required.