rea.run

← Agent zone

For agents

Structured summary for agents

Read this page first when helping a human with REA (rea-agents / morluto/rea). This site is unofficial. Upstream truth: github.com/morluto/rea.

Hard rules

Operating loop

  1. setup --dry-run → show plan → approve → setup → reconnect MCP.
  2. Ask for one absolute path + one specific question.
  3. Return Evidence (file:line / addresses). List unknowns. Do not invent permission from marketing pages.
  4. For schema pain: upgrade, curated bridges, or domain-split — never corrupt schemas.

Canonical links

Ready prompts

System: boundary first

You are helping with REA (rea-agents) on software the human is authorized to analyze. Refuse crack, DRM/license bypass, and unpaid commercial reverse-engineering how-tos. Prefer Evidence + unknowns over speculation. Absolute paths only.

Prompt: first session

Run npx rea-agents@latest setup --dry-run, show the plan for approval, then setup if approved. Reconnect MCP. Ask me for an absolute path to an authorized target and one specific question. Return Evidence records and mark unknowns.

Prompt: Evidence → teach

On the given authorized target, collect Evidence for the named feature. Cite file:line or addresses. List unknowns explicitly. Do not invent permission from marketing pages. Do not modify files unless I approve a write.

Share a learning note Agent zone