Reverse Engineer Anything: How To Point Your AI Agent At Software You Didn’t Write, And Where To Start
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: Reverse Engineer Anything: How To Point Your AI Agent At Software You Didn’t Write, And Where To Start on ThorstenMeyerAI.com

Before you orderOffer from Amazon

Get the latest gadgets delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

Reverse Engineer Anything (REA), an open-source toolkit for AI coding agents, provides tools to inspect existing programs and trace specific behaviors. A case study described by its maintainer reports that a locally built accounting app matched QuickBooks Desktop sample-company statements to the cent, though the source does not provide independent verification.

Reverse Engineer Anything (REA), an open-source toolkit for AI coding agents, is being presented as a way to inspect existing software and turn observed behavior into implementation specifications. In a report published October 19, Thorsten Meyer highlighted a case study in which a developer used REA and an AI agent to build a local accounting app whose statements reportedly matched QuickBooks Desktop’s official sample company account by account, to the cent—a result that could matter to developers recreating business workflows, but is not independently verified in the supplied material.

REA connects agents such as Claude Code, Codex, Cursor and Gemini CLI to software-analysis tools. The project combines a local Model Context Protocol (MCP) server, a command-line utility and an agent skill that guides investigations. According to Meyer, its analysis options cover native applications, JavaScript and Electron programs, .NET and Android apps, firmware, network captures, WebAssembly and SQLite databases. For websites, it can observe activity through a Chrome-family browser controlled by the user.

The report says the project is MIT-licensed, hosted as morluto/rea on GitHub, and at version 6.7.0 on October 19, following a release the previous day. Meyer reported about 325,000 stars and 82,000 forks at that time. The source also describes a guided setup command and says Node.js 22.19 or later is required; native-code analysis may require Ghidra, Hopper or IDA. These figures and technical details are reported by the source and are time-specific.

The featured example, Ledger Reborn, involved examining QuickBooks Desktop for Mac 2024 using REA 6.4.0 and Ghidra, according to the report. The investigation focused on inventory calculations, budget signs tied to account types, reconciliation balances and cash-basis report logic. The resulting app’s statements for Intuit’s sample company reportedly matched the original figures. Meyer frames the work as documenting rules and data behavior rather than copying screens. The supplied account does not include independent test results or a full technical audit of the implementation.

At a glance
reportWhen: Reported October 19, 2026; REA version…
The developmentA project published by Thorsten Meyer on October 19 describes REA’s tools and investigations, including a reported QuickBooks Desktop replication case study.
Thorsten Meyer AI
Open source · MIT

Infographic 01 · Reverse Engineer Anything

Five places to point REA first, and how to tell when the answer is wrong.

REA gives coding agents such as Claude Code and Codex tools to inspect programs, apps and browser sessions. Each investigation needs a finishable question and a check.

~325kGitHub stars on 19 Oct 2026 (82k forks)
6.7.0Current version, released 18 Oct 2026
1 lineGuided setup: npx rea-agents@latest setup
LocalRuns on your machine. Not a sandbox: treat unknown programs as untrusted.

The five investigations

What to ask, and the check that catches a wrong answer.

  1. 1

    Ask a question you can finish

    One behaviour, one decision it informs. Example: how a partial payment changes an invoice balance.

    It’s wrong ifThe agent can't walk through one concrete example with real inputs and outputs.
  2. 2

    Get REA connected and confirmed

    Run the guided setup, then doctor, then call binary_session inside the agent before any real target.

    It’s wrong ifAnswers arrive without a single REA tool call: you're reading the model's guesses.
  3. 3

    Turn a business rule into a spec

    Inputs, stored fields, formula, edge cases, plus test cases checked against the original's own output.

    It’s wrong ifYour version and the original disagree on a test case, even by one cent.
  4. 4

    See what has to survive a copy

    Find what an app writes to the clipboard and what it keeps locally, then design your own copy and paste.

    It’s wrong ifThe explanation doesn't predict what lands in a plain text editor, an email and your app.
  5. 5

    Your own app, your equipment, an old program

    Start with software you own or rely on. Ask what it sends, stores or calculates when you do one thing.

    It’s wrong ifIt only works for the example you watched. Test with a new file or a read-only command first.

Sources: REA on GitHub (stars via GitHub API, 19 Oct 2026); REA installation guide; REA security policy.
Powered by Thorsten Meyer AI

From Software Behavior to Specifications

For developers building replacements, integrations or internal tools, a familiar interface does not reveal the rules that govern calculations, stored records or edge cases. REA’s proposed value is to help an agent investigate a specific behavior and produce evidence that can inform a software specification. That approach could reduce reliance on guesswork when reproducing complex business workflows.

