REA
REA quickstart: inspect a static artifact safely
Preview agent setup, then use the CLI on an authorized JavaScript or Electron sample
What you will learn
- Review the proposed setup
- Start with a bounded file
- Check readiness by task
Before you start
- A target you own or are authorized to examine
- Node.js and npm
- A selected local provider only if native analysis is needed
Use a harmless artifact to test setup, provenance, limitations and cleanup
Key takeaways
- Setup previews changes and asks approval.
- Static JavaScript analysis needs no native engine.
- A structural report is not runtime proof.
Review the proposed setup
The documented command is `npx rea-agents setup`. It asks which supported agents to configure and shows exact configuration paths and changes before writing. npm package approval and REA setup approval are separate steps.
Existing registrations can be preselected; a newly detected client is not automatically selected. Backups and atomic writes protect existing configuration, but you should still review the plan and restart the named agent afterward.
Start with a bounded file
For a static JavaScript or Electron directory or ASAR, the README shows `analyze-javascript-application` with `--json`. This path needs Node.js and npm but does not require Ghidra or Hopper.
Use an absolute path to an authorized, disposable sample. Inspect the module and import evidence in the JSON before asking an agent to infer behavior; static structure alone does not establish a runtime effect.
Check readiness by task
The installation guide provides scoped readiness checks. A native task needs a provider; a browser task needs its observation prerequisites; static JavaScript has a different set.
We did not execute setup or inspect a local target. Treat the commands below as documentation to verify in your environment, especially because the project changes quickly.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Review the package source and setup plan.
- 2
Run a static analysis on an authorized sample.
- 3
Read evidence and limitations before interpretation.
Copy-ready example
npx rea-agents setup
npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --jsonFrequently asked questions
Will setup install Hopper automatically?
No. The installation guide describes a separate optional choice and explicit approval.
Can I use the CLI without registering an agent?
Yes. The README documents a direct CLI command for static JavaScript or Electron artifacts.
Sources
- REA / README.mdSource checked 2026-10-14
- REA / docs/installation.mdSource checked 2026-10-14
- REA / docs/cli.mdSource checked 2026-10-14
- REA / src/application/Setup.tsSource checked 2026-10-14
- REA / src/application/SetupSkill.tsSource checked 2026-10-14
- REA / docs/javascript-application-workflows.mdSource checked 2026-10-14