From 432103b4842dae7fa3b389427af7384be38da058 Mon Sep 17 00:00:00 2001 From: Felipe Marzochi Date: Wed, 5 Aug 2026 18:11:49 -0300 Subject: [PATCH] docs(install): correct what --target zed actually does 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 --- docs/installation.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/installation.md b/docs/installation.md index f32285184..97e5f3a9f 100644 --- a/docs/installation.md +++ b/docs/installation.md @@ -32,14 +32,18 @@ Memory is shared across EGC targets. Context saved while using Copilot is the sa ### Zed -EGC registers `egc-guardian` and `egc-memory` directly into Zed's `context_servers` config. Paths are resolved at install time so it works regardless of how EGC was installed. - ```bash npm install -g @egchq/egc egc install --target zed ``` -The installer writes to `~/.config/zed/settings.json` under the `context_servers` key. No manual JSON editing required. +This installs EGC's skills into `~/.config/zed/`. It does **not** register the MCP servers: `--target ` only ever installs skills and rules. + +To get `egc-guardian` and `egc-memory` into Zed's `context_servers`, run the installer or `egc init` instead. Both detect Zed and write to `~/.config/zed/settings.json` with paths resolved at install time: + +```bash +egc init +``` ---