One engine
Native work uses Ghidra, Hopper, or IDA. You bring that engine. REA does not switch to a second engine when the first one is missing.
How it works
One feature. One engine. A location for what was seen.
REA is a local CLI and MCP server. Your coding agent asks a question. REA reads the program and returns items the agent can check. An inference stays labeled as an inference.
- AskName one feature, one channel, or one saved capture. A whole-product rewrite is a later project.
- InspectREA returns a file and line, an address, a byte range, or a field. Each item names where it came from.
- ExplainSeen and not-seen stay in different sentences. A missing note does not prove the behavior is absent.
A located claim
Evidence is a place in the artifact: a path and line, a disassembly address, or a field in a capture. The Windows Calculator percent path is one checked example.
What leaves the machine
The tools run locally. Text you hand to the coding agent still goes to that agent’s model provider.
Next: install and read doctor, or read a dated case. Source ReaReverse.