+ ›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 command in your terminal:
+
+ npx rea-agents@latest setup
+
+
+
+ Review the plan, approve the setup, then restart your agent.
+ Already connected? Continue below.
+
+
+
+
2. Ask where the CSV is written
+
+ The example is a six-file Electron app with an
+ Export notes button. Your agent can inspect its
+ code without installing or launching Electron.
+
+
+
+ Your coding agent
+
+
+
+ ›Download https://rea.tools/examples/notes-example.zip into a
+ new example folder and unpack it. Use REA to find what happens
+ when I click Export notes. Show where notes.csv is written,
+ which fields it contains, and the relevant files and
+ lines.
+
+
+
+ Your agent downloads the files and gives the unpacked folder to
+ REA for inspection.
+
+ If your agent can’t download files, unzip this archive yourself.
+ Give it the path to the notes-example folder and the
+ same export question.
+
+
+
+
3. Follow the answer back to the code
+
Look for a short explanation with file and line references:
+
+
+ The button sends a notes:export message. The main
+ process formats the notes as CSV and writes
+ notes.csv in the user’s Downloads folder. The
+ columns are id and title.
+
+ A comma separates CSV columns. What happens when a note title
+ itself contains a comma or quotation marks?
+
+
+
+ Your coding agent
+
+
+
+ ›Predict the CSV for a note with id 1 and title Hello, "REA".
+ Then run the example’s toCsv formatter with Node.js to check
+ it. Show the prediction and actual output.
+
+
+
+
+ Expected formatter output
+
+
id,title
+1,"Hello, ""REA"""
+
+
+ The title stays in one quoted field; each quotation mark is
+ doubled. This checks the formatter directly with Node.js.
+
+
+ Run the check yourself
+
+ Open a terminal in the unpacked
+ notes-example folder:
+
- Use REA with your coding agent to inspect binaries, trace application
- code and observe runtime behavior.
+ REA gives your agent the tools to inspect a program and explain what
+ it does.
// x is the horizontal position
+double pan = (double)x;
+pan *= 1.5625;
+pan -= 500.0;
+pan *= pan_scale;
+return (int)pan;
+
+
+
+
+ Left side
+
+
+
+ x = 0 → pan = −500
+ Sound to the left
+
+
+ Center
+
+
+
+ x = 320 → pan = 0
+ Centered sound
+
+
+ Right side
+
+
+
+ x = 640 → pan = +500
+ Sound to the right
+
+
+
+ Examples of the calculation with the recorded initial scale of 1.
+ The code is a readable summary of the inspected function.
+
+
+
+ To explain this, an analyst identifies the input, follows the caller
+ and reads the values at those addresses.
+
+
+
+
+
+
+
+
+
Do I need to read assembly to get started?
+
No.
+
Ask your agent about the behavior you want to understand.
+
+
+
+
+ Example analysis · DX-Ball
+
+
+
Target · DXBALL.EXE
+
+ ›Use REA to inspect this DX-Ball executable. How does it
+ calculate left/right sound panning? Show the relevant
+ code.
+
+
+
+ Agent · explanation from the findings
+
+
+ This function converts a brick’s horizontal position into a
+ left/right sound value.
+
+
+ At the initial scale of 1, the screen center produces zero.
+ Positions to the left produce negative values; positions to
+ the right produce positive values.
+
+
+
+
+ Example prompt and explanation based on the recorded
+ investigation. Supply the executable to your agent.
+
+
+
+
+
What REA found for the agent
+
+
+ 01 · Inspect the function
+ An integer input
+ The instructions read [EBP + 0x8]. The initial
+ pseudocode had missed this input.
+
+
+ 02 · Follow the caller
+ A brick’s screen position
+ The caller passes 20 + 30 × tile_x, giving the
+ input its meaning.
+
+
+ 03 · Read the stored data
+ The calculation’s constants
+ Byte reads supply 1.5625, 500.0 and
+ the initial scale 1.0.
+
+
+
+ The agent uses these findings to explain the behavior and write
+ readable C.
+
+
+
+ The reconstruction project checked its maintained C function against
+ 3,205 original-x86 input cases and all 63 compiled bytes.
+ See the code and checks.
+
+
+
+
+
+
+
+
Your first investigation
+
Try REA on a small app.
+
+ Find out where an app exports its notes, then check how it formats
+ a title containing commas and quotes.
+
+
We provide the example files, a prompt and a result to check.
+ ›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 command in your terminal:
+
+ npx rea-agents@latest setup
-
- ›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.
+
+ Setup shows a plan for approval. Restart your agent after setup.
-
Or run this command in your terminal:
-
- npx rea-agents@latest setup
-
-
@@ -139,34 +333,6 @@
-
-
-
-
-
-
-
- REA connects your agent to analysis tools. The findings guide the
- next question, explanation or implementation.
- Open figure
-
-
-
-
-
@@ -177,12 +343,6 @@
in C, using REA to inspect the executable and independent tests to
check the recovered behavior.
-
- To recover a sound-pan calculation, the agent used REA to inspect
- the instructions, follow a caller and read the constants. Those
- findings led to a C function checked against the original behavior
- and all 63 compiled bytes.
-