Files
rea/experiments/codemode

REA Code Mode experiment

Frozen baseline: fb94d9dde0ccda83ae520ac6fb22b1d283562cf3, fetched from origin/main on 2026-10-11. Branch: experiment/codemode-bridge-20261011. This is a local experiment, not a change to the published CLI or MCP API.

The analyst question is whether composing REA's existing named tools in code improves investigation efficiency enough to justify an optional bridge. Existing users must keep their current names, input schemas, Evidence and session behavior. Provider analysis settings must stay identical between comparison profiles.

The bridge owns one upstream stdio MCP connection and discovers its complete live catalog. Only discovery and JavaScript execution are exposed downstream. Code calls tools.<original_name>(original_arguments) and receives the original MCP result envelope. REA still validates input, chooses providers, retains Evidence, and owns analysis resources. There is no second tool implementation or schema catalog to keep synchronized. A fresh QuickJS WASM context exposes only those tool calls, JSON helpers and explicit output; it has no host filesystem, network, process or module loader.

Install experimental dependencies separately with npm ci in this directory. They do not change the production package or lockfile. Use the repository's pinned Node and npm versions. No binary, provider database or raw third-party source is committed. Corpus identities and upstream download locations are in corpus.json.

Measure three baselines: normal full-catalog MCP, discovery-only MCP, and Code Mode. Count discovery, input code, intermediate results, final output, errors and retries. Report actual wall time separately from model-facing turns and local token estimates. Existing summary/page/workflow tools are fair alternatives; do not manufacture a gain by forcing full output on the direct-tool baseline. Replay measurements establish mechanism costs, not model task accuracy or inference latency. Real-agent trials must additionally verify supported facts, source identity, omissions and preserved Evidence references.

The supplied feedback is a research lead. Its Ghidra timing claim also changed auto-analysis options, so it does not isolate Code Mode's effect. Relevant primary sources: Cloudflare Code Mode, MCP patterns, Anthropic code execution, and QuickJS WASM.

Run expensive commands with python3 resource-run.py -- COMMAND ARGS... on Linux with a user systemd manager. It uses a transient scope with one CPU, a 4 GiB hard memory ceiling, a 3 GiB early-stop threshold, no swap, and a task ceiling. It refuses to start when less than 8 GiB is available and stops if host available memory drops below 4 GiB. These limits protect the host; a resource abort is a failed measurement, never a successful benchmark. Also cap Node and Java heaps.