REA Reverse – Engineer Anything
TL;DR · AI 摘要
REA是面向编码代理的反向工程工具,通过自然语言提示分析程序逻辑,附带计算器和游戏加速案例。
核心要点
- 使用npx rea-agents@latest setup命令可安装REA工具
- 计算器10%按钮实际执行200*10%+200=220的计算逻辑
- Chrome恐龙游戏加速规则为初始速度6逐步提升至13
结构提纲
按章节快速跳转。
思维导图
用一张图看清主题之间的关系。
查看大纲文本(无障碍 / 无 JS 友好)
- REA工具
- 核心功能
- 反向工程分析
- 自然语言交互
- 使用案例
- 计算器逻辑解析
- 游戏速度重构
- 技术实现
- x64汇编分析
- 代理集成方案
金句 / Highlights
值得收藏与分享的关键句。
MOV EAX, dword ptr [R13 + 0x18]指令序列揭示计算器百分号按钮的数值处理逻辑
通过单条自然语言提示'Why does 200 + 10% give 220?'即可触发完整反向工程流程
恐龙游戏加速规则为初始速度6,最大13的线性增长模型
REA â Reverse Engineering for Your Coding Agent
Reverse engineering, with your coding agent
Find out how software works.
REA gives your agent the tools to inspect a program and explain what it does.
See how REA works â
Setup guide
Showcases â
Already know RE? Skip to analysis guides â
Want to go deeper? Read the Blog â
Set up REA
Copy this into your coding agent:
Your coding agent
Copy
⺠Install REA and connect it to this coding agent using npx rea-agents@latest setup. Show me the setup plan for approval, then verify the installation.
Or run this in your terminal:
npx rea-agents@latest setupApprove the setup plan, then restart your agent.
What is reverse engineering?
Finding out how software works by examining the program itself.
The goal: understand a feature well enough to explain it , change it or rebuild it.
One question: why does Calculator give 220 for 200 + 10%?
Before REA · You investigate it yourself
01
Decode branches
02
Trace calls
03
Recover the rule
Original x64 · selected instructions
0x180124945: MOV EAX, dword ptr [R13 + 0x18]
0x180124949: CMP EAX, 0x5c
0x18012494c: JZ 0x180124aba
0x180124952: CMP EAX, 0x5b
0x180124955: JZ 0x180124aba
0x18012495b: MOV EDX, 0x64
0x180124960: LEA RCX, [RSP + 0x160]
0x180124968: CALL 0x180122650
0x18012496e: LEA RDX, [R13 + 0x160]
0x180124975: LEA RCX, [RSP + 0x78]
0x18012497a: CALL 0x180109720
0x18012497f: MOV RSI, RAX
0x180124982: MOV qword ptr [RSP + 0x28], RAX
0x180124987: LEA RDX, [RSP + 0x160]
0x18012498f: MOV RCX, RAX
0x180124992: CALL 0x180123190
; ⦠value-copy instructions omitted â¦
0x180124a14: MOV RDX, RDI
0x180124a17: LEA RCX, [RSP + 0xf8]
0x180124a1f: CALL 0x180109720
0x180124a24: LEA R8, [RSP + 0x30]
0x180124a29: MOV RDX, RAX
0x180124a2c: LEA RCX, [RSP + 0xb8]
0x180124a34: CALL 0x180123c10You decode the instructions, follow the calls and reconstruct the calculation.
With REA · You ask your agent
One prompt.
Ask your agent in plain English.
Example prompt · Calculator
⺠Use REA to inspect Windows Calculator. Why does 200 + 10% give 220?
Example answer · based on the findings
After +, the % button takes a percentage of the first number.
10% of 200 = 20â
200 + 20 = 220
REA supplies
The handlerâs instructions, decompiled code and calls.
Your agent explains
Which branch applies, what it calculates and how to rebuild it.
Selected assembly from the installed Calculator DLL. The thoughts and reply illustrate the findings. Continue with the Calculator example â
Let's try two examples. Change a game's speed, then return to Calculator and rebuild its % button.
Example 01 · Chromeâs dinosaur game
Why does the dinosaur get faster?
Goal
Rebuild the game with
adjustable speed.
Why reverse engineer it?
To reproduce its acceleration, we need
the rule in the running game
: how fast it starts, how much it increases and when it stops.
Play the reconstruction
Play
Jump â
Restart
Speed
6.0
Use the recovered acceleration rule
Original rule: start at 6, then increase toward 13.
Move the slider to set your own speed. Space or Jump clears a cactus.
REA returned
The script actually running in the page. The agent reads its update function and speed settings, then uses that rule in a new game.
Example prompt · Dinosaur game
⺠Use REA to inspect this dinosaur game. Why does it get faster? Show the speed rule, then build a small version with an adjustable speed.
Inspected target: wayouâs Chromium-derived browser edition .
REA · loaded index.js · selected lines
if (this.currentSpeed < this.config.MAX_SPEED) {
this.currentSpeed += this.config.ACCELERATION;
}Start at 6. Add 0.001 each update without a collision, while speed is below 13 .
Open the speed lab â
What each part does
- 01 · REA Read the running gameâs script Return its actual code and settings to the agent.
- 02 · Your agent Rebuild the rule, add a control Use the recovered acceleration in a small game with a speed slider.
- 03 · You Change the speed and play Try the original acceleration, then choose your own pace.
See the script, checks and how to try the analysis
REA inspected the HTTP browser edition through a local debugging connection and returned the loaded index.js , including its source and digest.
Selected settings from the inspected script
ACCELERATION: 0.001,
MAX_SPEED: 13,
SPEED: 6We called the original gameâs update function in a controlled browser check, with obstacles and automatic scheduling disabled. After 4,000 updates, speed was 10.0; after 10,000, it was 13.0, rounded to one decimal.
The new mini-game keeps that speed rule. Its drawing, jumping and collision code are a small teaching implementation. Open the lab to see the new code and run the same speed check.
To inspect the target yourself, follow the browser connection steps using the dinosaur page . Give your agent that page URL and your local debugging endpoint, then copy the prompt above.
Inspected speed code · Chromium Authors · BSD license
Example 02 · Windows Calculator
Rebuild Calculatorâs % button.
We saw why 200 + 10% gives 220. Now letâs recover the rules for both + and Ã, and try them.
Build a small calculator that handles
both + and à correctly.
The same button uses
different rules after + and Ã.
We inspect the installed app to find which number the percentage is applied to.
Try the calculation
200 + 10%
200 Ã 10%
200 +
20
%
=
Reset
10% of 200 = 20. Then 200 + 20 = 220.
Interactive illustration of the inspected percentage rule.
One branch divides by 100. The other also multiplies by the first number. The agent uses both to recreate the % button.
For this example, previous = 200 and current = 10 .
Example prompt · Rebuild the % button
⺠Use REA to inspect Windows Calculatorâs % button. Recover the rules after + and Ã, then build a small calculator that uses both.
Readable summary of the % handler
if (operation == multiply || operation == divide) {
percent = current / 100;
} else {
percent = current * previous / 100;
}With +
Take 10% of the first number.
10% of 200 = 20 â 200 + 20 = 220With Ã
Turn 10% into 0.1.
200 Ã 0.1 = 20From the installed app to a working % button
- 01 · REA reads calc.exe It launches the Calculator app The code opens ms-calculator: . The agent then selects the installed appâs library.
- 02 · REA reads the library Return the % handlerâs code The function checks the operator and uses the constant 100 .
- 03 · Your agent interprets it Explain and reproduce the rules Crosscheck the branch with Microsoftâs source, then try + and à above.
See the real code and how the answer was checked
REA · selected original instructions
0x180124945: MOV EAX, dword ptr [R13 + 0x18]
0x180124949:
CMP EAX, 0x5c
0x18012494c: JZ 0x180124aba
0x180124952:
CMP EAX, 0x5b
0x180124955: JZ 0x180124aba
0x18012495b:
MOV EDX, 0x64Operator IDs · Microsoftâs source
#define IDC_MUL 92 // 0x5c
#define IDC_DIV 91 // 0x5b
#define IDC_PERCENT 118 // 0x76
0x64 = 100Inspected with REA 4.1.0: Windows Calculator 11.2508.4.0, x64. The readable summary uses names from Microsoftâs public source to explain the recovered branch.
Percentage implementation · Microsoftâs test cases · Native setup guide
Your first investigation
Try REA on a small app.
Download our Notes example, trace its CSV export, and check one changed input.
Try the guided example
Want to go deeper?
Tell your agent what you want to understand or build. With REA, you can work together on anything from cloning this website to reconstructing a game from its executable.
Example prompt · Website
⺠Use REA to inspect https://rea.tools/. Clone this website for me.
Yes, this one.
Example prompt · Game reconstruction
⺠Use REA to reconstruct this game from its executable. Recover the gameplay logic in C and test it against the original.
See the DX-Ball case study â
For setup and analysis steps, choose your target:
Native binaries
Inspect functions, strings, references and call relationships in executables and libraries.
Native analysis guide
JavaScript & Electron
Map modules, routes, IPC and native dependencies from an application folder or ASAR archive.
Application workflows
Browser & runtime activity
Capture selected browser or process activity, then compare the results across runs.
Browser observation guide
Any questions?
Read the FAQ , chat with us on Discord , or open a GitHub issue for bugs and feature requests.
Join the community
Share investigations and get help from other REA users on Discord. Follow REA on X for project updates.
Join the community
Follow @reatools on X