Answer: Worktree isolation gives a thread an isolated Git checkout: if two threads might edit the same files, start one in a new Git worktree. Worktrees are managed from the title bar via the worktree picker, and new worktrees are created in a detached HEAD state so a branch isn't accidentally shared between worktrees. Status: Overdue (check was due 2026-11-20T13:38:43Z and has not succeeded) Entry: tool/zed/agents-and-automation/worktree-isolation Revision: 2 Digest: sha256:2a44cfde6d86fefa (changes whenever the content changes) Timeline: Created: 2026-11-13T04:00:18Z Last changed: 2026-11-19T13:38:43Z (main worktree variable: — → ZED_MAIN_GIT_WORKTREE) Last verified: 2026-11-19T13:38:43Z Next check: 2026-11-20T13:38:43Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of management location | title bar | [1] | 2026-11-19 new worktree state | detached HEAD state | [1] | 2026-11-19 setup hook | create_worktree | [1] | 2026-11-19 worktree root variable | ZED_WORKTREE_ROOT | [1] | 2026-11-19 main worktree variable | ZED_MAIN_GIT_WORKTREE | [1] | 2026-11-19 cleanup behavior | moving the thread to Thread History saves the worktree's Git state and removes it from disk | [1] | 2026-11-19 Sources: [1] Zed Industries. "zed.dev/docs/ai/parallel-agents.md". https://zed.dev/docs/ai/parallel-agents.md Role: primary. Accessed: 2026-11-19T13:38:43Z Quote: "Worktrees are managed from the title bar." (Supports: management location) Quote: "New worktrees are created in a detached HEAD state, so you won't accidentally share a branch between worktrees." (Supports: new worktree state) Quote: "The `create_worktree` hook runs automatically after Zed creates a linked worktree" (Supports: setup hook) Quote: "with `ZED_WORKTREE_ROOT` pointing at the new worktree" (Supports: worktree root variable) Quote: "`ZED_MAIN_GIT_WORKTREE` pointing at the original repository." (Supports: main worktree variable) Quote: "moving the thread to Thread History saves the worktree's Git state and removes it from disk." (Supports: cleanup behavior) Snapshot SHA-256: 86ce3f4330b0771d39cc6028964ec2b00b4c1845284c8d35bef63a18beef6884 (captured 2026-11-19T13:38: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]. Cross-check: not-available at 2026-11-19T13:38:43Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:38:43Z Last attempt: 2026-11-19T13:38:43Z Notes and limitations: Extracted automatically from a single official source (section "Worktree Isolation {#worktree-isolation}"). Human-readable page: https://zed.dev/docs/ai/parallel-agents.html Related: https://latestn.com/tool/zed/agents-and-automation/zed-agent-capabilities-sources What capabilities does Zed Agent use and where is each configured? https://latestn.com/tool/zed/agents-and-automation/zed-agent-vs-other-paths How does Zed Agent differ from other agent paths in Zed? https://latestn.com/tool/zed/agents-and-automation/zed-agent-what-it-does What can Zed Agent do in a project, like editing files or running terminal commands? https://latestn.com/tool/zed/agents-and-automation/open-terminal-thread How do I open a Terminal Thread in Zed? https://latestn.com/tool/zed/agents-and-automation/start-external-agent-thread How do I start an external agent thread in Zed? https://latestn.com/tool/zed/agents-and-automation/thread-types What thread types are available in Zed and where do they run? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:38:43Z | changed | main worktree variable: — → ZED_MAIN_GIT_WORKTREE | [1] 2026-11-19T13:38:43Z | changed | worktree root variable: — → ZED_WORKTREE_ROOT | [1] 2026-11-19T13:38:43Z | changed | hook env var for original repo: ZED_MAIN_GIT_WORKTREE → — | [1] 2026-11-19T13:38:43Z | changed | hook env var for new worktree: ZED_WORKTREE_ROOT → — | [1] 2026-11-19T13:38:43Z | changed | isolation method: Git worktree → — | [1] 2026-11-13T04:00:18Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/zed/agents-and-automation/worktree-isolation/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/agents-and-automation/worktree-isolation POST: https://latestn.com/dispute/tool/zed/agents-and-automation/worktree-isolation with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/agents-and-automation/worktree-isolation?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does worktree isolation work for Zed parallel agent threads? Revision 2, last verified 2026-11-19T13:38:43Z. https://latestn.com/tool/zed/agents-and-automation/worktree-isolation (accessed 2026-11-21T09:59:03Z). @misc{LatestN_tool_zed_agents_and_automation_worktree_isolation_r2, title = {How does worktree isolation work for Zed parallel agent threads?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/agents-and-automation/worktree-isolation}}, note = {Revision 2; digest sha256:2a44cfde6d86fefa; last verified 2026-11-19T13:38:43Z; accessed 2026-11-21T09:59:03Z} } 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/agents-and-automation/worktree-isolation