Look inside.
Figure it out.
Build it better.
Reverse Engineering Anything, explained.
A practical guide to REA, the open-source toolkit that connects your AI agent to the software beneath the surface.
function explain(behavior) {
return evidence + context;
}A feature is a question.
REA helps you
find the evidence.
Start with one thing you want to understand. Let your agent inspect the code, connect the clues, and explain what it finds.
What this guide covers ↗Inspect the target
Read application artifacts, modules, symbols, or native instructions with the appropriate tools.
Trace one behavior
Connect entry points, calls, and data. Ask for source locations, limits, and what is still unknown.
Build with understanding
Turn the findings into a specification for your own implementation. Test the behavior you care about.
One setup.
A better starting point.
Choose your agent to get the setup command.
Review the proposed changes, then restart your agent.
npx rea-agents@latest setupNode.js + npm required. Native analysis needs a compatible provider.
Your next right step.
Installation & first run
Set up Reverse Engineer Anything, choose an analysis provider, and verify the connection before your first investigation.
REA with Claude Code
Connect REA to Claude Code, verify its MCP registration, and use a focused prompt that asks for evidence.
REA with Codex & Cursor
Set up the REA MCP server for Codex or Cursor and diagnose the selected client without changing unrelated integrations.
CLI command reference
Copy REA commands for setup, diagnostics, static application analysis, native providers, and managed assembly inspection.
Troubleshooting REA
Diagnose missing MCP tools, provider problems, runtime requirements, and incomplete analysis with focused REA checks.
See what an investigation looks like.
Three official walkthroughs. Three different ways to look beneath the interface.
position → panDX-Ball
From screen position to stereo sound.
Notion
Follow a clipboard call across processes.
TH04
Recover the geometry behind a bullet ring.
Published by the REA project. These are linked learning resources, not results reproduced by this site.
What are you investigating?
Match the artifact to the analysis path before you start.
Inspect a directory or ASAR with Node.js and npm. No native decompiler is needed.
See the command reference ↗Before you dig in.
What is Reverse Engineering Anything?+
Reverse Engineering Anything commonly refers to REA (Reverse Engineer Anything), an open-source toolkit that gives AI agents access to software inspection tools through MCP and a CLI. This independent site helps you get started and find the official resources.
Is this the official REA website?+
This is an independent guide. The official project is morluto/rea on GitHub, and its website is rea.tools. Downloads and release instructions link directly to those sources.
Can it recover the original source code?+
Decompiled code is a reconstruction. Compiler transformations, missing symbols, and unsupported features can limit what you recover. Ask for the evidence and verify behavior in your own tests.
Do I need a paid decompiler?+
The requirements depend on the target. Static JavaScript and managed-code workflows do not require a native analysis engine. Native analysis can use compatible providers such as Ghidra, Hopper, or IDA; their own setup and license terms apply.
Does the analysis happen on this website?+
No. This site provides guides and command templates. REA runs on your computer. The AI agent you connect has its own provider and data policies.