chore: update zed mcp config#228
Conversation
Confidence Score: 5/5The current Zed path looks mergeable, with a compatibility risk for older installations.
src/semble/installer/agents.py Reviews (1): Last reviewed commit: "chore: update zed mcp config" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
|
||
| _ZED_SERVER_CONFIG: dict[str, object] = { # Zed requires "source": "custom" for manual servers | ||
| "source": "custom", | ||
| _ZED_SERVER_CONFIG: dict[str, object] = { # Zed: command/args only, no "source" |
There was a problem hiding this comment.
When an existing installation still depends on source: "custom", reinstalling replaces the complete context_servers.semble value and removes that field. Without Zed version detection or a stated minimum version, this can make Semble disappear for users running an older compatible Zed release.
There was a problem hiding this comment.
Difficult to account for IMO. This is a two-three month old change AFAIK. So not very recent.
There was a problem hiding this comment.
Fair point — if this format change landed 2–3 months ago, the vast majority of active Zed users will be on a version that supports it already. The compatibility concern is minimal in practice. No issue here.
Tip: You can customize Greptile's behavior for this repo with .greptile/rules.md and .greptile/config.json.
Codecov Report✅ All modified and coverable lines are covered by tests.
🚀 New features to boost your workflow:
|
2 participants
The zed MCP config got changed recently. Whenever I installed
semble, I would get a warning that my settings were out of date. Zed autofixed this, so nothing broke. This PR removes our outdated format and replaces it with the newer one. I tested and installing now no longer triggers the warning toast and auto-update.