How do I move a Zed context server without confusing ACP configuration?
A settings move can preserve Zed Agent’s remote definition while leaving an external agent unaffected. Relocate Montage’s context server only within its actual owner, and recheck account association rather than exporting consent or declaring every agent in the editor migrated. The move concerns an editor-owned context server only. Preserve destination settings and inspect its supported consent behavior without exporting source-machine storage or assuming that external agents inherit the editor’s connection automatically.
Help me move a Zed context server without confusing ACP configuration. Read context_servers.montage and identify the editor environment using it. Obtain signals_status in the destination Zed Agent conversation. No writes.Inventory the source entry
Read context_servers.montage and identify the editor environment using it. Separate the remote address from private auth storage and unrelated agent settings before planning the move. The move inventory should separate the hosted URL from user-owned authorization and from external-agent setup that happens to share the same editor window.
Inspect destination settings
Review existing destination context servers before merging the Montage URL. Preserve other tools and resolve a naming collision rather than overwriting a server with a similar display name. An existing destination entry may be deliberate; compare its purpose before replacing anything based on a matching server name or familiar logo.
Retain editor-owned remote intent
Use the documented context_servers URL shape for Zed Agent. Do not replace it with an external ACP agent’s native schema or assume that agent inherits the editor entry. The documented destination artifact is an editor context server, not an ACP wrapper or a shell command intended to launch another assistant.
Review destination authentication
Follow the destination editor’s supported standard OAuth prompt where applicable. Moving settings does not authorize transferring a browser session or relying on another user’s consent. The absence of a manually supplied Authorization header is relevant to the standard Zed OAuth route, not evidence that every account is already authorized.
Validate only the moved surface
Obtain signals_status in the destination Zed Agent conversation. Record that editor-owned result and leave external ACP or terminal callers unverified unless they receive their own configuration and authorized check. Keep the new editor’s result separate from the old environment, and do not claim that relocating settings revoked source-machine access or migrated external agents.
Keep the boundaries clear.
- The documented destination artifact is an editor context server, not an ACP wrapper or a shell command intended to launch another assistant.
- Keep the new editor’s result separate from the old environment, and do not claim that relocating settings revoked source-machine access or migrated external agents.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.