From ed4a1c7d95ecc5239927984fafa62e049a7d7deb Mon Sep 17 00:00:00 2001 From: Aaditya Date: Thu, 15 Oct 2026 12:37:42 +0530 Subject: [PATCH] docs(installation): list every client that first shipped in 6.5.0 (#3465) docs(installation): list every client missing from npm 6.4.0 The installation guide named only dsh, or dsh, kimi and workbuddy, as needing a newer release. The rea-agents-6.4.0 tag also lacks droid, qoder, trae and zcode, so setup against @latest rejects all seven as an unsupported agent integration. List all seven client IDs in both the registry-check note and the supported-agents table note. --- docs/installation.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/installation.md b/docs/installation.md index 39a53bb701..527014e54f 100644 --- a/docs/installation.md +++ b/docs/installation.md @@ -398,8 +398,9 @@ running server or its registration. The npm release checked on **2026-10-11** was **6.4.0**, published from [`a56f7bb6`](https://github.com/morluto/rea/commit/a56f7bb668ab23fec8d33f7af353ac7ed2fe1895). The actual registry package accepted dry-run setup plans for the 17 client IDs -in that release, including Qwen Code, Pi and Hermes. DeepSeek Harness (`dsh`) -is included from 6.5.0 and was absent from the checked npm 6.4.0 package. +in that release, including Qwen Code, Pi and Hermes. Seven client IDs are +included from 6.5.0 and were absent from the checked npm 6.4.0 package: `droid`, +`dsh`, `kimi`, `qoder`, `trae`, `workbuddy` and `zcode`. The 6.4.0 registry check does not establish 6.5.0 publication or live DeepSeek API integration. OpenCode's plan selected @@ -482,8 +483,8 @@ hosted connector; see [its configuration](client-configuration.md#other-client-s | ZCode | `zcode` | | DeepSeek Harness | `dsh` | -`dsh`, `kimi`, and `workbuddy` require a release containing them. The registry -check above does not cover them. +`droid`, `dsh`, `kimi`, `qoder`, `trae`, `workbuddy`, and `zcode` require +`rea-agents@6.5.0` or later. The 6.4.0 registry check above does not cover them. See [client configuration and troubleshooting](client-configuration.md) for configuration paths, profiles, trust policies, and schema-limit workarounds.