When REA setup works but your investigation does not.

The agent cannot see REA

First restart the selected agent. Then run a scoped diagnostic for that client and check that its configuration path matches your active profile.

npx rea-agents@latest doctor --client codex --json

Substitute cursor or claude_code as needed. If you installed only a skill, run setup to add the MCP registration too. A workflow file teaches the agent how to investigate; it does not start a tool server.

Native analysis has no usable provider

npx rea-agents@latest providers --json
npx rea-agents@latest doctor --provider ghidra --json

Confirm that the configured provider is installed, usable on this host, and supports the target format. A native-provider failure does not prevent unrelated static JavaScript inspection. For Hopper, complete any first-run activation or demo prompt before unattended use.

Setup and the active profile disagree

Multiple client profiles can have different configuration roots. For Claude Code, a custom CLAUDE_CONFIG_DIR must be consistent across setup, diagnostics, and the running client. Check the exact reported path before making repairs.

npx rea-agents@latest setup --client claude_code --dry-run

Read the proposed edits and backup paths. Avoid deleting an entire MCP configuration to remove a single stale entry; unrelated tools may share that file.

A target returns incomplete findings

Check whether the result reports truncation, missing companion files, unsupported formats, or unresolved references. Narrow the query to one module or function. If decompiled pseudocode looks inconsistent, compare it with instructions and callers before treating it as a complete explanation.

Static inspection describes code and artifacts. Runtime capture answers a different question and can launch or interact with the target. Choose it intentionally rather than assuming it is needed for every gap.

Report a useful bug

Update the installed package or refresh your package-runner setup, restart the agent, then retry the same small task. If it still fails, record the package version, host, provider, target format, exact command, and error output.

Remove private paths and target contents before posting an issue. Include a small public reproducer when possible. Report security vulnerabilities through the project’s security process instead of a public issue.