reticle_sessions - Reticle

{}

Real response, one session shown:

{
  "sessions": [
    {
      "sessionId": "s7fe3a790-ab02-4ebb-82b2-24d08a76fd59",
      "url": "http://localhost:4312/",
      "title": "Reticle · Mission Control",
      "adapters": ["react"],
      "hasCapabilities": true,
      "hidden": true,
      "throttled": true,
      "focused": false,
      "lastSeenMs": 21944,
      "realInputAvailable": false,
      "leased": false,
      "attachment": { "connectedSinceMs": 827874, "outages": 0 },
      "recommendation": "tab hidden/throttled and may be un-focusable from here; refocus it, or run `reticle drive <url>` for a guaranteed scriptable context"
    }
  ]
}

The fields that decide whether driving will work

Field	Why it matters
`throttled`	The browser is deprioritising a background tab. Synthetic timers and pointer gestures may silently no-op
`hidden` / `focused`	Why it’s throttled, and what to do about it
`hasCapabilities`	Whether the app registered testids, signals and stores. `false` means `reticle_state` has nothing to read
`adapters`	`["react"]` means you get component names and source pointers
`realInputAvailable`	`true` when native CDP input is available, under `reticle drive`
`outages`	How often the connection has dropped. Non-zero is worth investigating

throttled: true is the most common cause of “the click did nothing”. Focus the tab, or drive a dedicated context. It is not your app being broken. It is the browser saving battery on a tab nobody is looking at.

Confirm after navigating

reticle_navigate can only report that a navigation was dispatched. sessions is how you confirm one arrived: a session at the new URL means the page loaded and is instrumented. No session means one of those two is false, and you find out now rather than after three confusing failures.

Scoping

You rarely need to pass sessionId to other tools. Reticle scopes to your project, prefers the active tab, and refuses rather than guesses when the choice is ambiguous. A refusal you can act on beats a silent pick of the wrong tab. Pass it explicitly when you genuinely mean one specific tab, such as when testing two apps at once.

Sessions accumulate. A stale entry pointing at a dev server you have since restarted will sit there looking plausible. reticle_session { action: "end" } clears one out.

Last modified on August 14, 2026

⌘I