A practical REA command reference.

Setup and diagnostics

These commands use the current npm package without requiring a global install. Use an explicit package version when reproducing an old investigation.

npx rea-agents@latest setup
npx rea-agents@latest doctor --client codex --json
npx rea-agents@latest providers --json
npx rea-agents@latest --help

For frequent terminal use, install the CLI globally. The remaining examples use the resulting rea command.

npm install --global rea-agents
rea --help

JavaScript and Electron

Analyze an extracted directory or ASAR statically. Save large results to a local file so you can inspect them again instead of repeating the initial analysis.

rea analyze-javascript-application "/path/to/app" --json > app-evidence.json

Evidence files can be large. The official CLI guide documents summary and module views that keep follow-up queries bounded. A static module relationship alone does not establish that a branch ran.

Native binaries

Configure a supported native provider first. Here Ghidra is selected explicitly so another available provider does not change the investigation unexpectedly.

rea analyze /path/to/program --provider ghidra --json
rea search /path/to/program "export" --provider ghidra --json
rea function /path/to/program main --provider ghidra --json

Replace main with an actual symbol or address found in your target. Stripped binaries may have no useful function names. Provider and format support vary; inspect availability before relying on a command.

Managed assemblies

Inspect a .NET PE/CLI assembly’s identity before narrowing to specific types. These static commands do not load or execute the assembly.

rea inspect-managed-artifact /path/to/Assembly.dll --json
rea inspect-managed-members /path/to/Assembly.dll --json
rea inspect-managed-members /path/to/Assembly.dll --type Example.Parser --json

The type name is illustrative. Use the exact name returned by your own inventory. A file extension alone cannot distinguish managed code, NativeAOT, or a bundled host.

Read the result before the next command

Look for artifact identity, source references, truncation, and limitations. Preserve unknowns. An empty result may mean a query had no matches, a provider lacks a capability, or the target was not admitted; those outcomes require different next steps.

Check the installed version’s help for exact options. The official documentation can describe features ahead of the latest published release.