REA Configuration Troubleshooter

Eight reproducible setup problems

• Unclosed JSON object
• Wrong client root key
• Arguments supplied as one string
• Unsupported self-reported Node
• Direct npx Windows launcher
• Relative Ghidra installation override
• Compiler override without language
• Short Codex native tool deadline

Select an example or paste redacted configuration or error text. Choose the actual client, operating system, analysis task and optional full Node version, then diagnose locally. Each finding links to source-backed repair checks; unknown errors are explicitly left unclassified.

Example: arguments must be an array

{"mcpServers":{"rea":{"command":"npx","args":"-y [email protected] mcp"}}}

This is intentionally broken: args is one string. Put each argument in a JSON array instead. Codex uses TOML with mcp_servers, not the JSON wrapper.

What these checks establish

Baseline REA 6.5.0 and pinned installation/client sources reviewed 2026-10-18. Runtime versions and operating system are self-reported. Static JavaScript/Electron and .NET tasks do not require a native analyzer; native analysis needs actual provider readiness. Relative analyzer paths, compiler overrides without a language ID and potentially short native deadlines receive concrete checks rather than a claim that an installation was tested.

Node/npx ENOENT-like text is an executable-resolution heuristic. No machine scan, file inspection or live MCP connection takes place. Pasted text stays in the tab and is not saved or sent. Copy/download a findings report and the client-specific official setup dry-run and doctor commands; no command executes here. The report omits full pasted inputs. Unrecognized messages receive no guessed cause.

Pinned REA installation/troubleshooting · Pinned client registration source.