this is f*cking insane, every app u pay for monthly is already sitting on ur disk as code, and one free repo now lets Claude Code read all of it down to the binary in 5 minutes of setup
REA is an open-source MCP server that plugs into Claude Code, Codex, Cursor and Gemini CLI. it runs locally, uploads nothing and backs every answer with the function, file and call behind it
setup:
→ check Node: u need 22.19+, 24.11+ or 26+, versions 23 and 25 don't work
→ run npx rea-agents@latest setup and pick Claude Code
→ REA shows every change before making it and backs up ur config
→ restart the agent fully, closing the window isn't enough
→ run the doctor check, it only reads and tells u what to fix
engines by target:
> Electron apps like Notion, Slack, Discord: nothing extra
> .NET apps and many Unity games: nothing extra
> .exe programs and old games: Ghidra 12.1 with JDK 21
> Android APKs: JDK 17+ and JADX
> websites: any Chrome-family browser
> contract bytecode: Linux x64
limits:
> it can't touch server code, only what's on ur machine
> decompiled code is a reconstruction, so always verify
> stripped C++ binaries are much harder than Unity games
first test, send Claude Code this:
use REA to investigate how [feature] works in [app]. show the function, file and call behind every step, mark what is still unknown, write a spec with no copied code, then build my version and test it against the original
study the original, ship ur own ↓
REA is most dangerous thing on the internet right now...
It lets your AI agent reverse engineer any app, down to the binary
If you use it correctly, you can rebuild any feature you pay for, for FREE
In this article, I show you how: https://t.co/3P1FNXiXzl
this is getting f*cking dangerous, Claude Code just took apart an authenticator app with 3,077 classes, found how it makes its 6-digit login codes and rebuilt it until all 133 tests passed
and nothing left the machine. REA runs locally, so the app never gets uploaded anywhere
REA is the open-source repo behind it. it plugs into Claude Code and reads any app on ur computer down to the binary, from Notion and Slack to APKs, .exe games and contract bytecode
the difference from asking a chatbot is the receipts. every claim comes with the function, file and call behind it, and anything unproven stays marked unknown until a test closes it
the same receipts work far beyond rebuilding apps:
→ an app on ur phone: every permission, tracker and domain it talks to, with the class behind each one
→ a token with no published source: the raw bytecode, with mint, blacklist, pause and owner-only functions flagged
→ an update u just installed: both versions compared, so u see what really changed
→ a rebuild u made: checked against the saved evidence before u trust it
it has limits too. server code was never shipped to u, so REA can't touch it, and decompiled code is a reconstruction, which is why the verify step exists
install REA and hand Claude Code this:
use REA to investigate how [feature] works in [app]
trace it from the interface to the exact functions. show the function, file and call behind every step
mark what is confirmed and what is still unknown. never fill a gap with a guess
write a spec of the behavior, inputs, outputs and edge cases. no copied code
build my version from the spec in a new folder and test it against the original until it passes
read what's on ur machine, build ur own. copying their code or cracking paid features is still what gets people sued
REA is most dangerous thing on the internet right now...
It lets your AI agent reverse engineer any app, down to the binary
If you use it correctly, you can rebuild any feature you pay for, for FREE
In this article, I show you how: https://t.co/3P1FNXiXzl
this is f*cking insane, one person with AI agents rebuilt a Touhou game in about 12 days and 696 of its 697 functions came out an exact match
the tool behind it is REA. it's open source, runs on ur own machine and lets Claude Code read any app down to the binary, with proof attached to every answer
ask why the Chrome dinosaur game speeds up and you get the rule from the code. speed starts at 6, adds 0.001 every update and stops at 13
the whole method fits in one line, study the original and ship ur own
split the work so each step does one thing:
→ investigate: REA follows the feature down to the function and file behind it
→ spec: Claude describes how it behaves without copying any code
→ build: ur version gets written from that description alone
→ verify: tests check ur version against how the original behaves
Compaq rebuilt IBM's BIOS with the same clean-room idea in the early 80s for about $1 million. now agents run it in an evening
an agent can explain something confidently and still get it wrong, so nothing counts until a test backs it up
every answer has to come with:
> the feature it's tracing
> the exact function and file behind it
> a clear split between what's proven and what's still a guess
install REA, then hand Claude Code this:
"Use REA to investigate how [feature] works in [app]
1. Follow it from the interface to the exact functions, with the file and line for every step
2. Describe its behavior, inputs, outputs and edge cases in a spec. No copied code
3. Build my version from the spec in a new folder
4. Write tests from the observed behavior and keep running them until they pass"
the install takes about 5 minutes, and the official practice app is the place to try it first
lifting their code or unlocking paid features is still what lands people in court
the agents are at work in the video below
REA is most dangerous thing on the internet right now...
It lets your AI agent reverse engineer any app, down to the binary
If you use it correctly, you can rebuild any feature you pay for, for FREE
In this article, I show you how: https://t.co/3P1FNXiXzl
this is f*cking insane, one person with Claude Code agents just rebuilt an entire Touhou game, and 696 of its 697 functions matched the original exactly
no source code, no dev team, about 12 days. the tool that cracked the original open is REA: free, open source, runs on your own machine and plugs straight into Claude Code
no function counted as rebuilt until it behaved exactly like the original
REA traced the original program. Claude Code handled the rebuild, one function at a time:
→ investigate: read the function and pin the evidence to a file and a call
→ spec: write down what it does, without copying a line
→ build: write a fresh version from that spec only
→ verify: compare its output against the original
writing the code turned out to be the easy part
the hard part was knowing when a rebuild was really correct
at one point a broken comparison let a wrong function pass as a match
so from then on, the tests got tested too, not just the code
the lessons from the run:
> give the agent a clear goal and clear acceptance criteria
> keep notes and checks in git so the next session picks up where the last one stopped
> treat every explanation from the agent as a hypothesis, not a fact
> test your tests
the same loop rebuilt a sound function from a 1996 game in C:
> 3,205 original test cases → all passing
> 63 compiled bytes → all reproduced
every finding came with the function, file and line behind it, so each step could be checked by hand
full reverse engineering playbook below
REA is most dangerous thing on the internet right now...
It lets your AI agent reverse engineer any app, down to the binary
If you use it correctly, you can rebuild any feature you pay for, for FREE
In this article, I show you how: https://t.co/3P1FNXiXzl
this is f*cking insane, Claude Code just rewrote a function from a 1996 game in C, and it matched the original on all 3,205 test cases
REA, the open-source repo that went from launch to 100K+ GitHub stars in a single quarter, read the old binary and recovered exactly how the sound pans left and right. the new code shares nothing with the old one except behavior
software used to hide behind "you can't see inside". now your agent just asks for the receipts
give the job two separate desks:
→ desk one: REA digs through the program and pins every finding to a function, file and line
→ the note: Claude writes down what the feature does, in plain words, with no code attached
→ desk two: a brand-new session builds your version from that note alone
→ the referee: tests based on the original's behavior call the finish line
it's the trick that let other companies build "IBM compatible" PCs in the 80s, now run by two agent sessions in one evening
before anything counts as done, you need:
> receipts for every behavior you claim to understand
> a written spec with zero borrowed code
> tests that mirror what the original actually does
> a clear note of what nobody has proven yet
install REA, then hand Claude Code this:
"Use REA to investigate how [feature] works in [app]
1. Pin every finding to the function, file and line behind it
2. Describe the behavior as a spec: inputs, outputs, edge cases. No code from the original
3. In an empty folder, build my version from the spec alone
4. Write tests from the original's behavior and loop until they all pass"
setup is roughly 7 minutes. taking their code or switching on paid features is still the fastest way to a lawsuit
watch both desks at work below
REA is most dangerous thing on the internet right now...
It lets your AI agent reverse engineer any app, down to the binary
If you use it correctly, you can rebuild any feature you pay for, for FREE
In this article, I show you how: https://t.co/3P1FNXiXzl
this is f*cking insane, one open-source repo lets Claude Code tell you what any app on your phone is really doing
REA hit 100K+ GitHub stars in 3 months. it reads apps, APKs and smart contracts down to the binary, locally, and shows the evidence for every claim it makes
ask it about that "free signals" app from Telegram and you get every permission, every tracking SDK and every domain it talks to, with the class and method behind each one
the rule it runs on is one line: no proof, no claim
give each check a specific job:
→ apps: list permissions, analytics SDKs and network domains
→ tokens: find every function that can mint, blacklist, pause or change fees
→ files: take a suspicious download apart before you ever run it
→ features: trace how something works, then build your own version
it's how someone caught the fake 113 GB "GTA 6 build" going around: they took the files apart and found malware inside
a red flag can look scary and still be a false alarm
so every finding is treated as a hypothesis until the evidence backs it up
every check has to show:
> what was scanned
> the class, function or call behind each finding
> what was confirmed and what was inferred
> what is still unknown
REA took apart an authenticator app with 3,077 classes, found exactly how it makes its 6-digit codes, and the rebuild passed all 133 test cases
install REA, then ask Claude Code:
"Use REA on this [APK / contract / file]
1. List every permission, tracking SDK and domain it talks to. Show the class and method for each
2. Flag anything that can move money, collect data or change ownership
3. Mark what is confirmed, what is inferred and what is still unknown
4. Give me a plain-English verdict and what to check deeper"
setup takes 5 minutes. start with REA's official practice app before you scan anything real
it only reads what's on your machine, so it can't touch a company's servers or move a single dollar
watch the agents at work below
REA is most dangerous thing on the internet right now...
It lets your AI agent reverse engineer any app, down to the binary
If you use it correctly, you can rebuild any feature you pay for, for FREE
In this article, I show you how: https://t.co/3P1FNXiXzl
this is f*cking insane, one open-source repo went from 0 to 100K GitHub stars in 3 months by turning Claude Code into a reverse engineer
REA reads any app on your computer down to the binary, locally, and shows the evidence for every claim it makes
ask why Windows Calculator shows 220 for 200 + 10% and you get the rule straight from the code: after +, the % button takes a percentage of the first number
the rule it runs on is one line: study the original, ship your own
give each step a specific job:
→ investigate: REA traces the feature to the exact function, file and call
→ spec: Claude writes down the behavior, with no copied code
→ build: a fresh version gets written from that spec only
→ verify: tests compare your version against the original's behavior
it's the same clean-room trick Compaq used to rebuild IBM's BIOS in the 80s, now done by agents in an evening
an agent's explanation can sound right and still be wrong
so every answer is treated as a hypothesis until a test proves it
every investigation has to show:
> the feature being traced
> the function, file and line behind it
> what was confirmed and what was inferred
> what is still unknown
one person rebuilt a Touhou game this way: 697 functions, 696 exact matches, playable in about 12 days
install REA, then ask Claude Code:
"Use REA to investigate how [feature] works in [app]
1. Trace it from the interface to the exact functions. Show the file and line for every step
2. Write a spec: behavior, inputs, outputs, edge cases. No copied code
3. Build it from the spec in a new folder
4. Write tests from the observed behavior and run them until they pass"
setup takes 5 minutes. start with REA's official practice app before you open anything bigger
copying their code or cracking paid features is still the part that gets you sued
watch the agents at work below
REA is most dangerous thing on the internet right now...
It lets your AI agent reverse engineer any app, down to the binary
If you use it correctly, you can rebuild any feature you pay for, for FREE
In this article, I show you how: https://t.co/3P1FNXiXzl
681 decisions. 3 trades.
i rebuilt the dashboard from this setup and watched it run.
the model scores 10 market signals every ~457ms.
spread, imbalance, depth, momentum, volatility.
then the rules kill almost everything:
85%+ conviction
limit orders only
paper first
opus writes the strategy once.
jev says no 3 times a second until it doesn’t.
most people lose because they take every trade.
this thing only fires when the filter clears.
the bot is easy now.
the strategy is the product.
watch the numbers.