~4m10:46
Nick Saraev

I Tested The Viral Github Repo To Reverse Engineer Anything

Oct 10, 2026

Read: ~4m · You save: 7 min

I Tested The Viral Github Repo To Reverse Engineer Anything

Is REA the end of software as we know it? We test the viral AI tool that claims to reverse engineer anything and explore its true impact on the future of code.

The emergence of "Reverse Engineer Anything" (REA), a meta-command-processor (MCP), is generating significant discussion within the software development community. REA purports to enable users to virtually rebuild any software by decompiling its source application and then instructing an AI agent to recreate or replicate its features. Demonstrations have included reverse engineering an Apple TV remote in approximately 45 minutes, and claims have been made about reproducing the entire suite of Adobe Photoshop applications. This article examines the functionality of REA, critiques common interpretations of its impact, and discusses its broader implications for the future of software.

How Reverse Engineer Anything Works

REA operates by facilitating communication between a human user and an AI agent. The user poses a query, such as "How does this feature work?" or "Can you make me this app?", to their AI agent. The agent then transmits this request to the REA MCP. REA, in turn, interfaces with a suite of established reverse engineering tools, including Ghidra (released in 2019), Hopper (released in 2011), and IDA (released in the 1990s). This integration allows the AI agent to interact seamlessly with these tools. REA also leverages services like Chrome DevTools to further analyze applications.

The output typically includes pseudocode, which provides high-level descriptions of functionality, proof of operation, and identification of unknown elements. The AI agent then iteratively processes this information, refining its understanding and rebuilding the application.

Setting up REA is described as straightforward. Users can instruct their AI agent to download and install REA. The process can be managed within terminal applications like Orca, which allows for the creation of multiple terminal subdivisions to run different AI models concurrently, such as Claude and Codex.

A Practical Demonstration: Rebuilding the Preview App

To illustrate REA's capabilities, a demonstration involved rebuilding the macOS Preview application. Preview, a standard photo viewer, offers functionalities such as information display, zoom in/out, and sharing. The objective was to replicate these features, potentially with added capabilities like drawing boxes or handwriting annotations.

The AI agent was instructed to "Use REA to rebuild the preview app on my Mac." Concurrently, a separate attempt was made to rebuild the same app without using REA, instructing an AI agent to "reproduce the Mac preview app, the photo viewer one, and then serve me the result."

The REA process involved decompilation using Ghidra, with the AI agent progressing through the rebuilding stages. The non-REA attempt also proceeded independently.

The first completed result was from Opus, without relying on REA. The resulting Preview app exhibited some lag, potentially due to background processes. The REA-developed version took an additional 3-4 minutes to complete. Upon testing, the REA version opened and closed various tabs and displayed flashing elements. It eventually launched, presenting three files.

A comparison between the REA-developed app and the original macOS Preview app revealed significant similarities. Both applications displayed titles, information panels, zoom functionality, sharing options, and drawing capabilities. The drawing function in the REA version appeared to operate faster than in the original. Both versions also supported rotation and annotation saving.

Contextualizing REA: Not a New Breakthrough

A key point of contention is the perception of REA as a novel development. The underlying tools it utilizes are not new. Ghidra was released by the National Security Agency in 2019. Hopper Disassembler and IDA have been available for considerably longer periods, with IDA dating back to the 1990s. REA's primary function is to provide AI agents with a simplified interface to access these existing tools, thereby enabling reverse engineering.

The widespread enthusiasm for REA has been fueled by its viral spread on platforms like GitHub, evidenced by a rapid increase in its star count. However, critics argue that this focus on metrics like GitHub stars suggests a lack of compelling, substantive demonstrations of REA's unique value. The argument is that if the technology itself were sufficiently groundbreaking, the focus would be on its capabilities rather than its popularity.

While REA facilitates reverse engineering, the ability to reverse engineer software is not new. AI agents can be instructed to analyze specific features of an application and attempt to replicate them, even without specialized tools like REA. This can involve capturing animations or other visual elements through screenshotting and then using the AI's reasoning process to recreate them. While the accuracy of such AI-generated replications may vary, it is hypothesized that the resulting functions could be more efficient than human-developed counterparts. This was observed in the repurposing of the Photoshop suite, where vanilla AI models like Claude were able to achieve close approximations.

Broader Implications for Software Development

The trend towards AI-driven software reconstruction suggests a shift in the software landscape. It is posited that a significant portion of software will become open-source as development moves to a higher abstraction layer, focusing on general intelligence (e.g., Claude, Codex) capable of rebuilding software on demand. This could lead to the commoditization of front-end and back-end development.

From a business perspective, this trend presents both opportunities and challenges. While it lowers the barrier for recombining existing ideas into novel applications, it also potentially closes doors for certain types of software businesses. Wrapper applications that add functionality or visual enhancements to AI models may become obsolete as the underlying models are updated to incorporate these features directly. The value ladder for software development is perceived to be shifting.

