On this page
If you want a Shiplight alternative that reads your app's own state and maps a failure to the source line, not only what the browser shows, Reticle is built for that. If you want agent-written regression tests in plain-English YAML that export to standard Playwright, Shiplight is the stronger choice.
What Shiplight does
Shiplight calls itself "The agent-native testing platform" (shiplight.ai). A coding agent drives a real browser through Shiplight's MCP server to verify UI changes, and each action is saved as a plain-English YAML test. Saved tests replay from cached steps, self-heal stale locators, and export to Playwright. They run locally, on Shiplight's CI runners, or on your own infrastructure (coding agents).
It ships skills such as /verify, /create-tests and /review for Claude Code, Cursor and Windsurf. Pricing is public: free, Pro at $60 a month, and Enterprise on request, with your own model key on any plan (pricing, checked 2026-10-25). We found no public source repository; its MCP package on npm is labelled MIT.
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.
Your agent calls it through MCP while it works. Flows it drives are saved and replay deterministically, with no model in the loop. The SDK is open source (Apache-2.0) and runs on your machine; the hosted platform runs the same checks on previews and pull requests.
Shiplight vs Reticle at a glance
| Shiplight | Reticle | |
|---|---|---|
| Where it looks | The browser, through Playwright | Inside the app (SDK), plus a driven browser |
| What a check reads | Console, network and DOM at browser level | Network count, app state, console and DOM after each step |
| Saved tests | Plain-English YAML, exportable to Playwright | Flow files in .reticle/flows/, committed with your code |
| Re-running | Cached steps with self-healing locators | Deterministic replay, no model in the loop |
| App state (store) | Not read | Read, with the SDK in your build |
| Points to the fix | The failing step | The failing request or state, and file:line on React and Svelte |
| Sites you do not own | Yes | Yes (no app state or file:line) |
| Open source | MCP package MIT; platform closed | SDK Apache-2.0; server FSL-1.1 |
| Pricing | Free; Pro $60/month | Start free, no card; open-source SDK free |
Where Shiplight is the better choice
- You want portable Playwright tests. Exporting to standard Playwright reduces lock-in and fits an existing release suite. Reticle's saved flows replay with Reticle.
- You want readable YAML tests that people who do not write code can review.
- You want built-in review skills. Shiplight ships accessibility, security and performance review skills alongside verification.
- You want nothing in your build. Shiplight works at browser level. Reticle drives sites without its SDK too, but app state and file:line need it.
Where Reticle is the better choice
- The bug lives in app state. A store that disagrees with the total on the page, or an action that changes state nobody rendered. Browser-level reads cannot see a store; Reticle reads it.
- You want the source line. On React and Svelte the verdict names the
file:line, so the agent edits the right file instead of guessing from a selector. - You want counts, not just presence. Reticle checks how many times a request fired, so one click that sends two charges fails.
- You want measured, model-free replay. Eight replays gave one verdict, and four flows re-verify in about 480 tokens, about 251 times less than a model re-driving them.
On 88 seeded bugs, Reticle caught 85 with no false alarms, with one genuine miss (scorecard).
Can you use both?
Yes. Shiplight's exported Playwright tests can stay your cross-browser release gate while Reticle is the inside check your agent runs on each change. How the two layers divide the work is in Reticle vs Playwright Test. Related: the TestSprite alternative and all alternatives.
Try Reticle in five minutes
Paste one line to your coding agent, and it installs and wires the SDK in your app:
Follow https://raw.githubusercontent.com/reticlehq/reticle/main/SKILL.md
Or run npx @reticlehq/core init yourself. The README has the details.
FAQ
What is the best alternative to Shiplight?
The best alternative to Shiplight depends on what you need to see. For checks that read your app's state and point to the source line, Reticle fits. For hand-written cross-browser tests, Playwright fits. For another tool that turns agent browser sessions into YAML regression tests, look at other agent-native testing platforms.
How is Reticle different from Shiplight?
Reticle is different from Shiplight in how deep it reads. Shiplight works at browser level through Playwright and saves plain-English YAML tests. Reticle runs inside the app, reads application state as well as network and console, counts requests, and names the source line on React and Svelte, then replays saved flows with no model in the loop.
Can Reticle export tests to Playwright?
No, Reticle does not export its saved flows to Playwright. Flows live in .reticle/flows/, are committed with your code, and replay with Reticle locally or in CI. If you need tests in standard Playwright for a cross-browser release suite, Shiplight or Playwright itself does that, and Reticle can run alongside.
Is Shiplight open source?
Shiplight is not open source as far as we could find: there is no public source repository, though its MCP package on npm is labelled MIT. Reticle's in-app SDK is open source under Apache-2.0 and runs locally, and its server is source-available under FSL-1.1, which becomes Apache-2.0 after two years.
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.