From c0af3e293cd85bfdece21a4e2ce2f7d25ab8e684 Mon Sep 17 00:00:00 2001 From: gensokyo-dev Date: Sat, 21 Nov 2026 17:26:47 +0000 Subject: [PATCH] docs(install): describe setup's direct-launch MCP registrations The setup summary still said setup pins package-runner registrations to the installed version. Setup records the absolute runtime and entry script instead, as the guide's MCP Registry section already explains. Fixes #10252 Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com> --- docs/getting-started/installation.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/getting-started/installation.md b/docs/getting-started/installation.md index 5ab24b42b4..2fe74c641b 100644 --- a/docs/getting-started/installation.md +++ b/docs/getting-started/installation.md @@ -217,8 +217,11 @@ instructions and references. Consumers should use `identity.skill.state`, obsolete `installed_catalog_digest` field has been removed; current catalog identity remains available at `identity.catalog`. -Setup pins package-runner MCP registrations to the exact installed REA version, -installs the matching skill and on-demand references in the same plan, and adds +Setup records MCP registrations that launch the installation performing setup +directly: its absolute JavaScript runtime and entry script, followed by `mcp` +(see [MCP Registry](#mcp-registry)). Client starts therefore run that +installation instead of resolving a package. In the same plan, setup installs +the matching skill and on-demand references and adds `startup_timeout_sec = 30` for Codex and Grok Build when no positive timeout is already configured. Codex also receives a `tool_timeout_sec` derived from known provider startup plus operation headroom.