While short-term benefits might be derived from reverse engineering existing applications, intellectual property restrictions remain a significant hurdle. The primary impact of this trend is seen as a reduction in the effort required to iterate on and combine existing concepts.

Furthermore, the necessity of specialized reverse engineering tools like Ghidra or IDA may diminish. Vanilla AI agents, through their inherent reasoning capabilities, are increasingly able to produce plausible visual and back-end analogs of applications. While these tools may offer speed advantages, it is anticipated that general AI agents will capture much of this functionality. The "reverse engineer era" is presented as an imminent development.

Introduction to Reverse Engineer Anything (REA)

Introduction to REA, its viral nature, and initial reactions from the tech community, including quotes from Matthew Berman, Amjad (Replit CEO), and Jaden Williams.

  • REA is a tool that uses AI agents to virtually rebuild software by decompiling source apps.
  • Demos include reverse engineering an Apple TV remote in 45 minutes.
  • Matthew Berman stated, "reverse engineer anything software is done."
  • Amjad (Replit CEO) believes most software will soon be open source.
  • Jaden Williams expressed concern: "God help us all."

How REA Works: The Technical Process

Explanation of how REA functions, detailing the interaction between the human user, AI agent, REA MCP, and various decompilation tools like Ghidra, Hopper, and IDA.

  • The process involves a human asking an AI agent to rebuild an app.
  • The AI agent sends requests to the REA MCP.
  • REA utilizes tools like Ghidra (released 2019), Hopper (released 2011), and IDA (released in the 90s).
  • The REA library enables seamless communication between the AI agent and these tools.
  • Chrome DevTools can also be used to inspect apps.
  • The output includes pseudocode, proof of functionality, and identified unknowns.
  • The AI agent iterates until the app is effectively rebuilt.

Testing REA: Rebuilding the Mac Preview App

Demonstration of setting up and using REA, including the use of Orca terminal manager and Claude AI, to rebuild the Mac Preview app.

  • REA can be easily set up by instructing the AI agent to download it.
  • The creator uses Orca terminal manager for running multiple AI agents (Claude, Codex).
  • The demonstration involves using Claude to rebuild the Mac Preview app.
  • Preview app functionality includes viewing images, zooming, sharing, and drawing.
  • The creator also initiates a parallel attempt to rebuild the Preview app using Claude without REA for comparison.

Comparing REA vs. Vanilla AI: Preview App Results

Comparison of the REA-generated Preview app with the AI-generated version without REA, highlighting similarities, differences, and performance.

  • The first completed app was built by Opus without libraries.
  • The REA version took longer to complete.
  • The REA-generated app is virtually identical to the original Preview app.
  • Features replicated include title, information display, zoom, share, and drawing.
  • The REA version's drawing functionality was faster than the comparison app.
  • The REA version also included rotation and annotation saving.

The True Novelty (or Lack Thereof) of REA

Critique of the novelty of REA, emphasizing that the underlying tools (Ghidra, Hopper, IDA) are not new, and REA's main contribution is an accessible interface for AI.

  • The tools used by REA (Ghidra, Hopper, IDA) have existed for years.
  • Ghidra was released by the National Security Agency.
  • Hopper Disassembler and IDA are also older tools.
  • REA's innovation lies in providing a simple interface for AI agents to access these tools.
  • The internet may be overhyping REA, focusing on GitHub stars rather than inherent value.
  • Many demos are perceived as hype rather than genuine breakthroughs.

The Future of Software Development with AI

Discussion on the broader implications of AI in software development, suggesting a future where most software becomes open-source and front/back ends are commoditized.

  • Most software may become open-source due to AI's ability to rebuild it.
  • Abstraction layers have shifted from specific applications to general AI intelligence (e.g., Claude, Codex).
  • Front-end and back-end development are becoming highly commoditized.
  • This trend opens new opportunities but closes doors for traditional software businesses.
  • Wrapper apps and unique functionalities are being absorbed by AI models.
  • The barrier to recombining existing ideas and creating cool demos has lowered.
  • AI can potentially replicate app functions more efficiently than humans.

Is REA Essential? AI's Independent Capabilities

Exploration of whether REA is necessary for reverse engineering, concluding that AI agents can perform similar tasks independently, and discussing the evolving landscape of AI capabilities.

  • REA is not strictly necessary for reverse engineering; AI agents can do it independently.
  • AI agents can analyze features from screenshots and replicate them.
  • AI-generated code might be more efficient than human-written code.
  • Claude's post-training will likely incorporate reverse engineering capabilities.
  • Vanilla AI agents can rebuild apps visually in a fraction of the time REA takes.
  • The 'reverse engineer era' is approaching, driven by general AI capabilities.