REA with an agent vs opening Ghidra yourself

Last updated: · By the RepoRead editorial team · Unofficial guide
Quick answer

REA connects an AI coding agent (or the rea CLI) to local reverse-engineering tools. Ghidra is one of those tools. Choosing “REA” versus “just Ghidra” is really choosing orchestration + Evidence versus interactive GUI exploration — and for native work you often still need Ghidra installed either way.

Only analyze software you are authorized to examine.

Side-by-side

DimensionInteractive GhidraREA + agent (Ghidra provider)
Primary UIGhidra project windowYour MCP-capable agent + optional CLI
EngineGhidra itselfSame Ghidra install via GHIDRA_INSTALL_DIR
Best forDeep manual navigation, renaming, patching in-UIRepeated questions, scripted inspect/decompile/xrefs with Evidence
Output shapeProgram database / UI stateStructured Evidence + agent narration
SetupJDK + GhidraNode.js + npx rea-agents setup + Ghidra/JDK
Cost$0 (Apache-2.0)REA MIT; Ghidra still $0; agent/model separately

When to open Ghidra yourself

  • You are learning control-flow graphs and want to click around.
  • You need heavy manual renaming, bookmarks and patch experiments in the classic UI.
  • Your team already lives in shared Ghidra projects and headless scripts without agents.

When REA + agent helps

  • You want to ask natural-language questions and get Evidence-backed slices (functions, xrefs, decompilations) into the chat.
  • You already use Claude Code, Cursor, Codex, Gemini CLI or another local MCP client (supported agents).
  • You mix targets: Electron/.NET static lanes without Ghidra, then native lanes with Ghidra when needed.
export GHIDRA_INSTALL_DIR=/absolute/path/to/ghidra_12.1.4_PUBLIC
rea doctor --provider ghidra --json
rea analyze /absolute/path/to/program --provider ghidra --json
rea decompile /absolute/path/to/program 0x1000 --provider ghidra --json

Shared rules

Ghidra line cited by REA12.1.x (bridge verified with 12.1.4 + JDK 21 per REA docs)
REA licenseMIT (REA-authored code)
Ghidra licenseApache-2.0
AuthorizationRequired for every target
Verified2026-10-18 (UTC)

Neither path authorizes DRM bypass, pirated analysis engines or analyzing software without permission. REA's disclaimer closes such requests without support.

FAQ

Does REA replace Ghidra?

No. For deep native analysis REA drives an engine you already installed (Ghidra, Hopper or IDA). Interactive Ghidra remains useful for exploratory UI work.

Does REA install Ghidra for me?

No. Extract Ghidra and a matching JDK yourself, set GHIDRA_INSTALL_DIR, then rea doctor --provider ghidra. See Ghidra setup.

Which is “more accurate”?

Pseudocode quality comes from the engine and the binary, not from the MCP wrapper. REA adds Evidence structure and agent tooling; it does not magically fix bad decompilation.

Can I use both?

Yes. Many analysts explore in the Ghidra UI, then automate recurring questions through REA + an agent on the same authorized targets.

Is RepoRead affiliated with the NSA or Hex-Rays?

No. RepoRead is an unofficial REA guide. Ghidra is an NSA open-source project; IDA is Hex-Rays commercial software.

Sources