The QuickBooks example is relevant because accounting software must handle more than visible forms: balances can depend on transaction types, report basis and account classifications. A successful match on one sample company, if independently reproduced, would show that the method can capture some consequential behavior. It would not by itself establish compatibility across all QuickBooks features, data sets or versions.

The workflow also changes how AI-assisted development is checked. Meyer recommends asking an agent to explain a complete example with real inputs and outputs, and to mark findings as observed, inferred or unknown. That distinction helps readers separate evidence from a model’s plausible but untested explanation.

Amazon

software reverse engineering tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

How REA Investigations Are Framed

Meyer’s report advises against asking an agent to “figure out how this program works,” because the task has no clear stopping point. Instead, it recommends naming one behavior and the decision the investigation will inform—for example, how a partial invoice payment changes the remaining balance and which account receives the posting. The agent should identify stored data, calculations and conditions that alter the result.

Setup is only one part of the process. The article says REA’s diagnostic command checks installation files and prerequisites, but does not confirm a live connection to the agent. Users are advised to verify that the agent can call an REA tool before trusting answers about a target program. A response produced without an actual tool call may be a model-generated guess rather than an inspection result.

The report identifies a key safety limitation: REA runs analysis locally, but results are passed to the agent and may also be handled by the model provider under its data policy. The project describes itself as not a sandbox. Opening an untrusted program exposes it to analysis tools running with the user’s permissions, so the article warns readers to treat unknown binaries like other untrusted files.

“This is not a sandbox.”

— Reverse Engineer Anything project, as quoted in Thorsten Meyer’s report

Evidence and Safety Limits

The supplied report does not include independent verification of Ledger Reborn’s reported cent-level match, the full case study, or a detailed test matrix. It is unclear how many transactions, accounting features, edge cases or QuickBooks versions were covered. Matching statements for one official sample company would not establish broad compatibility.

Other details also need care. The reported GitHub counts and version describe the project on October 19, 2026, and may change. The source identifies the maintainer as anonymous, but provides no further information about governance or long-term support. It also does not specify which model provider handled the case study’s results or what data policies applied. Users should check current project documentation and provider terms before inspecting sensitive software or data.

Verify Tools Before Inspection

The immediate next step for a developer trying REA is to confirm that the agent can call its tools, then test the workflow on a harmless program they own. For a real investigation, the report recommends choosing one bounded behavior, collecting a concrete input-output example and checking the agent’s explanation against observable results. Any implementation derived from that work still needs its own tests, especially for exceptions and data migration.

Further evaluation of the QuickBooks example would require the complete case study and reproducible tests across more transactions and reporting conditions. The supplied source does not state whether additional validation or project releases are planned. Until such evidence is available, the case is a reported demonstration of a method—not proof that REA can reproduce accounting software generally.

Key Questions

What is Reverse Engineer Anything?

REA is an open-source toolkit that connects AI coding agents to software-analysis tools through an MCP server, a command-line utility and an agent skill. The source describes support for several application types, with available analysis depending on installed tools.

Did the Ledger Reborn app fully reproduce QuickBooks?

The report says its profit-and-loss statement, balance sheet and trial balance for Intuit’s official sample company matched QuickBooks Desktop account by account, to the cent. The supplied material does not provide independent verification or show that every feature and edge case was reproduced.

Does REA run safely in an isolated environment?

Not necessarily. The project warning quoted in the report says REA is not a sandbox; analysis tools run with the user’s permissions. The article advises treating unknown binaries as untrusted files.

Can a user assume the agent inspected a program because it answered questions about it?

No. Meyer says users should verify that the agent actually calls an REA tool. A diagnostic command can check files and prerequisites but, according to the report, does not prove the live agent connection works.

Source: ThorstenMeyerAI.com

HALLOWEEN

Halloween Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

Blanchard's Diverse Heritage and Advocacy Impact

With a blend of diverse backgrounds, Blanchard's advocacy for inclusivity in media leaves a lasting impact on Hollywood and beyond.

Yen faces new pressure as markets see chances for US rate hike

The yen faces renewed pressure amid market expectations of a U.S. interest rate hike by year’s end due to inflation concerns.

When AI Goes Wrong: Claude’s False Tip In A Philadelphia Homicide Case

An AP headline says Claude submitted a false tip about an unsolved Philadelphia homicide. The available account leaves key details unconfirmed.

Twenty Years Of RISC OS Open

RISC OS Open marks two decades of development, collaboration, and community growth since its founding in 2003, highlighting its impact on computing.