@@ -64,7 +64,7 @@ Learn more about [Built-in Modes](/basic-usage/using-modes#built-in-modes).
 -   **Context Isolation and Transfer:** Each subtask operates in complete isolation with its own conversation history. It does not automatically inherit the parent's context. Information must be explicitly passed:
     *   **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.
+-   **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.
 
 Boomerang Tasks provide a powerful way to manage complex development workflows directly within Zoo Code, leveraging specialized modes for maximum efficiency.
 
@@ -115,4 +115,4 @@ Adding capabilities to the Orchestrator mode should be done thoughtfully. The li
 
 [^1]: This context is passed via the `message` parameter of the [`new_task`](/advanced-usage/available-tools/new-task) tool when the Orchestrator mode delegates the task.
 [^2]: The mode for the subtask is specified via the `mode` parameter of the [`new_task`](/advanced-usage/available-tools/new-task) tool during initiation by the Orchestrator mode.
-[^3]: This summary is passed via the `result` parameter of the [`attempt_completion`](/advanced-usage/available-tools/attempt-completion) tool when the subtask finishes.
+[^3]: This summary is passed via the `result` parameter of the [`attempt_completion`](/advanced-usage/available-tools/attempt-completion) tool when the subtask finishes.