Install

Add the packages

pnpm add -D genie-react @genie-react/cli

Use npm or yarn if the project does not use pnpm.

Wire the app

Run this from the app folder:

npx @genie-react/cli init

init detects Vite and Next.js. Preview its changes first when needed:

npx @genie-react/cli init --dry-run

For a non-interactive run, --yes suppresses only the final post-init tip. It makes the same file changes as init and does not choose among setup options:

npx @genie-react/cli init --yes

Start and check

Keep the development server running in the first terminal:

pnpm dev

Open the app in a browser. Then verify the running setup from a second terminal. doctor reports discovery and remediation as JSON; status must show at least one ready, non-stale session.

doctor_json="$(npx @genie-react/cli doctor --live --json)"
jq '{ok, bridgeCandidates, remediation, live}' <<<"$doctor_json"
jq -e '.ok == true' <<<"$doctor_json" >/dev/null

status_json="$(npx @genie-react/cli status --sessions-only --json)"
jq '{connected, ready, sessionId, sessions}' <<<"$status_json"
jq -e '
  .connected and .ready and
  any(.sessions[]; .ready == true and .staleMs == null)
' <<<"$status_json" >/dev/null

If either assertion exits non-zero, read remediation, keep Terminal 1 running, open or reload the app, and rerun the whole Terminal 2 block.

Do not put doctor or status after pnpm dev in the same shell:

# pnpm dev blocks until you stop the server.

How this helps the agent

The agent can check the complete path from config file to hub, client script, and browser session. It does not need to guess why a tool call cannot connect.