reverse-engineering-anything/docs/index.md at fca1a0e925b6d9f590971a4cbcf2fa5f4258bf0c

0 Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-03 13:26:10 +00:00

Files

T

Edgar ArakelyanandClaude Fable 5.1 fe55c94e66 feat(environment): serve an environment manifest as a replay environment

Add rea environment-serve <manifest.json> --evidence <capture.json>
[--host] [--port]: it loads an environment-manifest view and the capture
Evidence it was projected from, refuses a manifest whose parent evidence id
does not match the capture, builds one MCP tool per manifest tool and serves
them over streamable HTTP beside an environment card at
/.well-known/agent-env.json and a data plane at /agentenv that refuses every
method. Each tool call replays the retained record whose path and query
values best match the arguments, cites the record ordinal and evidence id,
marks replayed content as untrusted target content, and truncates bodies
over 256 KiB with a flag. Nothing executes the captured application.

Refs morluto/rea#4933

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-10-18 19:43:09 -07:00

6.3 KiB

Raw Blame History

layout, hero, features

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

Task	Guides
Inspect native functions, references, or types	Native binaries, Go metadata, Rust dependencies, offline ELF layout, recorded crashes
Select a native provider or import format	Ghidra semantics, Windows, DOS, raw bytes, MIPS, PSP, NativeAOT, IDA, Kuna, 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, Electron fuses
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
Serve recorded behavior as an agent environment	Agent environments
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.

6.3 KiB Raw Blame History

Start with one command

Choose a guide

6.3 KiB

Raw Blame History