morluto / rea

**English** · 简体中文 · 繁體中文 · 日本語 · 한국어 · Türkçe · Русский · Tiếng Việt · ไทย · Deutsch · Español · Français · Українська · Polski · Português (Brasil) · العربية · فارسی · Bahasa Indonesia · Italiano
· Ελληνικά · മലയാളം
# REA: Reverse Engineer Anything
### One MCP for reverse engineering across binaries, applications, and runtime behavior.
**See a feature you like. Understand how it works, down to the binary level.**
**Website · Guides · Showcases**
Quick start · How REA works · What you can analyze · Showcases · FAQ · Documentation
 npx rea-agents setup 
> [!IMPORTANT]
> Get REA from morluto/rea,
> rea.tools, or the rea-agents npm package.
> Follow the installation and release links from these official sources. A similar
> repository name or copied README does not establish that a download is official.
 Join the Reverse Engineering Community 
 Discord · Q&A · Show and Tell 
---
See a feature in an app that you want in your own product? Ask your agent to investigate it with REA. It can inspect the app without its source code, explain how the feature works, show the evidence, and build a version for your project.
REA connects your agent to tools for inspecting native binaries, JavaScript and Electron apps, .NET assemblies, and websites. You can also use the same tools from your terminal. Analysis runs locally, and results include the evidence and limitations behind each conclusion.
Setup registers REA with your agent and installs matching workflow instructions. Native analysis can use an existing Hopper, Ghidra, or IDA installation; setup can optionally install Hopper with approval. Static JavaScript analysis needs no native analysis engine.
> **Visit the REA website** for setup instructions, illustrated guides, and real case studies.
## Quick start
On Linux, Ghidra, JADX, firmware tool launches and static JavaScript/Electron
analysis require a procps-compatible `ps` on REA's `PATH` for process ownership
checks. Recovery steps are in `docs/installation.md` under
"Linux owned-process prerequisite".
### Set up your agent
With Node.js and npm installed, run:
 [code] 
Choose your agents, review the proposed changes, and approve them. Setup adds
REA's MCP server and matching workflow instructions, with backups of existing
configuration. Restart your agent afterward.
Setup supports Claude Code, Codex, Cursor, Gemini CLI, Grok Build and
other agents. See
installation and setup for provider configuration and
manual MCP registration.
### Ask your agent
 [code] 
Replace Notes with your target app and the feature you want to understand.
### Use the terminal
Inspect an extracted JavaScript/Electron app directory or ASAR:
 [code] 
The result includes modules, imports, Electron boundaries and their evidence.
Replace the path with your target, such as `"D:/apps/example"` on Windows.
To install the `rea` command for regular use:
 [code] 
For native analysis, configure a provider first. See the
CLI and Evidence guide for native commands, provider selection,
snapshot