REA connects coding agents to local inspection tools and returns findings with evidence and limitations. Our November 14 source run installed and built successfully, then reached the test time limit. A separate November 17 CLI smoke run reached version and help before its usage recipe failed. Use REA for one authorized feature you can compare with known behavior. Skip it when your requirement is complete application recovery from a single prompt.
Attention does not establish successful investigations
GitHub stars count attention; a checked feature reconstruction answers whether an investigation worked. The andrew.ooo review records 58,461 stars in its October 10, 2026 snapshot. That dated figure belongs to the October review, rather than a current adoption count. It gives context for interest in REA, but a developer choosing an inspection workflow needs evidence about targets, returned findings and useful outcomes.
HoverSpeech provides a more concrete example because its author could compare REA's findings with his own source code. Moe Lueker reports that the identified speech stack matched his implementation, then describes building a web read-aloud feature. His HoverSpeech investigation supplies a target and an author-checked result. The repository's separately dated activity metadata describes repository activity, which answers a different question from whether a particular investigation succeeded.
What people use rea for
REA supports feature tracing, static application inspection and questions about existing native-analysis projects. Its README describes JavaScript/Electron modules and imports, native pseudocode and assembly, and website inspection. The agent uses returned findings to ask follow-up questions, explain behavior or write an implementation. Choosing one behavior gives that process a concrete destination: identify a speech engine, trace a clipboard payload or explain a calculation.
| Who used it | Target and outcome | What the result supports |
|---|---|---|
| Moe Lueker, HoverSpeech's author | Identified the speech stack, then used Claude to build and publish a web read-aloud feature. Author account | A feature reconstruction checked by the original author and connected to his existing voice server. |
| The andrew.ooo review lab | Inspected Express 4.21.2 without a native engine or agent login. Static-analysis review | A static JavaScript workflow. |
| REA AI troubleshooting authors | Corrected command lookup and missing-target errors, then analyzed a small JavaScript fixture. Troubleshooting account | Controlled corrections followed by successful fixture analysis. |
| An investigator described by MindStudio | Traced Notion's rich clipboard bridge. Secondary case account | An attributed explanation of an identifier connecting clipboard HTML to saved block data. |
Lueker reports identifying HoverSpeech's Kokoro-82M model, FluidAudio library and Heart voice after two Ghidra timeouts of 330 seconds each on a 16 MB helper. The agent fell back to text labels, file inventories and embedded type names. Lueker says the findings matched how he built the application. Claude subsequently built a web read-aloud feature and connected it to his existing Kokoro voice server.
MindStudio describes a developer studying QuickBooks Desktop for Mac before building Ledger Reborn with Python and SQLite. Its Notion account describes an HTML identifier reconnecting pasted content with locally stored structured blocks. The video-2 presenter also claims an Instagram-like application with clickable feed, likes and reels, followed by an Amazon-style store. These remain MindStudio's reported cases and the video presenter's demonstration claims, with the outcomes attributed to their respective accounts.
What happened when we ran it
Our November 17 CLI smoke run reached version and help output, then failed at usage selection. It used commit 05be423acbdf in a fresh unprivileged container configured with 2 CPUs, 4 GB RAM, image label lab-node:22, no published ports and no secrets. The run configuration names the quickstart-cli recipe. The following rows preserve each recorded step, including its failure and teardown outcome.
| CLI smoke-run step | Recorded outcome |
|---|---|
| Clone | The quickstart recipe cloned the repository in 4 seconds. |
| Global package install | The hands-on package record identifies rea-agents 6.7.0, 250.0 MB installed and 26.3 s. |
| Version | rea-agents --version exited 0 and printed 6.7.0 in 1.4 seconds. |
| Help | rea-agents --help exited 0 and listed CLI commands in 1.3 seconds. |
| Usage | FAILED: no runnable rea-agents command in the README's usage/examples sections. |
| Teardown | OK. |
The usage failure describes the recipe's command-selection step. The current README contains an explicit JavaScript-analysis command with a target-path placeholder, reproduced in the FAQ below. Both observations matter: the recorded recipe stopped after help, and the documentation provides a terminal example. Treating the recipe failure as an analysis failure would change what happened. The November 14 source harness measured a different checkout, commit 5815178.
| Source-run measurement | Result |
|---|---|
| npm install | Succeeded in 44 seconds, 743 dependencies recorded, 885 MB on disk |
| Build | Succeeded in 45 seconds |
| Tests | Timed out at 900 seconds |
| npm audit | 7 known vulnerabilities: 7 moderate, 0 high, 0 critical, 0 low |
| Repository scan | 12,953 files, approximately 2,418,704 source lines, 129.1 MB checked out |
| Automation signals | 35 CI workflow files, a tests directory, no Dockerfile detected |
In our November 14 source run, installation succeeded in 44 seconds, the build succeeded in 45 seconds, and tests timed out at 900 seconds. The configuration specified 3 CPUs, 8 GB RAM and image label lab-node:22. The passing tail named Playwright scenarios (52 tests), Apple Mach-O fixups (90), Deno artifacts (96), Apktool (72), browser scenarios (44) and Python bytecode parsing (63). These are displayed file counts within the timed-out command.
The tail also named recovery of later string pages and exhausted XML admission, alias-count retention after aggregate budgets of 2000 and 2001 entries, and disclosure of qualified and unfamiliar string tables with exact locale selection. A browser case preserved an unrelated launch failure, and a Python case retained one descendant list shared by many wrappers. Those passing cases remain part of the record; the enclosing test command still ended at its 900-second timeout.
Where people get stuck: command lookup, providers and client schemas
A missing executable, invalid target and rejected client schema require different corrections. REA AI's controlled troubleshooting account deliberately restricted command lookup, producing exit 127, then called the installed executable by absolute path and obtained exit 0. Its missing-target exercise succeeded after the authors supplied the existing Pocket Notes directory. Neither correction required changing the analysis engine, because each failure occurred at an earlier layer.
| Symptom and source | Useful correction or recorded outcome | Status in the supplied record |
|---|---|---|
| Shell cannot find rea, REA AI guide | Locate the executable and correct PATH, or call its absolute path. | Controlled correction succeeded. |
| Target directory does not exist, REA AI guide | Correct the path and repeat the operation. | The JavaScript fixture then succeeded. |
| Linux process prerequisite, README | Supply a procps-compatible system ps on REA's PATH. | Documented requirement. |
| Windows native-authority check, issue #1701 | Inspect the native-authority diagnostic even when Ghidra is detected. | Open, with mixed host outcomes reported. |
| Screenshot arguments rejected, issue #4973 | A Windows/Claude Desktop control accepted PNG objects and a numeric threshold on 6.7.0. | Original symptoms no longer reproduced in that control; issue open. |
| Gemini CLI HTTP 400, issue #4620 | A user reports a working schema wrapper; later investigation identifies an empty-string const. | Closed thread. |
Issue #1701 reports Windows native-authority refusal after a Win32 access-denied error despite Ghidra detection. In issue #4973, VarunRaj004 reports successful screenshot comparison on REA 6.7.0 through Claude Desktop for Windows. Two 1x1 PNG objects and channel_threshold 0 returned 1/1 changed pixels, maximum channel delta 255 and mean 127.5. These reports concern different layers: host authority and client argument acceptance.
Issue #4620 later identifies an empty-string const in trace_application_feature after a Gemini 400 survived an earlier boolean repair. That sequence changes the diagnosis from the thread's earlier confident explanation. When a client rejects the advertised catalog, inspect the schema and returned error. When native authority refuses an operation, inspect the host diagnostic. Reinstalling unrelated components does not address either reported cause.
Large targets make reuse and retained evidence matter
Selected expanded Ghidra projects can be reused on POSIX through a private copy and an executable-hash check, according to Morluto's controls. Issue #3751 describes server-start settings selecting the project and optional program. REA opens the copy read-only without fresh auto-analysis. Separate selected programs returned distinct annotations, making the exact program name and project state useful provenance alongside the original executable's identity.
A controlled project edit changed saved instructions and pseudocode while leaving the imported executable unchanged. REA returned that saved project state; a fresh import returned the original. Another control rejected an old snapshot after a project change and succeeded with fresh analysis. The practical distinction is between identifying the imported executable and identifying the analysis database supplying the answer. Recording both explains why two sessions can return different analysis for the same original binary.
Issue #8425 reports a completed Kuna observation disappearing from the caller's error when Evidence retention was refused. Its reproduction injected a zero-byte retention allowance. The provider completed, the caller received a resource-constraint error, and the investigation contained no Evidence records. Completion, delivery and retention are separate outcomes in this report. A reference becomes useful to a later question only when its supporting observation is actually retained.
Issue #2016 reports task-dependent efficiency results: selected Flutter and SQLite tasks reduced total input, while the compact HTTP capture view increased it. The README's compact discovery settings concern advertised tool schemas; complete analysis results are another surface. Choose a summary or projection that answers the question, then inspect retained detail when needed. A smaller representation at one stage does not by itself describe the cost of the whole investigation.
Cancellation and cleanup are separate outcomes
A client deadline ends its wait; resource cleanup determines whether subsequent work can proceed. The connection and recovery guide directs readers to use the observed failure and the connected server's actual schemas. Recovery therefore starts with the returned diagnostic and relevant session state. When an error names a retained cleanup owner, that owner identifies the recovery path for the resource the next operation needs.
Issue #4227 tracks readiness, cancellation, ownership and recovery failures, including abandoned work or listeners occupying a serial engine thread. Issue #1065 tracks responsiveness under bounded resources and long analysis phases. For an investigation that includes cancellation, the useful outcome is whether the next intended operation can acquire its resource. Increasing a wait duration and releasing that resource answer different operational questions.
Local analysis still sends results to the agent
REA analyzes targets locally, and the agent receives tool results under its model provider's data policy. The README distinguishes static JavaScript and .NET inspection, which read files, from runtime capture, which runs or interacts with the target using the user's permissions. This distinction tells the reader what the operation does on the host and which findings can enter an agent conversation.
Account discussions require similarly precise attribution. The synthesis identifies kincaidDev's historical temporary suspension as reverse-engineering experience explicitly separated from REA-specific use. In the directly supplied r/vibecoding extract, Ill_Explanation5427 says they nearly lost two accounts. Those are different reported events. A participant's question about refusals and suspensions is also a question, rather than an additional confirmed enforcement event. The table keeps those categories visible.
| Account-risk evidence | What the record contains | How to read it |
|---|---|---|
| REA-specific warning | Ill_Explanation5427 says they nearly lost two accounts. Warning thread | An individual user's warning. |
| Historical suspension | The synthesis describes kincaidDev's temporary reverse-engineering suspension as not specifically REA. Suspension discussion | Historical experience with its stated scope. |
| Ordinary refusals | A participant asks about reports of refusals and suspensions. Account-risk question | A question distinguishing two outcomes. |
| Alternative-model advice | Commenters recommend GPT, Kimi, DeepSeek, GLM and local models. Community recommendations | Community preferences and advice. |
REA vs Ghidra, Craft Anything and ordinary agent tools
Choose REA for repeated agent questions with structured findings, Ghidra for direct interactive binary work, and Craft Anything for its documented study/build/check workflow. These choices concern how the investigator works and what they want to produce. Ghidra can also operate beneath REA as a native provider, so choosing an agent interface can retain the same underlying analysis engine rather than replace it.
| Choice | Pick it for | Trade-off relative to REA |
|---|---|---|
| Interactive Ghidra | Manual navigation, renaming and patch experiments in the project window. | The investigator manages the interactive workflow; REA can use Ghidra underneath. Workflow comparison |
| Craft Anything | An explicit study/build/check loop producing a new project. | Its README describes an early-alpha application; REA supplies findings for the agent's implementation work. Craft Anything README |
| An agent using ordinary tools | A small question answered by file inspection, strings or existing scripts. | The investigator arranges the evidence; Lueker says ordinary agents suffice for simple jobs. Author experience |
Ghidra supports disassembly, decompilation, graphing and scripting in interactive and automated modes. Its primary README describes compiled-code analysis and custom scripts. Craft Anything's README describes studying a target, having a coding agent build a new project, checking it against the original and refining it. That documented loop gives a reader a concrete alternative when the desired deliverable includes a replacement project and comparison steps.
What the other reviews get wrong
The current README requires later Node patch versions than the older setup guidance: 22.23.4 for 22.x, 24.22.1 for 24.x, or 26.12.1+. FollowAgents' and Lueker's earlier requirements belong to their dated guidance. The October review's 6.3.0 release statement is also historical. Supplied release metadata identifies rea-agents-6.9.0 on November 12, 2026, while our separate CLI smoke record identifies the 6.7.0 package it actually reported.
REA's MIT licence describes the software licence, while an investigation can also use paid model access, commercial native tools and hosting. Lueker estimates $28.60 at API prices for his complete inspection, rebuild and deployment session, reporting about 56 million tokens and roughly 2% of his weekly Claude allowance. His cost account includes work beyond inspection. It is a dated session account rather than a universal REA price.
The follow-up issues also correct several blanket claims: selected-project reuse exists on POSIX; a completed observation can be lost during retention refusal; and Gemini's schema investigation progressed beyond an earlier boolean explanation. HoverSpeech's useful feature reconstruction followed two native-analysis timeouts. Reading those outcomes together gives a more practical account than promises that every call is retained, every import must be repeated or any application can reliably be reconstructed in minutes.
REA means Reverse Engineer Anything here
This review concerns morluto/rea, the software-inspection MCP server and CLI. The supplied autocomplete mixes software questions with unrelated football, phone and television searches. Those completions describe an ambiguous query string rather than demand for this repository. Naming the full software and repository keeps the review attached to the README, issue reports and dated measurements used here, and avoids borrowing apparent interest from unrelated entities.
FAQ
Start with npx rea-agents setup, select your agent, review the proposed changes and restart it. The README says setup registers the MCP server and matching workflow instructions, with backups of existing configuration. Choose the first analysis task by target type: static JavaScript inspection needs no native engine, while native work requires a suitable provider. A narrow behavior gives the first returned findings something concrete to explain.
How do I install and use REA with my coding agent?
Run npx rea-agents setup, choose the agent, review the proposed changes and restart it afterward. For terminal JavaScript inspection, the README supplies npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json. Replace the placeholder with an existing target directory or ASAR path appropriate to that workflow. These README commands document setup and inspection separately, so select the command that matches the intended task.
What is REA, and is it useful or mostly hype?
REA connects an agent to local software-inspection tools through MCP and exposes workflows through a CLI. Lueker's account offers a concrete outcome: speech-stack findings checked by the target's author, followed by a web read-aloud feature connected to his existing server. That author-checked case gives a developer a specific feature-investigation example to compare with their own task and available reference behavior.
Which prompts help REA investigate one feature at a time?
Lueker asked which speech engine and voice HoverSpeech used and what happened between incoming text and playback. He requested separate categories for proof, inference and unread code. His feature-scoped investigation suggests a practical prompt structure: name one behavior, request supporting locations and distinguish observations from interpretation. Compare the resulting explanation or implementation with the behavior that motivated the question.
Can using REA with Claude Code lead to an account suspension, even for authorized work?
The discussion includes an account-risk question, a historical suspension report and a separate warning about nearly losing accounts. The Claude Code thread asks explicitly about authorized reverse engineering; the r/vibecoding warning describes an individual's experience. The historical report is identified as not specifically REA. Keep those reported events distinct when considering a provider account alongside permission to examine a target.
What we have not tested yet
Our runs cover source installation and compilation, a timed-out test command, and CLI version/help output. They contain no completed feature investigation, model-generated rebuild, native-provider investigation, Windows workflow or representative multi-query workload from our team. The smoke record contains no known-answer question set, screenshots or observed task-memory measurement. Its 4 GB and the source run's 8 GB are configured memory. Image labels identify neither actual runtime nor operating-system versions; the timeout supplies no final test total or supported cause.
The documented terminal analysis command was not executed in these runs. Complete backend equivalence for the video demonstrations, an independently reproduced QuickBooks replacement, a universal speed advantage and a REA-specific suspension rate remain unresolved. The video record omits its channel name, and pronunciation is undocumented. Community model recommendations supply no compatibility measurement, account-safety guarantee or repeatable appeal procedure. Search volumes, ranks and demand are unknown in the supplied discovery record.
The selected Ghidra-project implementation covers expanded projects on POSIX; Windows reuse and direct .gzf selection fall outside that scope. The screenshot control used tiny PNG fixtures rather than complete real browser captures. Gemini's closed thread supplies no confirmation of a final published fix. Capacity experiments inject allowances rather than measure production-default exhaustion frequency. Our evidence also contains no target-execution audit or demonstration that the seven moderate advisories are reachable in a particular workflow.
For an adoption decision, the next useful experiment is one authorized target with known behavior. Trace a feature, retain its supporting Evidence and compare the reconstruction with that behavior. Include cancellation and reopening when the intended workflow depends on them. A source build, a CLI launch and an author-checked feature reconstruction answer different questions; choose the task that supplies the missing answer for your own investigation.


