Module backends 

Backends that turn a capability into typed crate::Tools.

Modules

control

Tools for one Right Suite app, reached through its in-app control service (rightkit-qa-driver’s embedded server, a rightkit-daemon host named control-<app>). Real webview input, DOM/AX query, screenshot, and the app’s own typed commands (command{name,args}), all over the user-only socket/pipe with the service’s per-app request allowlist on the far side.

desktop

desktop.* tools over rightkit-automation: observe and act on any allowlisted app (macOS AX, Windows UIA) through the automation engine’s own gates (allowlist, kill switch, lease fence, freshness, secure-field and credential gates, admission hook, tier ladder). This module adds only the typed JSON surface; it deliberately exposes no text delivery, no clipboard and no dictation entry points (HeardRight’s rules, see exposure).

speech

Speech tools over the shared speech service (rightkit-speech-client, the first client of this crate). File transcription only: the service allowlist carries health, capabilities, info and file requests, and nothing here reaches dictation, paste, or history.

web

browser.* tools over rightkit-browser (Chrome over CDP): open, read (text plus ref-addressed observation), click and type with real Input.dispatch* events, screenshot, console, close. The session is lazy (first browser.open), isolated (temporary profile unless the caller passes LaunchOptions with a named one), muted, and bound by rightkit-browser’s network policy (loopback, private ranges and file: blocked unless the caller’s LaunchOptions allow them). Dropping the BrowserTools shuts the browser down.