GitHub issue #55200 in zed-industries/zed, opened 2026-04-29 by jakeleventhal, records a report that after uninstalling an external agent (OpenCode / opencode), Zed still opens a new agent thread with opencode selected in the agent picker, though the picker only shows Zed Agent and Codex CLI as available options, and the thread fails immediately with "Failed to Launch / Custom agent server `opencode` is not registered"; the report was filed against Zed 0.233.10 on macOS 26.5.
Verbatim Excerpts from Cited Records
“Zed still opens the new thread with `opencode` selected in the agent picker.”
·
zed-industries/zed (issue 55200 opening body, Current vs. Expected behavior section)
·
2026-04-29T12:45:44Z
·GitHub Issue ↗
“The picker only shows Zed Agent and Codex CLI as available options, but the thread is already selected as `opencode` and fails immediately with:”
·
zed-industries/zed (issue 55200 opening body, Current vs. Expected behavior section)
·
2026-04-29T12:45:44Z
·GitHub Issue ↗
“Custom agent server `opencode` is not registered”
·
zed-industries/zed (issue 55200 opening body, Current vs. Expected behavior section)
·
2026-04-29T12:45:44Z
·GitHub Issue ↗
“If a previously-selected external agent is no longer registered/installed, Zed should not keep it as the selected agent for new threads.”
·
zed-industries/zed (issue 55200 opening body, Expected behavior section)
·
2026-04-29T12:45:44Z
·GitHub Issue ↗
Counter-record: Issue closed as of the fetch (2026-11-11); 7 comments were read. jakeleventhal (2026-04-29) confirms a sqlite3 change seemed to work. nikaro (2026-05-01) reports the same symptom with mistral-vibe after removal. github-actions[bot] closed the issue for inactivity on 2026-08-28. Codex-ChoBogeun (2026-10-15) reports still being affected in the Resolve with Agent flow for Git merge conflicts and asks for reopening and for PR #55494 to be considered. smitbarmase (2026-11-11) states the original bug is fixed by #62497 since v1.18.0, confirmed on stable 1.27, and that the Resolve with Agent case is a different gap with a fix coming. No retraction of the original report appears in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #55200 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.