Install REA, then make your first investigation.

Before you begin

Start with a local app you own or have permission to inspect. Make a copy of the target and pick one behavior to understand: an export format, a keyboard shortcut, or a small calculation. A narrow question is easier to verify than “rebuild this entire app.”

REA currently requires Node.js 22.x (22.19 or later), 24.x (24.11 or later), or 26+, with npm. Check both before setup:

node --version
npm --version

Host support and extra tools depend on the target. On Linux, static JavaScript analysis and several tool launches require a procps-compatible ps on PATH. Consult the official requirements for your exact workflow.

Connect your agent

Run the published package’s setup. Select the agents you actually use, inspect the proposed configuration paths, and approve the changes you want.

npx rea-agents@latest setup

Setup connects the MCP server and installs matching investigation instructions. npm’s download prompt and REA’s configuration approval are separate steps. Restart the selected agent when setup finishes. Fully quit Claude Desktop before changing its configuration.

For a preview limited to one client:

npx rea-agents@latest setup --client codex --dry-run

Choose the right analysis path

An extracted JavaScript application or Electron ASAR is a practical first target because static inspection does not require a native decompiler. Native code needs an appropriate provider such as Hopper, Ghidra, or IDA. Check provider availability instead of assuming setup installed every engine.

npx rea-agents@latest providers --json

Hopper installation is optional and requires approval. Ghidra and IDA use existing installations. Commercial tools retain their own license requirements; REA does not include a commercial license.

Inspect a small target

Replace this example path with an extracted application directory or ASAR. Keep the quotation marks when the path contains spaces.

npx rea-agents@latest analyze-javascript-application "/path/to/your/app" --json

Read the result as a map of modules and relationships. It is a starting point for investigation. Next ask your agent to follow one feature and cite the files or addresses that support its explanation.

Verify readiness

npx rea-agents@latest doctor --client codex --json

Doctor checks local configuration and prerequisites. A successful file check does not prove the running agent has established a live MCP session. After restarting, confirm that the agent can discover REA’s tools and run one bounded inspection.