From 351ad8282a25768a0a757b348643255b7a868910 Mon Sep 17 00:00:00 2001 From: GamerDubz Date: Tue, 13 Oct 2026 15:09:04 +0200 Subject: [PATCH 1/2] docs(plugin): check engine readiness through the connected plugin server The plugin guidance said a package-runner doctor report describes the server the plugin starts. Doctor reads the invoking shell's environment, while the plugin server inherits the client's, so the two can disagree about settings such as GHIDRA_INSTALL_DIR. Point plugin users and the bundled recovery guide at binary_session tool availability, and say what the terminal check does and does not cover. Co-Authored-By: Claude Opus 5.5 --- .../references/connection-and-recovery.md | 6 ++++-- docs/installation.md | 15 ++++++++++++--- 2 files changed, 16 insertions(+), 5 deletions(-) diff --git a/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md b/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md index 97f9cef2e..ccc13fbc7 100644 --- a/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md +++ b/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md @@ -50,8 +50,10 @@ missing tools. Instead: server if tools are still absent. The first start downloads the pinned package through `npx` and can exceed the client's startup timeout; a second start uses the cache. -- Check analysis engines with `rea doctor --provider --json`, using the - package invocation when `rea` is not on `PATH`. +- Check analysis engines through the connected server's + `binary_session.result.tool_availability`. `rea doctor --provider --json` + from a shell reports that shell's environment, which can differ from the + environment the client gave the plugin server. Use the setup repair below only when the user wants a setup-owned registration instead of the plugin, and remove or disable the plugin first. diff --git a/docs/installation.md b/docs/installation.md index afb8a42ae..c7f997226 100644 --- a/docs/installation.md +++ b/docs/installation.md @@ -817,9 +817,15 @@ only the registrations and skill locations that `rea setup` manages, so for a plugin-only install `rea doctor --client ` and `rea doctor --skill` report `missing` and recommend `rea setup`. Do not follow that remediation. Check the plugin with the client instead (`claude plugin list` and `/mcp` in Claude -Code, `codex plugin list` in Codex). A plugin does not put `rea` on your -`PATH`, so check analysis engines through the package runner, at the version -the plugin pins so the report describes the server it starts: +Code, `codex plugin list` in Codex). + +For analysis engines, ask the connected server: have the agent call +`binary_session` and read `result.tool_availability`, which reports what the +server the plugin started can use, with reasons and remediation. See +[MCP contracts](mcp-contracts.md). + +A plugin does not put `rea` on your `PATH`. To check an engine from a +terminal, use the package runner at the version the plugin pins: @@ -830,6 +836,9 @@ npx -y rea-agents@6.4.0 doctor --provider ghidra --json If your installed plugin is older, use the version in its manifest instead. +That report describes the terminal's environment, not the plugin server's. +The server inherits the client's environment, so a setting such as +`GHIDRA_INSTALL_DIR` that exists only in your terminal does not reach it. ## MCP Registry From a74d0502b909a37c80cc23cda45d2de56395dccf Mon Sep 17 00:00:00 2001 From: GamerDubz Date: Tue, 13 Oct 2026 15:16:31 +0200 Subject: [PATCH 2/2] docs(skill): use the plugin's pinned version for package-runner checks The plugin recovery section left the package-runner version to the skill's generic @latest fallback, so a doctor run could describe a newer release than the server an installed plugin starts. Tell the agent to use the version pinned in the plugin manifest. Co-Authored-By: Claude Opus 5.5 --- .../references/connection-and-recovery.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md b/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md index ccc13fbc7..35d0042c7 100644 --- a/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md +++ b/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md @@ -53,7 +53,10 @@ missing tools. Instead: - Check analysis engines through the connected server's `binary_session.result.tool_availability`. `rea doctor --provider --json` from a shell reports that shell's environment, which can differ from the - environment the client gave the plugin server. + environment the client gave the plugin server. If you still run it through + the package runner, use the version pinned in the plugin manifest's server + entry (`rea-agents@`), not `@latest`, so it matches the server the + plugin starts. Use the setup repair below only when the user wants a setup-owned registration instead of the plugin, and remove or disable the plugin first.