morluto/rea puts Ghidra, IDA and JADX behind any coding agent through one MCP server

In REA, the analysis is done by professional tools. REA connects an existing coding agent to them, so the agent calls Ghidra, Hopper or IDA and gets back pseudocode, assembly and function-level analysis ^[3]. Setup is one command, npx rea-agents setup ^[2]. Practitioners on r/ReverseEngineering were already wiring agents into Ghidra, the same toolchain REA builds on ^[21]. The addition is the one-command wrapper.

Obscurity worked because reading decompiler output is slow. An agent shortens the slow parts, and the post's best-documented case shows how much slow work remains. Volunteers completed a full decompilation of the N64 game Snowboard Kids in 84 days ^[10], or 12 weeks ^[14]. The volunteers wrote the code. The agents accelerated renaming symbols, identifying function boundaries and suggesting C equivalents for assembly blocks ^[11].

One developer writing on Substack said one prompt to Claude, on its first try, yielded a function that matched at 96% ^[17]. For that figure to transfer to your binary, the function would have to resemble yours in size, compiler and symbol coverage.

The post's adoption figures contradict each other. Its own GitHub trending data puts REA at 66,886 stars on October 10, after a gain of 25,784 that day ^[15], and at 95,662 on October 11 after 25,585 more ^[16]. Adding 25,585 to 66,886 gives 92,471, which falls 3,191 short of the reported total ^[13]. Snapshot timing may explain it. A star also records only interest.

Nikita Bier, a former Head of Product at X, supplies another of the post's signals. He posted a prediction that software "will be personalized exactly to your preferences" ^[20]. It drew over a million views ^[20].

Of the post's signals, the Thales launch is the one with a commercial stake. The post describes it only as a new product built to defend against AI-assisted reverse engineering ^[18]. In our view obscurity was always a delay, and agent tooling now makes it shorter. A stripped, optimized release build is the case to benchmark. Nothing in the post measures one.