Harness For Rea

How a task runs ·
  Isolation ·
  MCP integrations ·
  Install ·
  Using it ·
  Development

Harness for REA

A desktop app and a terminal UI for deep analysis of software you own or are authorized to study:
understanding a legacy system, debugging, reverse engineering a binary or an app, and porting or
reimplementing what it does.

You describe what you want in a chat. Two agents do the work:

REA is a reverse engineering MCP server for native binaries,
Android, .NET, Electron and JavaScript targets. The orchestrator does not analyse the target itself.

The split keeps the expensive, careful work with the specialist and the cheap planning and coding
with the orchestrator, and keeps the target away from your machine: the specialist only ever sees
copies of the files it was handed.

How a task runs

1. You start a task in a project with a request. The orchestrator breaks it into steps.
2. For each analysis, the orchestrator writes a _context package_: a technical brief (what the
   artifact is, what is already known), the objective, the files, the questions and the report
   format. The specialist sees that package and nothing else — not your request, not the chat.
3. The specialist runs in a fresh container (or a sandbox the orchestrator prepared with tools
   and files), with the files copied into /work. It answers with a report whose claims cite
   evidence: a line range, an address in a binary, or an REA evidence id.
4. Every report ends with a contract, a JSON block the app validates: the functions mapped with
   their inputs, outputs and side effects; the constants found, each with a source or marked
   estimated; the questions left open; and _test vectors_ — inputs given to the target and the
   output it produced, observed by running it. A report whose contract…