Configuration

Defaults require nothing. Override through your profile's cordis.patch.yml:

- id: dsh-rea
  name: dsh-rea
  config:
    tools: navigate        # entry (default) | navigate | analyze | all, or an explicit name list
    version: '6.4.0'       # exact rea-agents version, pinned for stable schemas
    toolCallTimeoutMs: 300000
    env:
      REA_MCP_INPUT_SCHEMA_PROFILE: compact   # trim parameter descriptions

Field	Default	Meaning
`enabled`	`true`	Set `false` to keep the plugin installed but inert
`tools`	`'entry'`	Tier name (`entry`/`navigate`/`analyze`/`all`), an explicit array of REA tool names, or `null` for everything
`version`	`'6.4.0'`	Exact `rea-agents` version; pinning keeps tool schemas stable across restarts
`runner`	`'npx'`	Package runner used to launch REA
`env`	`{}`	Extra child environment, merged over the inherited env
`toolCallTimeoutMs`	`300000`	Per-call timeout; native analysis can run long
`failOnStartupError`	`false`	Reject activation when REA fails to start, instead of degrading to no tools

Usage

Registered tools use the rea__ prefix and route by target:

Target	First tool
ASAR or extracted JavaScript/Electron tree	`rea__analyze_javascript_application`
Native executable	`rea__open_binary`, then `rea__binary_overview`
Archive, ZIP/APK/IPA/MSIX, or DMG	`rea__open_binary`, then `rea__inspect_artifact`
Managed PE/CLI assembly	`rea__inspect_managed_artifact`
Browser page already open	`rea__list_browser_targets`
Electron runtime already open	`rea__list_electron_targets`

REA reports each result as an evidence_id. When a response is too large for the stdio budget, REA says so and points at rea__export_evidence_bundle (in the default tier) to retrieve the retained records.

dsh-rea

같은 패키지 이름의 다른 저장소

설치

문서

Configuration

Usage