From 0107a0163cf73004ee13b0ae5fd46811a273d80a Mon Sep 17 00:00:00 2001
From: marius-kilocode <marius@kilocode.ai>
Date: Thu, 28 May 2026 16:06:54 +0200
Subject: [PATCH] feat(cli): guide Agent Manager recall usage

---
 .changeset/recall-sibling-context.md                  | 5 +++++
 packages/opencode/src/kilocode/tool/agent-manager.txt | 2 ++
 2 files changed, 7 insertions(+)
 create mode 100644 .changeset/recall-sibling-context.md

diff --git a/.changeset/recall-sibling-context.md b/.changeset/recall-sibling-context.md
new file mode 100644
index 00000000000..3ecc1fb6f3d
--- /dev/null
+++ b/.changeset/recall-sibling-context.md
@@ -0,0 +1,5 @@
+---
+"@kilocode/cli": patch
+---
+
+Guide Agent Manager orchestration to recall completed session context only when needed.
diff --git a/packages/opencode/src/kilocode/tool/agent-manager.txt b/packages/opencode/src/kilocode/tool/agent-manager.txt
index d1a85145af5..3c3c59bb4b3 100644
--- a/packages/opencode/src/kilocode/tool/agent-manager.txt
+++ b/packages/opencode/src/kilocode/tool/agent-manager.txt
@@ -10,4 +10,6 @@ Each task may provide a prompt, a short display name, and a branch name. Keep di
 
 By default, multiple tasks are started as independent Agent Manager sessions. Set `versions` to true only when all tasks are alternate versions of the same work that should be compared together. Versioned worktrees are grouped in Agent Manager and branch names may receive version suffixes.
 
+If available, use `kilo_local_recall` only if you need context from a completed Agent Manager session.
+
 Do not use this for ordinary subagent research. Use the `task` tool for internal subagents, and use this only when the user wants visible Agent Manager sessions in the extension.