[GH-ISSUE #1626] [Docs] Clarify that npm 6.3.0 does not include automatic Pi or Hermes setup #548

New issue

Closed

opened 2026-10-15 18:26:03 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:26:03 +00:00

Owner

Originally created by @N0zoM1z0 on GitHub (Oct 10, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/1626

Before submitting

Searched existing onboarding and release documentation reports.
Removed credentials, private paths and target data.

Documentation location

docs/installation.md#released-package-and-main and the Pi/Hermes setup sections.

Problem

The guide gives automatic Pi/Hermes setup commands and lists both clients, while its dated release checkpoint still describes 5.0.0. A first user following npx rea-agents@latest setup --client pi downloads 6.3.0 and gets VALIDATION_ERROR: Unsupported agent integration. Hermes is also absent from that release. The general main-versus-release warning does not identify this concrete onboarding boundary next to these commands.

Expected content

Document the npm checkpoint checked today and state explicitly that automatic Pi/Hermes registration requires a source build or a later release containing those integrations. Keep the source workflows documented; do not change the released client's supported-ID contract or install a development build silently.

Supporting evidence

On 2026-10-10 the npm registry reports latest 6.3.0, gitHead 74cf9e1401fcd89482fe39c27cc898f5858e9b72, bundled skill 34. One genuinely cold npm cache downloaded this package in 49 seconds. Pi registration was rejected in two independent invocations; Hermes was rejected in two. Each rejection occurred before client configuration/skill writes. The released SupportedClients catalog contains neither identifier. Candidate main at 2653b194 supports both and has passed repeated public setup and native client/MCP tests.

Additional context

Follow-up to #1587. This is a documentation/release-scope correction, not a proposal to special-case poor client behavior. Separate fresh npm setup/analysis/approval/idempotence checks are being completed with a supported released client (Codex). Other providers and native Windows remain TODO. Live DeepSeek model-provider compatibility is not established by testing DeepSeek Harness against Codex.

Originally created by @N0zoM1z0 on GitHub (Oct 10, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/1626 ### Before submitting - [x] Searched existing onboarding and release documentation reports. - [x] Removed credentials, private paths and target data. ### Documentation location `docs/installation.md#released-package-and-main` and the Pi/Hermes setup sections. ### Problem The guide gives automatic Pi/Hermes setup commands and lists both clients, while its dated release checkpoint still describes 5.0.0. A first user following `npx rea-agents@latest setup --client pi` downloads 6.3.0 and gets `VALIDATION_ERROR: Unsupported agent integration`. Hermes is also absent from that release. The general main-versus-release warning does not identify this concrete onboarding boundary next to these commands. ### Expected content Document the npm checkpoint checked today and state explicitly that automatic Pi/Hermes registration requires a source build or a later release containing those integrations. Keep the source workflows documented; do not change the released client's supported-ID contract or install a development build silently. ### Supporting evidence On 2026-10-10 the npm registry reports latest 6.3.0, gitHead `74cf9e1401fcd89482fe39c27cc898f5858e9b72`, bundled skill 34. One genuinely cold npm cache downloaded this package in 49 seconds. Pi registration was rejected in two independent invocations; Hermes was rejected in two. Each rejection occurred before client configuration/skill writes. The released SupportedClients catalog contains neither identifier. Candidate main at `2653b194` supports both and has passed repeated public setup and native client/MCP tests. ### Additional context Follow-up to #1587. This is a documentation/release-scope correction, not a proposal to special-case poor client behavior. Separate fresh npm setup/analysis/approval/idempotence checks are being completed with a supported released client (Codex). Other providers and native Windows remain TODO. Live DeepSeek model-provider compatibility is not established by testing DeepSeek Harness against Codex.

bsakaguchi

2026-10-15 18:26:03 +00:00