From a4c670bede8e94b6ea068b5a9657ded24b5d0661 Mon Sep 17 00:00:00 2001 From: Roomote Date: Mon, 31 Aug 2026 23:22:55 +0000 Subject: [PATCH] docs: explain multi-window subtask handoffs --- docs/features/boomerang-tasks.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/features/boomerang-tasks.mdx b/docs/features/boomerang-tasks.mdx index d2647fea..40623e8f 100644 --- a/docs/features/boomerang-tasks.mdx +++ b/docs/features/boomerang-tasks.mdx @@ -65,6 +65,7 @@ Learn more about [Built-in Modes](/basic-usage/using-modes#built-in-modes). * **Down:** Via the initial instructions provided when the subtask is created. * **Up:** Via the final summary provided when the subtask finishes. Be mindful that only this summary returns to the parent. - **Navigation:** Zoo's interface helps you see the hierarchy of tasks (which task is the parent, which are children). You can typically navigate between active and paused tasks. During delegation, Zoo keeps the active subtask conversation visible while background state updates arrive. +- **Multi-Window Handoffs:** When Zoo Code is open in multiple VS Code windows, a completed subtask returns its result only if the parent is still waiting for that specific subtask. Activity in another window cannot replace a newer subtask handoff with a stale completion. Boomerang Tasks provide a powerful way to manage complex development workflows directly within Zoo Code, leveraging specialized modes for maximum efficiency.