Skip to content
← All guides

REA: Claude Can Now Figure Out How Any App Works

See a feature you love in an app? REA lets your Claude look inside that app, figure out how the feature actually works, show you the evidence, and build your own version of it. It's free, open source and sitting at 463K stars on GitHub. Here's the setup, the exact prompts I'd use, and everything that trips people up.

How it works

Normally, to know how an app does something, you'd need its source code. Nobody hands you that. REA gets around it by looking at the app itself, the files that are already on your computer.

  1. You ask Claude about a feature. "How does search work in the Notes app?"
  2. Claude uses REA to look inside the app. REA inspects the installed app (or the website) and traces the code behind that feature. No source code needed.
  3. You get the evidence. REA hands back what it found, where it found it, and what it couldn't confirm. No guessing dressed up as fact.
  4. Claude builds your version. From what it learned, it writes and tests a similar feature in your own project.

It works on desktop apps, websites, Android apps, games and a lot more. The analysis runs on your own computer.

What you need

  • Claude Code Or the Code tab in the Claude desktop app. Any paid plan.
  • Node.js + npm Version 22.23.4+, 24.22.1+ or 26.12.1+. The first prompt checks this.
  • A Mac, Windows or Linux computer REA runs on your own machine.
  • An app or website you want to understand Something on your computer, or a URL.

That's it for apps built with web tech (Notion, Slack, Discord, Obsidian, VS Code) and for websites. Apps compiled to machine code need one free extra tool, covered in the 6 things that break this.

1. Set it up (5 minutes)

Open Claude Code (or the Code tab in the Claude desktop app) and paste this first. It checks your computer is ready and tells you exactly what to do if it isn't.

Prompt 1: Get my computer ready for REA
I want to set up REA (Reverse Engineer Anything, github.com/morluto/rea) so you can use it. Before I install it, check my computer for me:

