Admit same-major Ghidra releases at or above the verified minor through the existing compatible/unverified policy. Preserve the observed version, verified12.1.4 pin, installation-declared Java floor and separate NativeAOT verification gate. 367 targeted tests/static/docs, all10 real Java bridge-source compilation, and actual Linux12.2/JDK25 CLI/MCP queries and cleanup pass. JDK21 remains refused for12.2. Exact-main controls reproduce all3 unrelated CI assertions; canceled shards and an apt-blocked binary-layout lane remain unverified. Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
97 KiB
Installation and setup
Run REA, connect your selected agents, and check the tools needed for your task. Setup previews configuration changes and asks for approval before applying them.
| Task | Section |
|---|---|
| Connect an agent | Start setup, then review changes |
| Diagnose one task | Scoped readiness checks |
| Configure an analysis engine | Hopper, Ghidra, the IDA guide, or Kuna |
| Update or remove REA | Maintenance |
| Resolve a client-specific problem | Client configuration |
Start setup
npx rea-agents setup
Choose the agents to configure, review the proposed paths and changes, and approve the plan. npm's package-download approval and REA's setup approval are separate. Setup asks before changing agent configuration or installing Hopper. Restart the agents named in the completion message. Quit Claude Desktop fully before approving, because a running app can overwrite the registration; on Windows, see where Claude Desktop reads its configuration.
During package resolution, npm may print a deprecation warning for prebuild-install
from transitive native dependencies (such as Frida). This warning originates from
the upstream dependency tree and does not affect REA or indicate setup failure.
For the latest published release, use npx rea-agents@latest setup.
Package-runner and global-installation options
cover explicit versions, Bun, runtime requirements, and the curl wrapper.
Review setup changes
rea setup first offers the supported agents in a multi-select. Existing REA
registrations are selected by default. Newly detected clients remain available
but unselected: detection gives setup co