**English** · [简体中文](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_zh.md) · [繁體中文](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_zh-TW.md) · [日本語](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_ja.md) · [한국어](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_ko.md) · [Türkçe](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_tr.md) · [Русский](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_ru.md) · [Tiếng Việt](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_vi.md) · [ไทย](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_th.md) · [Deutsch](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_de.md) · [Español](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_es.md) · [Français](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_fr.md) · [Українська](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_uk.md) · [Polski](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_pl.md) · [Português (Brasil)](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_pt-BR.md) · [العربية](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_ar.md) · [فارسی](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_fa.md) · [Bahasa Indonesia](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_id.md) · [Italiano](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_it.md) · [Ελληνικά](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_el.md) · [മലയാളം](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_ml.md) · [Roman Urdu](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_ur-Latn.md) · [Română](https://github.com/morluto/rea/blob/HEAD/docs/readme/README_ro.md) # 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.** [](https://www.npmjs.com/package/rea-agents) [](docs/mcp-contracts.md#generated-catalog) [](#what-you-can-analyze) [](https://skills.sh/morluto/rea/reverse-engineer-anything) [](LICENSE) [](https://discord.gg/GkcryMnJDM) **[Website](https://rea.tools/) · [Guides](https://rea.tools/guides/) · [Showcases](https://rea.tools/showcase/)** [Quick start](#quick-start) · [How REA works](#how-rea-works) · [What you can analyze](#what-you-can-analyze) · [Showcases](#showcases) · [Build RL environments](#build-rl-environments) · [FAQ](#faq) · [Documentation](#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, IDA or Kuna 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:

npx rea-agents setup

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 records the selected runtime and REA entry script directly. If acquired through a package runner, keep its cache entry available. Run package acquisition from a trusted directory outside the target project. Installation and recovery details are in the setup guide below.

Setup supports Claude Code, Codex, Cursor, Gemini CLI, Grok Build and other agents. See installation and setup for provider configuration and manual MCP registration and Claude Code/Codex plugin installation.

MCP uses compact input schemas by default to reduce context overhead. Set REA_MCP_INPUT_SCHEMA_PROFILE=full in your MCP registration when you need the complete advertised field guidance and nested validation details. Both profiles keep the full tool set and canonical server validation. See "Compact input schema profile" in the MCP contracts guide.

Complete output schemas are advertised by default. If your client caps the complete tools/list frame, set REA_MCP_OUTPUT_SCHEMA_PROFILE=compact to bound each advertised output schema, or off to omit output schemas entirely. Both settings keep canonical server-side validation and complete structured results. See "Output schemas" in the MCP contracts guide.

Ask your agent

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

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:

npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json

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:

npm install --global rea-agents
rea --help

For native analysis, configure a provider first. See the CLI and Evidence guide for native commands, provider selection, snapshots and scripting.

Update REA

REA changes quickly, and new releases include frequent bug fixes. Keep your installation up to date.

For a CLI installed with npm install --global or bun add --global:

rea update

rea --update is an alias for this verified workflow and accepts the same global output flags. Use rea update when combining it with other command controls.

Updater commands retain at most 4 MiB of stdout and stderr combined. Oversized metadata replies are rejected after the command exits; verbose installs continue with bounded diagnostics. Human progress output respects terminal backpressure and waits for submitted writes to finish.

Bun global updates require Bun 1.2.17 or later. With an older Bun release, upgrade Bun manually before running rea update.

To refresh your agent registrations and skill, run the setup command printed by the update.

If you use npx, update your agent setup with:

npx rea-agents@latest setup

Review the setup changes and restart your agent. For one-off CLI commands, use npx rea-agents@latest followed by the command. With Bun, use bunx rea-agents@latest in place of npx rea-agents@latest.

How REA works

Your agent calls REA through MCP to inspect the target and trace relevant code. REA returns findings with their evidence. The agent uses them to ask follow-up questions, explain the behavior, or write and test an implementation. CLI commands use the same workflows.

Open the full-size figure.

What you can analyze

REA requires Node.js 22.x (>=22.23.4), 24.x (>=24.22.1), or 26.12.1+, plus npm. Additional tools and host support depend on the target: