operate-zed-agentlisted

# Operate Zed Agent Choose the Zed agent path before editing settings. Read `references/zed-surface-map.md` when the request crosses native and external agent configuration. ## Choose the Agent Path - Use Zed Agent when Zed should own the model, provider, tools, profiles, permissions, instructions, skills, and MCP configuration. - Use an External Agent when an ACP agent such as Codex, Claude, OpenCode, or Hermes should own its runtime, model, authentication, native skills, and persistent state while Zed owns the editor UI. - Use a Terminal Thread when the original CLI or TUI behavior matters more than ACP-native diffs, approvals, or session rendering. Do not apply Zed Agent Skills or profiles to an External Agent by assumption. The external agent keeps its own configuration unless its ACP implementation explicitly accepts a forwarded capability. ## Configure Zed Agent 1. Confirm the worktree is trusted before expecting project-local skills. 2. Use Zed's Skills Manager to create or import a skill when interactive management is appropriate. A GitHub URL import is an installation copy, not a remote runtime dependency. 3. Keep manually managed skills as direct children of global `~/.agents/skills/` or project `.agents/skills/`; Zed does not discover nested or arbitrary search roots. 4. Keep names and descriptions concise because Zed has a catalog budget. 5. Use `/skill` or `@skill` for explicit invocation. Use `disable-model-invocation` only when the