Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk.
Authorization notice. This tool is dual-use. Only use it on software, sites and systems you own or have explicit permission to test, and follow the relevant licenses and terms of service.
WhoSolo founder who wants a comparable feature in their product after studying how another app does it
The problemYou know what the feature does but not how to build it, and copying blindly risks missing key details.
The outcomeA working implementation in your project, grounded in what the agent observed in the target app.
Steps
Run npx rea-agents setup and restart your agent.
Ask the agent to investigate the feature in the target app and explain it first.
Ask it to build a version for your project and test it.
Review the code and compare it against the evidence it listed.
Prompt for your agent
Use REA to investigate <feature> in <app> at <path>, show the evidence, then build a version for my project at <project path> and test it. Verify the result matches the behavior it observed, not just a guess.
Caveat. Reimplementing another product's behavior can raise copyright, license and terms-of-service issues. Write your own code and only study apps you are permitted to inspect.
Let your agent inspect a site's page structure, scripts and network calls and explain what the client does.
Intermediate
45 minutes
Claude Code
Codex
Cursor
Gemini CLI
Seen in the wild
Evidence (similar to what people reported): X, Oct 2026
WhoFrontend developer curious how a web app wires its UI to its scripts and requests
The problemMinified scripts and network traffic make it hard to see how a web app actually works.
The outcomeA summary of the page structure, scripts and observed network requests for the site.
Steps
Run npx rea-agents setup and restart your agent.
Make sure a Chrome-family browser is installed.
Ask your agent to observe the target website with REA and list scripts and network calls.
Ask it to explain the part of the behavior you care about.
Prompt for your agent
Use REA to observe <website url> in a browser and summarize its page structure, scripts and network requests. Explain how <feature> works and verify claims against the observed requests.
Caveat. Observation covers the client side only. Server logic can only be inferred from responses, and you should respect the site's terms of use.
WhoIndie developer who likes a feature in a desktop app and wants to understand how it is built
The problemThe app has no public source code, so you cannot tell how the feature is put together.
The outcomeA written explanation of how the feature works, with the evidence listed and unknowns flagged.
Steps
Run npx rea-agents setup, pick your agent, approve the changes, then restart the agent.
Ask your agent to investigate one specific feature in the target app using REA.
Ask it to show the evidence for each claim and mark anything it is guessing.
Read the explanation and ask follow-up questions about the parts you will reuse.
Prompt for your agent
Use REA to work out how <feature> works in <app> at <path>. Show the evidence, flag what you are guessing, and summarize the design in plain words. Verify every claim points to a file, symbol or observed behavior.
Caveat. Only analyze software you own or are licensed to inspect, and check the app's license terms. REA can only infer backend logic from what the client exposes.
Use your agent to inspect a game's WASM web build and surface what it contains.
Advanced
1 hour
Claude Code
Codex
Cursor
Gemini CLI
Seen in the wild
Evidence (similar to what people reported): X, Oct 2026
WhoHobbyist or modder who wants to know how a cross-platform game's web build is put together
The problemThe web version ships as compiled WebAssembly, which you cannot read directly.
The outcomeA decoded view of the WASM imports, exports and sections, plus the agent's notes on what they suggest.
Steps
Run npx rea-agents setup and restart your agent.
Download or locate the .wasm file from the game you are allowed to inspect.
Ask your agent to inspect the WASM artifact with REA and decode it.
Ask it to explain the notable imports and exports.
Prompt for your agent
Use REA to inspect the WASM artifact at <path to .wasm>, decode its sections and imports/exports, and explain what stands out. Verify against the decoded output and flag any guesses.
Caveat. WASM decoding needs the caller-supplied WABT 1.0.42 toolchain. Only inspect builds you have the right to analyze.
Feed a saved network capture to your agent to see requests, responses and the payloads they expose.
Intermediate
45 minutes
From the README
Claude Code
Codex
Cursor
Gemini CLI
WhoDeveloper debugging how an app talks to its server using a capture they already recorded
The problemA raw capture has hundreds of requests and no clear picture of what the app actually sends.
The outcomeA readable breakdown of requests, responses and exposed payloads tied to source locations.
Steps
Export your traffic as a HAR file or a Fiddler Everywhere SAZ file.
Run npx rea-agents setup and restart your agent.
Ask the agent to analyze the capture with REA.
Ask it to explain the calls behind the feature you are tracing.
Prompt for your agent
Use REA to analyze the network capture at <path to .har or .saz>, list the key requests and responses, and explain which calls drive <feature>. Verify each claim against a specific request in the capture.
Caveat. Captures may contain tokens and personal data, so scrub them before sharing. On Linux, native mitmproxy captures need mitmdump installed.
Run one command on an extracted Electron app or ASAR to see its modules, imports and process boundaries.
Beginner
30 minutes
From the README
Any agent
WhoDeveloper vetting or learning from an Electron desktop app they have installed
The problemPackaged Electron apps hide their structure inside bundled files, so you cannot easily see what talks to what.
The outcomeA JSON report of modules, imports, Electron boundaries and the evidence for each.
Steps
Locate the extracted app directory or ASAR file on disk.
Run npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json
Read the report for modules, imports and Electron boundaries.
Feed the JSON to your agent and ask it to explain the feature you care about.
Prompt for your agent
Run REA's analyze-javascript-application on <path to extracted Electron app> and explain the main modules, imports and IPC boundaries. Verify each finding cites evidence from the report.
Caveat. On Linux you need a procps-compatible ps on PATH. Replace the example path with your own, such as a Windows path like D:/apps/example.
Decode a Unity IL2CPP metadata file to see assembly images, type names and method names.
Advanced
1 hour
From the README
Claude Code
Codex
Cursor
Gemini CLI
WhoGame modder or QA engineer who needs the class and method names in a shipped Unity game
The problemIL2CPP compiles game code to native, hiding the original type and method names.
The outcomeA list of assembly images, types and methods with index ranges from the metadata file.
Steps
Locate the global-metadata.dat file from the game you are allowed to inspect.
Run npx rea-agents setup and restart your agent.
Ask the agent to inspect the IL2CPP metadata with REA.
Ask it to summarize the types and methods related to the system you care about.
Prompt for your agent
Use REA to decode the IL2CPP metadata at <path to global-metadata.dat> and list assembly images, types and methods related to <system>. Verify names come from the decoded output.
Caveat. Static decoding supports metadata versions 29, 31 and 39 only. Check the game's terms before analyzing it.
Connect your agent to Hopper, Ghidra or IDA and ask what a native program's function does.
Advanced
1 hour 30 minutes
Claude Code
Codex
Cursor
Gemini CLI
Seen in the wild
Evidence (similar to what people reported): Reddit
WhoEngineer inheriting an old compiled tool whose source is lost, needing to know what one routine does
The problemYou only have the compiled binary and cannot read assembly fluently.
The outcomePseudocode, strings, symbols and call references for the routine, explained in plain words.
Steps
Install Hopper, Ghidra or IDA locally and configure it as the provider.
Run npx rea-agents setup and restart your agent.
Ask the agent to open the binary and explain the function you care about.
Ask it to show the pseudocode and references it relied on.
Prompt for your agent
Use REA with my installed <Hopper, Ghidra or IDA> to analyze the binary at <path>, explain what <function or behavior> does, and show the pseudocode and references. Verify claims against the shown output.
Caveat. Needs a native analysis engine installed and configured; setup can optionally install Hopper with your approval. Only analyze binaries you own or are authorized to inspect.
Inspect an APK's manifest, classes and decompiled methods to see what the app declares.
Intermediate
1 hour
From the README
Claude Code
Codex
Cursor
Gemini CLI
WhoIT admin or security reviewer vetting an Android app before approving it for staff devices
The problemYou cannot tell what permissions and components an APK declares or how its key methods behave.
The outcomeA report of manifest declarations, classes and decompiled methods you can review.
Steps
Install headless JADX if you do not have it.
Run npx rea-agents setup and restart your agent.
Ask the agent to analyze the APK with REA and list manifest declarations.
Ask it to decompile and explain the methods that handle the behavior you worry about.
Prompt for your agent
Use REA to analyze the APK at <path to apk>, list its manifest declarations and explain what <suspicious behavior> does in the decompiled methods. Verify each claim cites a class or method.
Caveat. APK analysis depends on JADX being available. Only inspect apps you are authorized to review; decompiled output is an approximation of the original code.
Who it is forFor developers and security-minded builders who want an AI agent to take apart an app they can run locally and explain how a feature works, with evidence.
Why it is hot+229,268 stars this week, 335k total, talked about in 3 AI sources we track
DEDUPED