RSS
Tools

Reverse-engineering 10 paid apps with Opus 5.5 and REA

Movez published a long guide to studying how paid apps work and rebuilding clean-room versions with Opus 5.5 in Claude Code, using the MIT-licensed REA MCP server. He reports 10 projects in 18 days and 13,000+ downloads. The setup, the contract-first agent team, and the legal lines.

space gray iPhone X
Photo by William Hook on Unsplash

Updated November 20, 2026: Expanded with REA's setup and requirements, the guide's map, contract and agent-team steps, and the limits both set.

Movez, who writes as 0xMovez on Substack, has published a long guide to what he calls product reverse-engineering. You study what an existing app does, write down the evidence, then have Claude Code with Opus 5.5 build your own version from scratch. He says he ran the pipeline ten times in 18 days, typed no code by hand, and got more than 13,000 downloads and about 850 GitHub stars across the projects. Those are his own figures. The examples he names include DuoDesk, which shares one mouse and keyboard between a Windows PC and a Mac, and Cleanly, a cleanup utility.

The engine: REA

The guide is built around REA, short for Reverse Engineer Anything: an MIT-licensed MCP server and command-line tool on GitHub at morluto/rea. It gives an agent tools to inspect native binaries, JavaScript and Electron apps, .NET assemblies, Android APKs and websites, plus many narrower formats. Analysis runs locally. Results come back with the evidence and limitations behind each conclusion. For deep native analysis REA uses an existing Hopper, Ghidra, IDA or Kuna install, while static JavaScript and .NET inspection need no extra engine. The README marks a 400,000-star milestone; the repository page showed about 470,000 stars when we checked on November 20, 2026. The guide pairs it with a second open-source tool, Craft Anything from the ArtCraft suite, which studies a target, builds your version, compares it with the original and refines it. Movez sums up the split as REA explaining how something works and Craft Anything building your version.

Setting it up

The README requires Node.js 22.x (22.23.4 or later), 24.x (24.22.1 or later) or 26.12.1+, plus npm; the guide's own setup notes list older minimums, so go by the README. One command registers REA with your agents. Setup supports Claude Code, Codex, Cursor, Gemini CLI, Grok Build and others, and backs up any configuration it changes. Restart your agent afterwards. The guide then runs doctor to check what works on the machine and providers to see which analysis engines are available.

npx rea-agents setup
npx -y rea-agents@latest doctor --json
npx -y rea-agents@latest providers --json

# or install the CLI and inspect an Electron app yourself
npm install --global rea-agents
rea analyze-javascript-application /absolute/path/to/app --json

The README warns that only morluto/rea, rea.tools and the rea-agents npm package are official, and that a similar-looking repository name proves nothing. That is worth taking seriously for a tool you give access to binaries on your machine.

The pipeline in the guide

  • Map: REA inspects the target and writes research/MAP.md, with every line citing an evidence ID. Anything that can't be proven is logged as unknown rather than guessed.
  • Contract: before any agent starts, the guide tells you to write CONTRACT.md, describing the interface between UI and backend, and a shared types file implementing it. For Cleanly, the lead session wrote shared/types.ts itself: 24 typed IPC methods, so a missing handler became a type error.
  • Ownership: the work is split so no two agents ever edit the same file, and the ownership table is printed before launch.
  • Build and review: one builder per module, each followed by a reviewer and a fixer.
  • Attack: a safety agent tests every delete, overwrite and network path on a fake home folder. In Cleanly it found 11 real issues. A design critic screenshots each screen and sends weak ones back. Throughout, the guide keeps agents read-only on the target and has them work on copies.
  • Ship gate: an integration agent routes findings to their owners, then runs typecheck, build and a smoke test. The packaged app is tested on real hardware, with destructive actions left to the human.

Not every project started from a paid app. For DuoDesk, Movez says the starting point was an existing open-source project's GitHub URL, which Claude cloned and mapped with read-only agents before rebranding it. For a router-security tool called Bastion, the target was his own router.

Both REA and the guide draw the same boundary. The guide's suggested CLAUDE.md rules limit targets to software you own or are licensed to inspect, open-source code, public websites and your own hardware. They rule out cracking licences, bypassing DRM or logins, and copying code, strings, icons or names, and they keep research notes and product code in separate folders; a nocopy.py script checks for shared strings before anything ships. REA says it is for lawful research, interoperability and analysis of software you are authorised to examine. Commercial tools such as IDA or Hopper must be properly licensed. According to the guide, REA also marks target content as untrusted and tells the agent never to follow instructions found inside it. Our own view, not the guide's: rules like these do not settle every legal question about rebuilding a competitor's features, so if you plan to sell a clean-room copy, get proper legal advice first.

Who it is for

Our reading is that this suits solo developers and small teams who want to ship focused desktop tools quickly and are comfortable reviewing a lot of agent output. For a single feature, REA's evidence-backed trace may be all you need; the guide's contract and one-owner-per-file rules exist for the case where several builders work in parallel, which is where the full pipeline earns its overhead.

Our take

The part worth borrowing is not the reverse-engineering. It is the contract-first structure: evidence before claims, a typed interface before parallel work, one owner per file, and agents whose only job is to attack the others. That pattern works for any large Claude Code build, including entirely original ones. The download and star figures are self-reported and partly driven by launch posts, so judge the method on its structure, not the numbers.

Source: How I reverse-engineered 10 paid apps with Opus 5.5 (Full-Guide) (Movez on Substack), REA: Reverse Engineer Anything (GitHub)

This story first appeared in the claudefox daily briefing for November 7, 2026.