Skip to content

docs(install): correct what --target zed actually does - #1206

Merged
Fmarzochi merged 1 commit into
mainfrom
docs/zed-mcp-claim
Aug 5, 2026
Merged

docs(install): correct what --target zed actually does#1206
Fmarzochi merged 1 commit into
mainfrom
docs/zed-mcp-claim

Conversation

@Fmarzochi

@Fmarzochi Fmarzochi commented Aug 5, 2026

Copy link
Copy Markdown
Owner

The false claim

docs/installation.md told the reader:

EGC registers egc-guardian and egc-memory directly into Zed's context_servers config. [...] The installer writes to ~/.config/zed/settings.json under the context_servers key.

right under egc install --target zed. That command does no such thing. scripts/lib/install-targets/zed-home.js is a flat skill-plan adapter (rootSegments: ['.config','zed']) and never touches context_servers; MCP registration lives in egc init and the shell installers.

Someone following that section ends up with skills installed, no MCP servers, and nothing telling them so.

Fix

The section now says what --target does (skills and rules only), states plainly that it does not register MCP, and points at the command that does. Found while mapping registration coverage for #1197.


Summary by cubic

Fixes the Zed install docs to state that egc install --target zed only installs skills and rules into ~/.config/zed/ and does not register MCP servers. Adds guidance to use the installer or egc init to register egc-guardian and egc-memory in Zed’s context_servers (~/.config/zed/settings.json).

Written for commit 432103b. Summary will update on new commits.

Review in cubic

The Zed section promised that 'egc install --target zed' registers egc-guardian and egc-memory into Zed's context_servers. It does not: scripts/lib/install-targets/zed-home.js is a flat skill-plan adapter, and MCP registration happens only in egc init and the shell installers. Someone following that section would end up with skills installed and no MCP servers, with nothing saying so.

Signed-off-by: Felipe Marzochi <fmarzochi@gmail.com>
@sonarqubecloud

sonarqubecloud Bot commented Aug 5, 2026

Copy link
Copy Markdown

@Fmarzochi Fmarzochi moved this from Todo to In Progress in EGC Roadmap Aug 5, 2026

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

@Fmarzochi
Fmarzochi merged commit 7bcccc1 into main Aug 5, 2026
41 checks passed
@Fmarzochi
Fmarzochi deleted the docs/zed-mcp-claim branch August 5, 2026 21:22
@github-project-automation github-project-automation Bot moved this from In Progress to Done in EGC Roadmap Aug 5, 2026
Fmarzochi added a commit that referenced this pull request Aug 6, 2026
The spec described MCP registration as part of the Tier 1 install
pipeline and, per target, as something the claude, zed and continue
targets do. None of them do: every '--target <tool>' installs skills
and rules only, and MCP registration belongs to 'egc init' and the
shell installers. This is the same false claim #1206 corrected in the
installation guide; it survived here.

The runtime map row also pointed at tests/test_orchestrator.py as its
validator, a file removed in #307. It is now listed among the honest
gaps the spec already tracks, alongside the schema's real consumers.

Signed-off-by: Felipe Marzochi <fmarzochi@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant