What people tried with REA this week (authorized demos)

Public threads this week mixed explainer energy with concrete tips. Here we keep the useful parts and drop crack framing: authorize the target first, prefer own/open/clean-room demos, and treat Evidence as the product.

Setup checklist (ops). Use Node 22+, pin a rea-agents version you trust, run setup --dry-run before writing client configs, then reconnect the MCP host. Prefer absolute paths in the first question. Tip threads circulating mid-October 2026 (e.g. checklist posts on X) align with /docs/install/.

Calculator % rewrite. Several explainers used Windows Calculator’s percent behavior (200+10% → 220 vs naive ×10%) as a teaching rewrite. That story already lives on this site as windows-calculator-percent — authorized teaching, not a retail crack.

DX-Ball / Evidence narrative. Community posts citing large Evidence suites and byte-match claims map to the existing dx-ball showcase. Read the Evidence + unknowns; do not treat social metrics as a substitute for your own verification.

Agent + Ghidra/IDA framing. “REA connects Claude/Cursor to Ghidra & IDA” is accurate only as bring-your-own engines on targets you may analyze. See Ghidra MCP with REA and /faq/legal-boundary/.

New teaching layer. For Electron/JS without native engines, start with rea-playbook (Evidence → file:line → recreate on an in-repo demo).

Sources (public). X tips/explainers from mid-October 2026 (setup checklists, calculator %, DX-Ball Evidence, Ghidra/IDA connectors). We do not deep-link every viral post; we keep lawful teaching URLs on rea.run.