Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Fmarzochi merged 1 commit into from
Aug 5, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions docs/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <tool>` 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
```

---

Expand Down
Loading