reticlehq/reticle

drive-desktop-app

Drive and verify an Electron or Tauri desktop app from the inside, including the main-process and Rust IPC calls a browser tool cannot see.

Zobacz źródło
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

Drive a desktop app and prove what happened

A desktop app reaches its backend over IPC, not HTTP. Patching fetch/XHR cannot see that, so a browser-shaped tool is blind to every backend call the app makes: the network log reads empty, an action has no in-flight request to settle on, and asserting on the network is vacuously true. That is a false green by construction.

Reticle observes the renderer and the IPC boundary, so a desktop verdict means what a web one does. Not installed? RETICLE_INSTALL_SOURCE=npx_skill npx @reticlehq/server@latest init, then the `install-and-verify` skill.

Electron: two lines, none in your app code

ts
// vite.config.ts — desktop:true also runs the plugin for `vite build`, because a packaged
// renderer is a production build with no dev server
export default defineConfig({
  base: './', // file:// needs relative asset paths
  plugins: [react(), reticle({ desktop: true })],
});
js
// electron/preload.cjs — FIRST line. This is what makes main-process IPC visible.
require('@reticlehq/electron/preload');

It must be in the preload and it must be first. contextBridge.exposeInMainWorld hands the renderer a deeply frozen object, so nothing in the page can instrument it afterwards. The preload is the last point where ipcRenderer.invoke is still writable, and the shim has to run before your preload captures its own reference.

A sandboxed preload cannot resolve node_modules, so the bare require fails. Either bundle the preload (electron-vite and Forge do by default) or set sandbox: false.

Tauri: the CSP step is required and its failure is silent

The frontend is the same as any web app. The part people miss is that Tauri's default CSP blocks the bridge WebSocket before it opens, so the app runs perfectly and simply never connects:

json
{
  "app": {
    "security": {
      "csp": "default-src 'self' ipc: http://ipc.localhost; connect-src 'self' ipc: http://ipc.localhost ws://localhost:4400 ws://127.0.0.1:4400"
    }
  }
}

Keep ipc: http://ipc.localhost: Tauri v2 needs it for invoke itself. Dev-only; drop the ws:// entries from your release config.

IPC observation needs nothing on the Rust side: an invoke('load_todos') already reaches Reticle as ipc://load_todos. The `reticle-tauri` crate is only for screenshots and headless, and it is versioned independently of the npm packages.

Also: use a hash router. A packaged renderer is served from file://, where history-based routing does not resolve.

Verify

Same loop as the web, with IPC in the predicates:

reticle_act_and_wait({ sessionId, ref, action: "click", until: { kind: "allOf", predicates: [
  { kind: "net",     urlContains: "ipc://todos:archive", status: 200 },
  { kind: "element", query: { testid: "..." } },
  { kind: "console", level: "error", absent: true },
]}})

IPC has no status code. 200/500 are synthetic, mapped from whether the command succeeded, precisely so the same predicates keep working. On Tauri you will see status: 500 next to statusText: "OK". That is not a bug: the transport answered fine and the 500 is the command's own verdict. ok is authoritative.

reticle_state reads the live store exactly as on the web. reticle_screenshot and reticle_visual_diff work once the platform's capture step is wired. Electron needs nothing extra; Tauri needs the crate. Headless on Tauri is RETICLE_HEADLESS=1, and screenshots keep working because the capture renders the webview rather than the screen.

What a missing observer looks like

A missing Electron preload is declared, not silent: verdicts come back with coverage: partial naming the line you did not add, instead of reading clean over a blind spot. If you see that, add the preload line before trusting anything.

If IPC calls never appear while the app works fine: on Electron, the shim's require is not first. On Tauri, invoke from @tauri-apps/api/core is observed, but a hand-rolled postMessage protocol is not.

Honesty

unknown is not a pass on the desktop either. And do not weaken an IPC assertion to make a red verdict green: a desktop false green is the exact failure this wiring exists to remove.


Full desktop reference: curl https://docs.reticle.sh/desktop.md. Everything else: curl https://docs.reticle.sh/llms.txt.

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
reticlehq
Społeczność

audit-my-app

Sweep a whole running web app for what is broken, without writing a script or knowing the codebase. Clicks every reachable control and reports dead buttons, console errors, failed requests, and places where the API and the screen disagree. Use on an unfamiliar codebase, before a release, after a big merge or dependency bump, when the user asks for a smoke test or a health check, or when someone says "just check everything still works".

instalacje
1
GitHub Stars
900
Aktualizacja
26 wrz
reticlehq
Społeczność

debug-broken-ui

Find out why something in a running web app does not work, when the console is empty and the code looks correct. Reads the click, the request, the store and the console together and returns the file:line to open. Use when a button does nothing, a form will not submit, data will not load, a page renders blank or stale, a modal will not close, or the user says "it's broken" and the code review says it is fine.

instalacje
1
GitHub Stars
900
Aktualizacja
26 wrz
reticlehq
Społeczność

fix-what-i-pointed-at

Pick up the bugs a human flagged by pointing at them in the running app, each arriving with the element, the note they typed, and the source file and line. Use when the user says they marked or flagged something, when starting a session on an app someone has been clicking through, when a designer or PM has left feedback in the UI, or when the user describes a problem as "that button there" without saying which file.

instalacje
1
GitHub Stars
900
Aktualizacja
26 wrz
reticlehq
Społeczność

replay-user-flows

Turn a user journey you just clicked through into a saved regression check that re-runs deterministically, with no model in the loop and no test code to write. Use when you have driven the same flow twice, when the user wants regression coverage without a Playwright suite, when a refactor needs proving against every existing journey, or when re-verifying by hand is costing a full drive every time.

instalacje
1
GitHub Stars
900
Aktualizacja
26 wrz