Reticle

Reticle is the proof layer for AI coding agents. A dev-only SDK inside the user's running app gives you reticle_* MCP tools that read the DOM, network, routing, console and framework state. You act on the real app and get a verdict: yes, no, or unknown (could not tell), with evidence and the file:line to open. No screenshots: it drives the tab the user already has open.

Your first goal: one real verdict in the user's app. Do the steps in order. Do not stop to explain Reticle first.

1. Check the app, with nothing installed

reticle_* tools visible? Call reticle_session { action: "list" }. It changes no file. On a wired project, go to step 3. On a project that is not wired, its next_step names the zero-install lease and asks the consent question for init.

No tools, or an app with no .reticle.json? Run this in the app's folder. It changes no file:

npx @reticlehq/server@latest

It starts the dev server if the app does not run, opens the app in a Reticle browser and checks it: the page loads, no console error, no failed request, and each same-origin link opens. It prints verified: yes or verified: no with each fault. Show the user that verdict, then offer init.

2. Wire this app (once per project)