Answer: To attach Zed to an existing Delve instance, use `tcp_arguments` to instrument Zed's connection to Delve, specifying the host and port in a `tcp_connection` object. Zed then won't spawn a new Delve instance and will use the existing one, so there will be no terminal in Zed. Status: Overdue (check was due 2026-11-20T13:42:12Z and has not succeeded) Entry: tool/zed/troubleshooting/attach-existing-delve Revision: 1 Digest: sha256:cfb93d50d3424c68 (changes whenever the content changes) Timeline: Created: 2026-11-13T04:03:43Z Last changed: 2026-11-13T04:03:43Z Last verified: 2026-11-19T13:42:12Z Next check: 2026-11-20T13:42:12Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of configuration key | tcp_arguments | [1] | 2026-11-19 host | 127.0.0.1 | [1] | 2026-11-19 port | 53412 | [1] | 2026-11-19 adapter | Delve | [1] | 2026-11-19 request | launch | [1] | 2026-11-19 mode | exec | [1] | 2026-11-19 Sources: [1] Zed Industries. "zed.dev/docs/languages/go.md". https://zed.dev/docs/languages/go.md Role: primary. Accessed: 2026-11-19T13:42:12Z Quote: "you can use `tcp_arguments` to instrument Zed's connection to Delve" (Supports: configuration key) Quote: ""tcp_connection": { "host": "127.0.0.1", "port": 53412 }" (Supports: host, port) Quote: ""adapter": "Delve"," (Supports: adapter) Quote: ""request": "launch"," (Supports: request) Quote: ""mode": "exec"," (Supports: mode) Snapshot SHA-256: 49d9dbada0c59ae805a81b1a361faa2b107e4347f69520df65d293165ee408b4 (captured 2026-11-13T04:03:41Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T04:03:43Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T13:42:12Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:42:12Z Last attempt: 2026-11-19T13:42:12Z Notes and limitations: Extracted automatically from a single official source (section "Attaching to an existing instance of Delve"). Human-readable page: https://zed.dev/docs/languages/go.html Related: https://latestn.com/tool/zed/troubleshooting/built-in-debugger-zed How do I debug Zed itself using Zed's built-in debugger? https://latestn.com/tool/zed/troubleshooting/cargo-unstable-features-error How do I fix Cargo errors in Zed saying a dependency uses unstable features on FreeBSD? https://latestn.com/tool/zed/troubleshooting/check-fish-indent-installed How do I check that fish_indent is installed and available for Zed formatting? https://latestn.com/tool/zed/troubleshooting/agent-max-tokens-reached What does the Zed agent "Max tokens reached" error mean and how do I fix it? https://latestn.com/tool/zed/troubleshooting/async-task-profiling How do I profile async tasks in Zed and save a trace? https://latestn.com/tool/zed/troubleshooting/attach-debugger-browser-server How do I attach the Zed debugger to a server running in a web browser with npx serve? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T04:03:43Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/zed/troubleshooting/attach-existing-delve/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/zed/troubleshooting/attach-existing-delve POST: https://latestn.com/dispute/tool/zed/troubleshooting/attach-existing-delve with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/troubleshooting/attach-existing-delve?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I attach Zed to an existing Delve instance when debugging Go? Revision 1, last verified 2026-11-19T13:42:12Z. https://latestn.com/tool/zed/troubleshooting/attach-existing-delve (accessed 2026-11-21T09:57:12Z). @misc{LatestN_tool_zed_troubleshooting_attach_existing_delve_r1, title = {How do I attach Zed to an existing Delve instance when debugging Go?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/troubleshooting/attach-existing-delve}}, note = {Revision 1; digest sha256:cfb93d50d3424c68; last verified 2026-11-19T13:42:12Z; accessed 2026-11-21T09:57:12Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/zed/troubleshooting/attach-existing-delve