- Help
- Google+
What if you could ask your AI assistant how any app works and get a real answer, backed by evidence, without ever seeing the source code?
You use an app, tap a feature, and wonder how it was built. Maybe it is a fast search bar, a clever clipboard trick, or a mechanic in an old game. Until recently, finding out meant months of learning disassemblers and reading assembly code. A new open-source project called REA changes that. It has earned more than 430,000 stars on GitHub, and in this guide I will explain what it does, which problems it solves, and how you can start using it today.
In this guide
Reverse engineering is the practice of studying finished software to understand how it works. It is powerful, but it has never been beginner-friendly. If you have tried it, or even thought about trying it, you have probably run into these obstacles.
1. A steep learning curveReading assembly code and pseudocode takes a long time to learn. Many curious developers give up before they get their first useful result.
2. Too many tools and no single workflowAn Electron app needs one approach. An Android APK needs another. A .NET assembly, a native binary, and a website each have their own tools, file formats, and tricks.
3. Slow, manual investigationEven experts can spend hours following one function through strings, calls, and references just to understand a single small feature.
4. AI answers you cannot verifyIf you ask a general chatbot how an app works, it may give a confident answer that is simply invented. Without evidence, you cannot tell what is real.
5. Painful setupConnecting analysis tools to an AI agent usually requires custom scripts and configuration, and it is easy to break.
The Solution: REA (Reverse Engineer Anything)REA is a free, MIT-licensed project that connects your AI agent to professional reverse engineering tools through MCP (Model Context Protocol). MCP is a standard way for AI agents to use external tools. In simple terms, REA acts as a bridge between your agent and the software you want to understand. Here is how it answers each problem above.
The Problem How REA Solves It Steep learning curve You ask in plain English. Your agent runs the tools and explains the results. Too many tools One MCP server covers native binaries, Electron apps, Android, .NET, websites, and dozens of other formats. Slow and manual The agent traces code, references, and calls for you. Answers you cannot verify Every result includes the evidence and limitations behind it. Painful setup One command registers REA with your agent and backs up your existing configuration.You do not need the app’s source code. You point your agent at the app, ask a question, and REA helps it trace the answer.
How REA WorksThe same workflows are available from the terminal, so you can also script them without an agent. Analysis runs locally on your machine. Your agent receives the tool results, and your AI provider’s own data policy applies to that part.
What Can REA Analyze?The range of supported targets is one of REA’s biggest strengths. These are the main groups.
Native programs and binariesREA returns pseudocode, assembly, strings, symbols, calls, and references. Deep native analysis uses an engine you already have, such as Hopper, Ghidra, IDA, or Kuna. It also supports GNU objdump and Rizin for offline inspection.
JavaScript and Electron appsThis is the easiest place to start, because static JavaScript analysis needs no native engine. REA recovers modules, imports, source maps, routes, IPC connections, and native add-on relationships.
atOptions = { 'key' : '291a91492f7bcf13f252654de362127b', 'format' : 'iframe', 'height' : 50, 'width' : 320, 'params' : {} }; Android apps and devicesREA can inspect APK manifests, classes, decompiled methods, signatures, and resources. Through adb, it can also look at packages, processes, and logs on an emulator or a real phone. Flutter apps and JEB projects are supported too.
.NET and managed codeFor .NET assemblies, REA reads metadata, CIL instructions, and native dependencies without running the program.
Websites and network capturesREA can inspect page structure, scripts, and network activity using a Chrome-family browser. It can also read saved HAR and Fiddler SAZ files to examine requests, responses, and exposed payloads.
Specialist formatsThe list continues with Go and Rust binaries, GPU code objects, GGUF and safetensors model files, Unity IL2CPP metadata, Godot PCK archives, PE imports and certificates, ELF notes, Linux kernel modules, WebAssembly, EVM bytecode, SQLite databases, firmware images, packet captures, and PyInstaller executables. Most of these use built-in static inspection, so no extra software is required.
Real Examples: What Has REA Done?The project publishes several case studies on its website.
REA can record a web app session and turn its API calls into tools an AI agent can use. It then exports a runnable environment for reinforcement learning or for testing how well an agent completes tasks. With a saved HAR file, the command looks like this:
rea environment-build ./session.har ./my-env --name my-env --jsonYou then run the result with AgentEnv and Docker, and add your own tasks and reward checks.
How to Get Started With REAYou need Node.js and npm. The project lists supported Node versions as 22.x (22.23.4 or newer), 24.x (24.22.1 or newer), or 26.12.1 and above.
Step 1: Run the setup command npx rea-agents setup Step 2: Choose your agents and approve the changesSetup supports Claude Code, Codex, Cursor, Gemini CLI, Grok Build, and other agents. It shows you the proposed changes first and keeps backups of your existing configuration.
Step 3: Restart your agentThe new MCP server is loaded when the agent starts again.
Step 4: Ask your first question Understand how search works in the Notes app, show me the evidence, and build a similar feature for my project. Prefer the terminal?You can inspect an extracted Electron app or ASAR file directly:
npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --jsonTo keep REA installed, run npm install --global rea-agents. REA changes quickly, so use rea update to stay current. Updating is also the first fix to try if you run into a bug.
REA at a Glance What makes it specialREA combines the reach of dozens of analysis tools with the convenience of an AI agent. It helps you understand software you do not have source code for, and it backs each conclusion with evidence instead of guesses. The range of supported formats, from native binaries to Electron apps to Android devices, is unusually broad for a free tool.
Key featuresDevelopers, security researchers, students, software preservationists, and anyone who wants to understand how an app works.
Using REA ResponsiblyUse REA only on software you own or are authorized to examine.
The project is intended for lawful research, education, interoperability, software preservation, and analysis of software you have permission to study. It does not permit cracked tools, stolen license keys, or bypassing license restrictions. Read the project’s disclaimer before you start.
Also be careful where you download it from. The project warns that a similar repository name or a copied README does not make a download official. Use only these sources:
Only for deep native binary analysis. JavaScript and .NET inspection work without a native engine, and setup can install Hopper with your approval.
Does REA upload my app?No. Analysis runs locally. Your agent sees the results, and its provider has its own data policy.
Which AI agents work with REA?Any agent that supports local MCP servers can use it.
What should I do if I find a bug?Update first, because a recent release may already include the fix. If the problem continues, open an issue on GitHub with your REA version, the target type, the steps to reproduce, and the error output.
Final ThoughtsThe old problem was simple: understanding software without source code took too much skill, too many tools, and too much time. REA’s answer is just as simple. It gives your AI agent the tools to investigate, and it requires the agent to show its evidence. Whether you want to learn how a favorite feature works, study a classic game, or inspect an Electron app, REA is a strong place to start. Just make sure you use it only on software you are allowed to examine.