Install REA and run your first analysis

Check the prerequisites

The official README currently specifies Node.js 22.x from 22.19, 24.x from 24.11, or 26 and above, plus npm. Check the current requirements before installing, as supported versions can change.

Start with local JavaScript analysis if you want to avoid configuring a native decompiler. Native analysis needs a supported engine. On Linux, JavaScript/Electron and several tool launch workflows also require a procps-compatible ps command on PATH.

node --version
npm --version
# On Linux:
ps --version

Register REA with your agent

Run the official setup command. Select your agent, review the proposed configuration and workflow instruction changes, and approve the changes you intend to apply. Setup backs up existing configuration. Restart your agent after setup.

REA supports multiple coding agents. Check the official installation guide for the current list and manual MCP registration options.

npx rea-agents@latest setup

Try a small local JavaScript target

Choose an extracted application directory or ASAR file that you own or are authorized to examine. Use an absolute path. This static operation reads the supplied application files without executing the application.

Inspect the returned modules, imports and Electron relationships. Missing relationships or incomplete results should stay unresolved until you obtain more evidence.

npx -y rea-agents@latest analyze-javascript-application \
  /absolute/path/to/your-app --json

Give the agent a bounded task

A first investigation should have a clear finish line. Ask the agent to locate one feature and explain the evidence before asking it to write code.

Use REA to locate the export entry point in this local app.
Trace the modules and IPC calls involved.
Cite the exact source locations.
Report what static analysis cannot confirm.

Keep setup and analysis problems separate

If a command fails, record the REA version, operating system, selected engine, target type and complete error. Check the official installation and troubleshooting instructions before changing several settings at once.

For repeatable work, record the package version used. Updating may resolve a bug, but it can also change result contracts; preserve old evidence and verify downstream scripts when upgrading.