See how an app's feature works without its source: REA hands binary and JavaScript inspection to AI agents
Synopsis
REA connects AI agents to tools for inspecting native binaries, JavaScript and Electron apps, .NET assemblies, and websites, so an agent can examine how a feature works without the app's source code and report the evidence and limitations behind each conclusion. Analysis runs locally, and static JavaScript analysis needs no native analysis engine, while native analysis can reuse an existing Hopper, Ghidra, or IDA installation. Setup runs through npx rea-agents setup, which registers an MCP server and matching workflow instructions and backs up existing configuration.
Interpretation
An AI agent can use REA to investigate a feature in an app even without that app's source code, explain how the feature works, show the evidence, and build a version for the user's own project. Understanding a shipped app's feature previously called for its source or manual reverse engineering; REA exposes this inspection capability as tools an agent can call. The tools cover native binaries, JavaScript and Electron apps, .NET assemblies, and websites, and the same tools are usable directly from a terminal.
Analysis runs locally, and each result carries the evidence and limitations behind it, which the agent uses to ask follow-up questions, explain behavior, or write and test an implementation. The agent calls REA through MCP to inspect the target and trace relevant code, and REA returns findings with their evidence rather than a bare conclusion. Static JavaScript and .NET inspection read the supplied files without running the application, while runtime capture runs or interacts with the target using the user's permissions, with each runtime guide describing its effects.
Perspective
Intended for developers who want an agent to inspect native binaries, JavaScript and Electron apps, .NET assemblies, or websites and rebuild a feature in their own project. Static JavaScript and .NET inspection read the supplied files without running the application; runtime capture runs or interacts with the target using the user's permissions, and each runtime guide describes its effects. Native analysis can reuse an existing Hopper, Ghidra, or IDA installation, and static JavaScript analysis needs no native analysis engine.
The material gives no accuracy, coverage, or performance figures and no detailed success-case specifics per target type. REA changes quickly and new releases include frequent bug fixes, so the material advises keeping the installation up to date; Bun global updates require Bun 1.2.17 or later, and older Bun releases must be upgraded manually first. The runtime requires Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+, plus npm.