Tool reference

The built-in collectors expose 80 tools. The active app may expose fewer, and can add its own under the app group (App tools). Run status to see its domains, then discover one exact contract:

npx @genie-react/cli tools react_render_causes

All calls use this shape:

npx @genie-react/cli call <tool> '<JSON input>'

Every entry includes the exact input, a call, selected output fields, and the decision that output enables. The examples come from live demo runs, source tests, or the validated contract. IDs, counts, paths, and times change with the app.

Commands return JSON by default. Existing --json examples remain valid. Use the live contract above as the source for your installed version, and read CLI output when parsing, projecting, or saving results. A successful process exit alone does not prove a wait condition was met; use --fail-on-result-error with devtools_wait and react_quiesce in scripts.

Rules for safe use

• Target one named session before changing live state.
• Use devtools_interaction_begin and devtools_interaction_stop to join renders, causes, effects, and coverage under one interaction ID. Use the timeline when the question spans requests, Query updates, React commits, and navigation.
• Read coverage, omissions, truncation, and evictions.
• Treat inferred and unknown as leads, not proof.
• Distinguish effect scheduling, execution, cleanup, and observed consequences.
• Restore Query simulations and React overrides.