Your environment. Your setup path.
Build a guide you can take to your terminal. This assistant does not inspect or change your computer.
Start with your environment
Run node --version and prepare a supported runtime before connecting your agent.
node --version
npm --version
npx rea-agents@6.5.0 setup --client claude_code --dry-run
npx rea-agents@6.5.0 setup --client claude_code
npx rea-agents@6.5.0 doctor --client claude_code --jsonPreview the plan, approve setup in your terminal, and restart Claude Code. Doctor verifies registration; check a small analysis target afterward.
REA with Claude Code: the basic sequence
Use Node 22.19+ (22.x), 24.11+ (24.x), or 26+, with npm available. Preview the plan first, then run setup and approve the proposed changes in your terminal. Restart Claude Code afterward.
npx rea-agents@6.5.0 setup --client claude_code --dry-run
npx rea-agents@6.5.0 setup --client claude_code
npx rea-agents@6.5.0 doctor --client claude_code --jsonFor Codex or Cursor, replace claude_code with codex or cursor. A client-scoped doctor check verifies registration, not a successful investigation of your target.
REA, Ghidra MCP and choosing an engine
| Target | What to prepare | First check |
|---|---|---|
| JavaScript / Electron | A readable directory or supported ASAR. No Ghidra required. | Our frozen-source case |
| Browser behavior | A Chromium debugging session configured with the official guide. | Check the page and debugging endpoint. |
| Native binary | A compatible Ghidra, Hopper or IDA installation; requirements differ. | Verify the engine starts independently, then follow its setup guide. |
Check the official experimental-support notes for Windows Ghidra. Relevant Linux process checks need a procps-compatible ps. Do not copy another Ghidra MCP project’s configuration into REA.
Upstream Ghidra setup →Keep the first task small
Once connected, try a specific question: “Use REA to inspect this directory. Find the function that builds setup commands, report source locations and calls, and distinguish resolved from unresolved relationships.”
Download and reproduce the case →Explore your next question
- When to use REA vs a regular coding agent
Choose REA for evidence from shipped binaries and packages. Use ordinary repository tools for complete source, and measure added value with a bounded test.
- REA MCP: how the client, server and engines fit
Understand REA MCP before setup: separate agent registration, MCP tool discovery and analysis-engine readiness for JavaScript, browser and native targets.