1. Run node -v and npm -v. REA needs Node.js 22 (22.23.4 or newer), 24 (24.22.1 or newer) or 26.12.1 or newer, plus npm.
2. If Node is missing or too old, tell me the exact, simplest way to install the right version on my computer (I'm not a developer, so one method only, step by step).
3. Tell me if I'm on Mac, Windows or Linux, and whether anything else on my machine will get in the way.
4. Then tell me to run this myself in my Terminal, because it asks me questions: npx rea-agents setup
   Tell me what to pick when it asks (choose Claude Code, review the changes, approve them).

Don't install REA yourself. Just get my computer ready and walk me through it.

Then open Terminal (Mac: press Cmd + Space, type Terminal. Windows: search for Terminal or PowerShell) and run this one line yourself:

Install REA
npx rea-agents setup
  1. Choose Claude Code when it asks which agents to set up. Pick others too if you use them (Codex, Cursor and Gemini CLI all work).
  2. Review the changes and approve them. It backs up your existing settings first.
  3. Restart Claude Code. Close it fully and open it again. New tools only load on startup.

Now check it worked:

Prompt 2: Is REA connected?
Check that REA is connected. List the REA tools you can use right now, grouped by what they're for (apps, websites, native programs, files), in plain English. Then tell me which kinds of apps on my computer you could investigate today without me installing anything else.

2. Your first investigation

Give Claude somewhere to put what it builds. Paste this once:

Prompt 3: Make a folder for your rebuilds
Make me a new folder on my Desktop called my-rebuilds and set it up as a simple web app I can open in my browser (one command to start it, nothing fancy).

That's where everything I rebuild with REA will go. When it's ready, open it in my browser so I can see it works, and tell me the one command to start it again later.

Then try the example straight from REA's own README. Swap "Notes" for any app on your computer and "search" for any feature you want.

Prompt 4: The REA example
Understand how search works in the Notes app, show me the evidence, and build a similar feature for my project.

Watch what comes back. You should see where the app lives, the parts of its code that handle the feature, an explanation, and a list of things REA couldn't confirm. That last part is the point: it tells you what it knows and what it doesn't.

3. 5 prompts to rebuild anything

Fill in the brackets and paste. Each one asks for evidence and asks Claude to write its own version instead of copying anything.

1/ Rebuild one feature from an app on your computer

Use it when: You love one thing an app does (Notion's slash menu, Slack's quick switcher, the way Obsidian links notes) and want it in your own thing.

Prompt 5: Rebuild one feature from an app on your computer
Use REA to investigate how [THE FEATURE] works in [THE APP] on my computer.

1. Find where the app is installed and what it's built with.
2. Trace the code behind [THE FEATURE]: what happens when I [WHAT I DO, e.g. type / and the menu pops up].
3. Explain how it works in plain English, with the evidence for each part, and tell me what you couldn't confirm.
4. Then build my own version of it in my-rebuilds on my Desktop. Write it yourself from what you learned. Don't copy their code, their text or their images.
5. Run it, test it, and open it in my browser so I can try it.

2/ Rebuild something from a website

Use it when: A site has a booking flow, a pricing toggle, a signup quiz or a search bar you want for yours.

Prompt 6: Rebuild something from a website
Use REA to investigate [THE PART OF THE SITE, e.g. the booking flow] on [WEBSITE URL].

Look at the page structure, the scripts and what it sends and gets back while I'd use it. Then explain step by step how it works, with the evidence, and what you couldn't confirm.

After that, build my own version in my-rebuilds on my Desktop, in my own design, with my own text. Don't copy their code, their text or their images. Open it in my browser when it works.

3/ Replace an app you pay for every month

Use it when: You pay monthly for a tool and only use one or two things in it.

Prompt 7: Replace an app you pay for every month
I pay for [THE APP] every month but I only really use [THE 1-2 THINGS I USE].

Use REA to investigate how those features work in the app on my computer (or on [WEBSITE URL] if it's a website). Explain how each one works, with the evidence.

Then build me a simple version that does just those things, in my-rebuilds on my Desktop. Keep it small and easy to run. Tell me honestly what my version can't do that theirs can.

4/ Just explain how it works (no building)

Use it when: You're curious, or you want to know how hard something is before you build it.

Prompt 8: Just explain how it works (no building)
Use REA to figure out how [THE FEATURE] works in [THE APP OR WEBSITE].

Don't build anything. Give me:
1. How it works, in plain English, like you're explaining it to a friend.
2. The evidence behind each part (what you actually found, and where).
3. What you couldn't confirm.
4. How hard it would be to build my own version, and the simplest way to do it.

5/ Figure out an old app you own but lost the code for

Use it when: You (or your business) paid someone to build something years ago and nobody has the source code anymore.

Prompt 9: Figure out an old app you own but lost the code for
I own [THE APP] but I don't have its source code anymore. It's at [WHERE IT IS ON MY COMPUTER].

Use REA to map how it works: what it's built with, its main parts, and how [THE MOST IMPORTANT FEATURE] works, with evidence. Then write me a plain-English document I could hand to a developer (or back to you) to rebuild it, and save it in my-rebuilds on my Desktop.

Where your apps actually live

You can just name the app and Claude will usually find it. If it can't, point it here:

  • Mac
    Apps are in your Applications folder. Apps built with web tech keep their code inside the app, usually at /Applications/[App].app/Contents/Resources/app.asar.
  • Windows
    Most apps are in C:\Program Files or in your user folder under AppData\Local\Programs\[App]. Look for a resources folder with app.asar inside.
  • Websites
    No files needed. Give Claude the URL. REA uses a Chrome-family browser to watch the page.

The 6 things that quietly break this

  • Your Node.js is too old
    REA needs Node.js 22 (22.23.4+), 24 (24.22.1+) or 26.12.1+. Older versions fail during setup with an error that doesn't say why. The first prompt checks this for you before you install anything.
  • You didn't restart Claude Code
    Setup adds REA to Claude Code, but Claude Code only loads new tools when it starts. Close it fully (or quit the desktop app) and open it again. If Claude says it has no REA tools, this is almost always why.
  • You let Claude run the setup
    npx rea-agents setup asks you questions: which agents to set up, and whether to approve the changes. Run it yourself in Terminal so you can answer them. It backs up your existing settings before it changes anything.
  • Native apps need one more tool
    Apps built with web tech (Notion, Slack, Discord, Obsidian, VS Code and most websites) work with nothing extra. Apps compiled to machine code need a decompiler like Hopper, Ghidra or IDA. Setup can install Hopper for you if you approve it. On a Mac, Hopper shows a first-run box asking for demo mode or a license: open it once and click through before you ask Claude to use it.
  • You're on an old version
    REA ships fixes constantly. If something breaks, update first by running npx rea-agents@latest setup again, then restart Claude Code.
  • You downloaded a copycat
    Only get REA from github.com/morluto/rea, rea.tools or the rea-agents package on npm. A repo with a similar name or a copied README is not the real thing.

Stay on the right side of this

REA is for understanding how things work and building your own version. It's not for pirating apps.

  • Use it on software you own or are allowed to look at, and for learning, research, and making things work together. That's what REA's own disclaimer covers.
  • Build your own version. Don't copy another company's code, text, logos or design and ship it as yours.
  • Don't use it to get around a paywall or a license check.

I didn't build REA

REA is made by morluto and 400+ contributors, free and open source under the MIT license. The prompts in this guide are mine. Everything else is theirs.

Their site has illustrated guides and real case studies, like rebuilding a calculation from DX-Ball byte for byte and tracing how Notion's clipboard works.

See REA on GitHub →

If it saves you a subscription, go star the repo. That's the whole payment they asked for.