# REA

> Let your coding agent reverse engineer an app, from its behaviour down to the native binary

- Category: Agents & Automation / Security Agents
- Language: TypeScript
- Licence: MIT
- Repository: https://github.com/morluto/rea
- Canonical page: https://ai-tldr.dev/tools/rea/
- Updated: 2026-10-08

## In short

REA (Reverse Engineer Anything) is an open-source TypeScript CLI and MCP server that gives AI coding agents one consistent way to investigate software they do not have the source for. It sits in the Security Agents category of the Agents & Automation tools and is open-source, written in TypeScript and licensed MIT.

## Overview

REA (Reverse Engineer Anything) is an open-source TypeScript CLI and MCP server that gives AI coding agents one consistent way to investigate software they do not have the source for. You point your agent at an app, ask how a feature works, and REA lets it decompile the binary, follow the code between functions, and show the evidence behind its explanation. The project describes the workflow in three steps: decompile, understand, recreate.

Deep native analysis runs through Hopper or a Ghidra installation you supply, on macOS and Linux, with an experimental Ghidra-only path for native x86 and x86-64 Windows applications. REA installs and manages Hopper for you (its free demo mode is supported), while the Ghidra adapter runs read-only and exposes inventory, decompilation, assembly, cross-references, call graphs and function dossiers. Beyond native binaries it covers managed PE/CLI triage, passive observation of websites, Electron pages and Node/Electron V8 Inspector sessions, JavaScript and source-map reconstruction, and controlled process capture.

Analysis runs on your own machine and REA does not upload the app to a hosted service. Results are recorded as reproducible Evidence bundles that can be imported, exported and compared, and the project is explicit that it does not claim to recover original source code or automatically clone an application. A guided setup registers REA with Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, Grok Build and Windsurf.

## What it does

- Same reverse-engineering capabilities from the terminal (rea analyze, rea decompile) or from an agent over MCP, with a bundled routing skill
- Native binary analysis through Hopper or a bring-your-own Ghidra 12.1.4 provider: decompilation, assembly, xrefs, call graphs, control-flow graphs and function dossiers
- Static analysis of JavaScript and Electron apps (directories or .asar) without executing them, plus passive website, Electron and V8 Inspector observation
- Reproducible Evidence records that can be validated, canonicalized and compared between investigations
- Reviewed, backup-first setup that detects installed agents, shows every change before applying it, and can be undone with rea uninstall
- Local by design: analysis runs on your machine with no hosted analysis service

## Getting started

REA needs Node.js 22.19+ (or 24.11+) on macOS 12+, Ubuntu 24.04+, Fedora 41+ or 64-bit Arch Linux. Run the setup wizard once, then either ask your agent or use the CLI directly.

1. Run the setup wizard

   Setup detects your agents and asks which capabilities to configure: agent integration (MCP registration plus the matching routing skill) and, if needed, the Hopper provider. Nothing is preselected and nothing changes until you approve the final plan. Restart the configured agent afterwards.

```bash
npx --yes rea-agents@latest setup
```

2. Ask your agent

   Once REA is registered, describe the app or feature you want to understand. Notes is only the README's example; name any app.

```text
Understand how search works in the Notes app, show me the evidence, and build a
similar feature for my project.
```

3. Or install the rea command and use the CLI

   Install globally to get a shell-visible rea command, check the environment with doctor, and analyze an app. rea upgrade updates a global install in place.

```bash
npm install --global rea-agents
rea setup
rea doctor
rea analyze /Applications/Notes.app
```

4. Optional: use Ghidra instead of Hopper

   Download Ghidra 12.1.4 and a full JDK 21 yourself, point REA at them, then let doctor verify the installation and setup copy the paths into your MCP registrations.

```bash
export GHIDRA_INSTALL_DIR=/absolute/path/to/ghidra_12.1.4_PUBLIC
export JAVA_HOME=/absolute/path/to/jdk-21
rea doctor --json
rea setup
rea providers --json
```

## When to use it

- Working out how a feature in a closed-source app is implemented so you can build your own version adapted to your stack
- Giving a coding agent decompilation, cross-reference and call-graph access to a native binary instead of letting it guess
- Mapping a JavaScript or Electron application from its .asar without running it
- Keeping reproducible, comparable evidence of what an investigation found across app versions

## Version history

- 2026-10-08 v6.0.0: Adds offline EVM bytecode inspection, ELF layout and recorded-crash inspection through pwntools and pwndbg, LLDB call observation and native x86 PE support in Ghidra on Windows. Breaking: MCP filesystem inputs must now be absolute host paths; 6.1 to 6.3 followed on October 9 with more breaking schema changes.
- 2026-10-06 v4.1.0: Adds static Android APK analysis through headless JADX, firmware analysis through Binwalk and Unblob, read-only IDA GUI and headless providers, and Windows x64 read-only analysis in Ghidra. It follows the breaking 4.0.0 release, which removed replay and permission-policy features.
- 2026-10-03 v3.2.0: Adds new native investigation features and returns complete native analysis results from the Ghidra provider, alongside a batch of boundary and cleanup fixes.
- 2026-08-09 v3.1.0: Adds autonomous Electron runtime analysis and hardens the Evidence lifecycle and MCP contracts.
