/Catalogue/Prompt/reticlehq/reticlehq-reticle-drive-desktop-app

Origin: github

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. Use when a desktop app needs testing, when a feature works in the browser but not in the packaged app, when an IPC or invoke call needs proving, when a desktop screenshot or visual diff is wanted, or when you need a headless run of a desktop UI in CI.

by reticlehq · updated 4h ago · imported from GitHub

Installs0+0/7d
Security score100/100
Retention 14d0%
GitHub stars851

Skill logic

Execution graph
User message
Prompt rewrites behaviour
Response

SKILL.md

View on GitHub ↗

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

// 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 })],
});
// 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:

{
  "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.

Discussion

No comments yet — start the thread.

Sign in to join the discussion.

/More from reticlehq/reticle

reticlehq· 4h agoSandbox
reticle

Prompts · TypeScript · v0.1.0

Reticle embeds a dev-only SDK in the user's running app and exposes it to you as `reticle_*` MCP tools. You look, act, observe, and assert against the real app. No screenshots, and no browser download for the verify loop: it drives the tab the user already has open.

#agent-skill#agent-skills#agent-testing

0 851
reticlehq· 4h agoCommunity
reticle

Prompts · TypeScript · v0.1.0

Install, instrument and verify this running web app from the inside (DOM, network, routing, console and framework state) instead of screenshots or guessing. Drives one real flow end to end and returns a verdict with the file:line to fix. Use when the user asks to set up or install Reticle, when a user-facing change needs proving before you call it done, when a test passes but the UI is broken, or when the user types /reticle.

#agent-skill#agent-skills#agent-testing

0 851
reticlehq· 4h agoCommunity
agentic-tdd

Prompts · TypeScript · v0.1.0

Test-driven development for behaviour a unit test cannot reach, by writing the expectation against the running app before writing the code. Declare the consequence first, watch it fail, implement, watch it pass. Use when building a user-facing feature, when the user asks for TDD on UI or full-stack work, when a unit test cannot express the outcome that matters, or when you want a red-green loop that runs against the real app instead of mocks.

#agent-skill#agent-skills#agent-testing

0 851
reticlehq· 4h agoCommunity
audit-my-app

Prompts · TypeScript · v0.1.0

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".

#agent-skill#agent-skills#agent-testing

0 851