rea/docs/index.md

layout	hero	features
home	name text tagline actions REA Reverse Engineer Anything Understand binaries, applications, and runtime behavior with one CLI and MCP server. theme text link brand Get started /installation theme text link alt View on GitHub https://github.com/morluto/rea	title details link Investigate with your agent Connect REA to your coding agent, describe the app or feature you want to understand, and follow the evidence. /mcp-prompts title details link Inspect across formats Explore native binaries, JavaScript and Electron apps, .NET assemblies, Android packages, firmware, and websites. /installation title details link Keep the evidence Analysis runs locally and returns observations, limitations, and unknowns through the CLI and MCP. /mcp-contracts

Start with one command

npx rea-agents setup

Choose your agent, review the planned changes, and approve setup. Native binary analysis can use an existing Hopper, Ghidra, or IDA installation; static JavaScript analysis needs no native analysis engine.

For a first result from an extracted JavaScript application or ASAR:

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

See installation and setup for requirements and configuration.

For runtime instrumentation, see the Frida guide.

Choose a guide

The documentation directory lists every guide by domain and explains where authored references, specifications and generated records belong.

Task	Guides
Inspect native functions, references, or types	Native binaries, Go metadata, offline ELF layout, recorded crashes
Select a native provider or import format	Ghidra semantics, Windows, DOS, raw bytes, MIPS, PSP, NativeAOT, IDA, JEB
Analyze JavaScript or Electron artifacts	Static analysis, tracing and comparisons, application graph, source recovery
Compare static JavaScript with runtime observations	Runtime attribution, reconciliation, Electron observation
Inspect assemblies, packages, or firmware	.NET, Android, Apktool resources, ADB acquisition, Apple, Harmony, firmware, WASM, EVM
Observe or compare a browser scenario	CDP observation, scenarios, runtime evidence, historical captures
Trace captured website source	Source locations, module traces, script export
Capture and compare a command	Process capture
Use CLI/MCP and retain evidence	CLI, MCP contracts, agent prompts, obligation ledgers

For development, use testing, client verification, tool design, and releasing. Reconstruction readiness describes a development conformance verifier. The 6.2 migration records that release's compatibility changes; the roadmap tracks future work.