@within-7/minto 0.4.1 → 0.4.2

package/dist/tools/TaskTool/prompt.js

@@ -1,12 +1,16 @@
 import { getTools, getReadOnlyTools } from "../../tools.js";
-import { TaskTool } from "./TaskTool.js";
-import { FileWriteTool } from "../FileWriteTool/FileWriteTool.js";
-import { GlobTool } from "../GlobTool/GlobTool.js";
-import { FileReadTool } from "../FileReadTool/FileReadTool.js";
 import { getActiveAgents } from "../../utils/agentLoader.js";
+const EXCLUDED_AGENT_TOOLS = /* @__PURE__ */ new Set([
+  "Agent",
+  // Prevent recursive TaskTool calls (unless explicitly allowed via toolFilter)
+  "TeamCreate",
+  // Team management is leader-only
+  "TeamDelete"
+  // Team management is leader-only
+]);
 async function getTaskTools(safeMode) {
   return (await (!safeMode ? getTools() : getReadOnlyTools())).filter(
-    (_) => _.name !== TaskTool.name
+    (_) => !EXCLUDED_AGENT_TOOLS.has(_.name)
   );
 }
 async function getPrompt(safeMode) {
@@ -15,100 +19,100 @@ async function getPrompt(safeMode) {
     const toolsStr = Array.isArray(agent.tools) ? agent.tools.join(", ") : "*";
     return `- ${agent.agentType}: ${agent.whenToUse} (Tools: ${toolsStr})`;
   }).join("\n");
-  return `Launch a new agent to handle complex, multi-step tasks autonomously. 
+  return `Launch a new agent to handle complex, multi-step tasks autonomously.
+
+The Agent tool launches specialized agents (subprocesses) that autonomously handle complex tasks. Each agent type has specific capabilities and tools available to it.
 
 Available agent types and the tools they have access to:
 ${agentDescriptions}
 
-When using the Task tool, you must specify a subagent_type parameter to select which agent type to use.
+When using the Agent tool, specify a subagent_type parameter to select which agent type to use. If omitted, the general-purpose agent is used.
 
-\u{1F6A8} CRITICAL: You MUST use the EXACT agent type name from the list above. Common mistakes to avoid:
+When to use the Agent tool:
+- When you are instructed to execute custom slash commands. Use the Agent tool with the slash command invocation as the entire prompt. The slash command can take arguments. For example: Agent(description="Check the file", prompt="/check-file path/to/file.py")
 
-NAMING FORMAT:
-- \u2705 ALWAYS use hyphens (-): "strategic-market-analyzer", "business-analyst", "qa-engineer"
-- \u274C NEVER use underscores (_): "strategic_market_analyzer", "business_analyst"
-- \u274C NEVER use spaces: "strategic market analyzer", "business analyst"
-- \u274C NEVER invent names: "researcher", "analyst", "data_analyst"
+When NOT to use the Agent tool:
+- If you want to read a specific file path, use the Read or Glob tool instead of the Agent tool, to find the match more quickly
+- If you are searching for a specific class definition like "class Foo", use the Glob tool instead, to find the match more quickly
+- If you are searching for code within a specific file or set of 2-3 files, use the Read tool instead of the Agent tool, to find the match more quickly
+- Other tasks that are not related to the agent descriptions above
 
-SELECTION RULES:
-1. For market/business analysis \u2192 use "strategic-market-analyzer" or "business-analyst"
-2. For data analysis \u2192 use "data-scientist"
-3. For general tasks \u2192 use "general-purpose"
-4. For code/QA tasks \u2192 use "qa-engineer" or "code-reviewer"
+## Parallel Tasks vs Agent Teams \u2014 Decision Framework
 
-If unsure, use "general-purpose" - it has access to all tools.
+**USER INTENT OVERRIDE: If the user explicitly asks for a team, swarm, or multi-agent group, ALWAYS use Agent Teams regardless of the heuristics below.**
 
-When to use the Agent tool:
-- When you are instructed to execute custom slash commands. Use the Agent tool with the slash command invocation as the entire prompt. The slash command can take arguments. For example: Task(description="Check the file", prompt="/check-file path/to/file.py")
+You have TWO ways to run multiple agents. Choose the right one:
 
-When NOT to use the Agent tool:
-- If you want to read a specific file path, use the ${FileReadTool.name} or ${GlobTool.name} tool instead of the Agent tool, to find the match more quickly
-- If you are searching for a specific class definition like "class Foo", use the ${GlobTool.name} tool instead, to find the match more quickly
-- If you are searching for code within a specific file or set of 2-3 files, use the ${FileReadTool.name} tool instead of the Agent tool, to find the match more quickly
-- Other tasks that are not related to the agent descriptions above
+### Parallel Tasks (multiple Agent calls in one message) \u2014 DEFAULT CHOICE
+Use when tasks are **independent and fire-and-forget**:
+- Each agent works alone, returns a result, and is done
+- No agent needs to see another agent's output to do its work
+- You (the orchestrator) synthesize all results after they return
+
+Examples: analyze 3 files, search 5 code patterns, run independent checks
+
+### Agent Teams (TeamCreate + SendMessage) \u2014 for collaboration or user-requested teams
+Use when agents **must communicate with each other** during execution, or when the user explicitly requests a team:
+- Agent A's output feeds into Agent B's work (and B may send findings back to A)
+- Agents need a shared task board to coordinate who does what
+- The work requires multiple rounds of back-and-forth between agents
+- Agents need to persist across rounds and be reassigned new tasks
+
+**Important**: Teammates in a team automatically run in background, so you (the team-lead) remain available to process messages and coordinate work.
+
+Examples: researcher finds info \u2192 implementer codes it \u2192 tester validates \u2192 implementer fixes issues
+
+### Decision Checklist
+Ask yourself: "Did the user ask for a team, OR do agents need to TALK TO EACH OTHER?"
+- **User asked for a team** \u2192 Use Agent Teams (always honor explicit requests)
+- **No communication needed** \u2192 Use parallel Agent calls (simple, fast, no overhead)
+- **Agents must communicate** \u2192 Use Agent Teams (TeamCreate + spawn teammates + SendMessage)
+
+**Efficiency tip:** For independent tasks, parallel Agent calls are simpler and faster. But always defer to user intent \u2014 if they ask for a team, create one.
 
 Usage notes:
 - Always include a short description (3-5 words) summarizing what the agent will do
 - Launch multiple agents concurrently whenever possible, to maximize performance; to do that, use a single message with multiple tool uses
 - When the agent is done, it will return a single message back to you. The result returned by the agent is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result.
-- You can optionally run agents in the background using the run_in_background parameter. When an agent runs in the background, the tool result will include an output_file path. To check on the agent's progress or retrieve its results, use the Read tool to read the output file, or use Bash with \`tail\` to see recent output. You can continue working while background agents run.
+- **Foreground tasks return results directly** \u2014 when a foreground Agent (including parallel Agents) completes, its result and agentId are returned inline in the tool result. Do NOT call TaskOutput for foreground tasks; their results are already in your context. TaskOutput is ONLY for background tasks started with \`run_in_background: true\`.
+- You can optionally run agents in the background using the run_in_background parameter. When an agent runs in the background, you will be automatically notified when it completes \u2014 do NOT sleep, poll, or proactively check on its progress. Continue with other work or respond to the user instead.
+- **Foreground vs background**: Use foreground (default) when you need the agent's results before you can proceed \u2014 e.g., research agents whose findings inform your next steps. Use background when you have genuinely independent work to do in parallel.
+- When using Agent Teams (TeamCreate), teammates automatically run in background so you remain available to coordinate. After spawning all teammates, respond to the user with a brief status (e.g., "Agents are working...") and STOP \u2014 do NOT manually read files, check inboxes, or use TaskOutput. Teammate results are delivered to you automatically as new messages.
 - Agents can be resumed using the \`resume\` parameter by passing the agent ID from a previous invocation. When resumed, the agent continues with its full previous context preserved. When NOT resuming, each invocation starts fresh and you should provide a detailed task description with all necessary context.
 - When the agent is done, it will return a single message back to you along with its agent ID. You can use this ID to resume the agent later if needed for follow-up work.
 - Provide clear, detailed prompts so the agent can work autonomously and return exactly the information you need.
-- Agents with "access to current context" can see the full conversation history before the tool call. When using these agents, you can write concise prompts that reference earlier context (e.g., "investigate the error discussed above") instead of repeating information. The agent will receive all prior messages and understand the context.
 - The agent's outputs should generally be trusted
 - Clearly tell the agent whether you expect it to write code or just to do research (search, file reads, web fetches, etc.), since it is not aware of the user's intent
 - If the agent description mentions that it should be used proactively, then you should try your best to use it without the user having to ask for it first. Use your judgement.
-- If the user specifies that they want you to run agents "in parallel", you MUST send a single message with multiple Task tool use content blocks.
+- If the user specifies that they want you to run agents "in parallel", you MUST send a single message with multiple Agent tool use content blocks.
 
 Example usage:
 
 <example>
-<scenario>Market research analysis with multiple files</scenario>
-user: "Analyze these 3 market research reports and summarize findings"
-assistant: I'll use multiple subagents to analyze the reports in parallel.
-<uses Task tool>
-subagent_type: "strategic-market-analyzer"
-prompt: "Analyze market_report_1.md and provide key insights..."
-</uses Task tool>
-<uses Task tool>
-subagent_type: "strategic-market-analyzer"
-prompt: "Analyze market_report_2.md and provide key insights..."
-</uses Task tool>
-<uses Task tool>
-subagent_type: "business-analyst"
-prompt: "Analyze financial_report.md and provide key insights..."
-</uses Task tool>
-</example>
-
-<example>
-<scenario>Code review after implementation</scenario>
 user: "Please write a function that checks if a number is prime"
-assistant: First let me use the ${FileWriteTool.name} tool to write the function
-<writes code>
-assistant: Now let me use the code-reviewer agent to review the code
-<uses Task tool>
-subagent_type: "code-reviewer"
-prompt: "Review the isPrime function in utils.js for correctness and performance"
-</uses Task tool>
+assistant: I'm going to use the Write tool to write the following code:
+<code>
+function isPrime(n) {
+  if (n <= 1) return false
+  for (let i = 2; i * i <= n; i++) {
+    if (n % i === 0) return false
+  }
+  return true
+}
+</code>
+<commentary>
+Since a significant piece of code was written and the task was completed, now use the test-runner agent to run the tests
+</commentary>
+assistant: Uses the Agent tool to launch the test-runner agent
 </example>
 
 <example>
-<scenario>Data analysis task</scenario>
-user: "Analyze the CSV data in sales.csv and find trends"
-assistant: I'll use the data-scientist agent to analyze this data
-<uses Task tool>
-subagent_type: "data-scientist"
-prompt: "Analyze sales.csv and identify trends, patterns, and anomalies"
-</uses Task tool>
-</example>
-
-\u274C WRONG EXAMPLES (DO NOT DO THIS):
-<wrong_example>
-subagent_type: "researcher"  \u2190 WRONG! This agent type doesn't exist
-subagent_type: "market_analyzer"  \u2190 WRONG! Uses underscore instead of hyphen
-subagent_type: "data analyst"  \u2190 WRONG! Uses space instead of hyphen
-</wrong_example>`;
+user: "Hello"
+<commentary>
+Since the user is greeting, use the greeting-responder agent to respond with a friendly joke
+</commentary>
+assistant: "I'm going to use the Agent tool to launch the greeting-responder agent"
+</example>`;
 }
 export {
   getPrompt,

package/dist/tools/TaskTool/prompt.js.map

@@ -1,7 +1,7 @@
 {
   "version": 3,
   "sources": ["../../../src/tools/TaskTool/prompt.ts"],
-  "sourcesContent": ["import { type Tool } from '@tool'\nimport { getTools, getReadOnlyTools } from '@tools'\nimport { TaskTool } from './TaskTool'\nimport { BashTool } from '@tools/BashTool/BashTool'\nimport { FileWriteTool } from '@tools/FileWriteTool/FileWriteTool'\nimport { FileEditTool } from '@tools/FileEditTool/FileEditTool'\nimport { NotebookEditTool } from '@tools/NotebookEditTool/NotebookEditTool'\nimport { GlobTool } from '@tools/GlobTool/GlobTool'\nimport { FileReadTool } from '@tools/FileReadTool/FileReadTool'\nimport { getModelManager } from '@utils/model'\nimport { getActiveAgents } from '@utils/agentLoader'\n\nexport async function getTaskTools(safeMode: boolean): Promise<Tool[]> {\n  // No recursive tasks, yet..\n  return (await (!safeMode ? getTools() : getReadOnlyTools())).filter(\n    _ => _.name !== TaskTool.name,\n  )\n}\n\nexport async function getPrompt(safeMode: boolean): Promise<string> {\n  const agents = await getActiveAgents()\n\n  // Format: (Tools: tool1, tool2)\n  const agentDescriptions = agents\n    .map(agent => {\n      const toolsStr = Array.isArray(agent.tools) ? agent.tools.join(', ') : '*'\n      return `- ${agent.agentType}: ${agent.whenToUse} (Tools: ${toolsStr})`\n    })\n    .join('\\n')\n\n  return `Launch a new agent to handle complex, multi-step tasks autonomously. \n\nAvailable agent types and the tools they have access to:\n${agentDescriptions}\n\nWhen using the Task tool, you must specify a subagent_type parameter to select which agent type to use.\n\n\uD83D\uDEA8 CRITICAL: You MUST use the EXACT agent type name from the list above. Common mistakes to avoid:\n\nNAMING FORMAT:\n- \u2705 ALWAYS use hyphens (-): \"strategic-market-analyzer\", \"business-analyst\", \"qa-engineer\"\n- \u274C NEVER use underscores (_): \"strategic_market_analyzer\", \"business_analyst\"\n- \u274C NEVER use spaces: \"strategic market analyzer\", \"business analyst\"\n- \u274C NEVER invent names: \"researcher\", \"analyst\", \"data_analyst\"\n\nSELECTION RULES:\n1. For market/business analysis \u2192 use \"strategic-market-analyzer\" or \"business-analyst\"\n2. For data analysis \u2192 use \"data-scientist\"\n3. For general tasks \u2192 use \"general-purpose\"\n4. For code/QA tasks \u2192 use \"qa-engineer\" or \"code-reviewer\"\n\nIf unsure, use \"general-purpose\" - it has access to all tools.\n\nWhen to use the Agent tool:\n- When you are instructed to execute custom slash commands. Use the Agent tool with the slash command invocation as the entire prompt. The slash command can take arguments. For example: Task(description=\"Check the file\", prompt=\"/check-file path/to/file.py\")\n\nWhen NOT to use the Agent tool:\n- If you want to read a specific file path, use the ${FileReadTool.name} or ${GlobTool.name} tool instead of the Agent tool, to find the match more quickly\n- If you are searching for a specific class definition like \"class Foo\", use the ${GlobTool.name} tool instead, to find the match more quickly\n- If you are searching for code within a specific file or set of 2-3 files, use the ${FileReadTool.name} tool instead of the Agent tool, to find the match more quickly\n- Other tasks that are not related to the agent descriptions above\n\nUsage notes:\n- Always include a short description (3-5 words) summarizing what the agent will do\n- Launch multiple agents concurrently whenever possible, to maximize performance; to do that, use a single message with multiple tool uses\n- When the agent is done, it will return a single message back to you. The result returned by the agent is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result.\n- You can optionally run agents in the background using the run_in_background parameter. When an agent runs in the background, the tool result will include an output_file path. To check on the agent's progress or retrieve its results, use the Read tool to read the output file, or use Bash with \\`tail\\` to see recent output. You can continue working while background agents run.\n- Agents can be resumed using the \\`resume\\` parameter by passing the agent ID from a previous invocation. When resumed, the agent continues with its full previous context preserved. When NOT resuming, each invocation starts fresh and you should provide a detailed task description with all necessary context.\n- When the agent is done, it will return a single message back to you along with its agent ID. You can use this ID to resume the agent later if needed for follow-up work.\n- Provide clear, detailed prompts so the agent can work autonomously and return exactly the information you need.\n- Agents with \"access to current context\" can see the full conversation history before the tool call. When using these agents, you can write concise prompts that reference earlier context (e.g., \"investigate the error discussed above\") instead of repeating information. The agent will receive all prior messages and understand the context.\n- The agent's outputs should generally be trusted\n- Clearly tell the agent whether you expect it to write code or just to do research (search, file reads, web fetches, etc.), since it is not aware of the user's intent\n- If the agent description mentions that it should be used proactively, then you should try your best to use it without the user having to ask for it first. Use your judgement.\n- If the user specifies that they want you to run agents \"in parallel\", you MUST send a single message with multiple Task tool use content blocks.\n\nExample usage:\n\n<example>\n<scenario>Market research analysis with multiple files</scenario>\nuser: \"Analyze these 3 market research reports and summarize findings\"\nassistant: I'll use multiple subagents to analyze the reports in parallel.\n<uses Task tool>\nsubagent_type: \"strategic-market-analyzer\"\nprompt: \"Analyze market_report_1.md and provide key insights...\"\n</uses Task tool>\n<uses Task tool>\nsubagent_type: \"strategic-market-analyzer\"\nprompt: \"Analyze market_report_2.md and provide key insights...\"\n</uses Task tool>\n<uses Task tool>\nsubagent_type: \"business-analyst\"\nprompt: \"Analyze financial_report.md and provide key insights...\"\n</uses Task tool>\n</example>\n\n<example>\n<scenario>Code review after implementation</scenario>\nuser: \"Please write a function that checks if a number is prime\"\nassistant: First let me use the ${FileWriteTool.name} tool to write the function\n<writes code>\nassistant: Now let me use the code-reviewer agent to review the code\n<uses Task tool>\nsubagent_type: \"code-reviewer\"\nprompt: \"Review the isPrime function in utils.js for correctness and performance\"\n</uses Task tool>\n</example>\n\n<example>\n<scenario>Data analysis task</scenario>\nuser: \"Analyze the CSV data in sales.csv and find trends\"\nassistant: I'll use the data-scientist agent to analyze this data\n<uses Task tool>\nsubagent_type: \"data-scientist\"\nprompt: \"Analyze sales.csv and identify trends, patterns, and anomalies\"\n</uses Task tool>\n</example>\n\n\u274C WRONG EXAMPLES (DO NOT DO THIS):\n<wrong_example>\nsubagent_type: \"researcher\"  \u2190 WRONG! This agent type doesn't exist\nsubagent_type: \"market_analyzer\"  \u2190 WRONG! Uses underscore instead of hyphen\nsubagent_type: \"data analyst\"  \u2190 WRONG! Uses space instead of hyphen\n</wrong_example>`\n}\n"],
-  "mappings": "AACA,SAAS,UAAU,wBAAwB;AAC3C,SAAS,gBAAgB;AAEzB,SAAS,qBAAqB;AAG9B,SAAS,gBAAgB;AACzB,SAAS,oBAAoB;AAE7B,SAAS,uBAAuB;AAEhC,eAAsB,aAAa,UAAoC;AAErE,UAAQ,OAAO,CAAC,WAAW,SAAS,IAAI,iBAAiB,IAAI;AAAA,IAC3D,OAAK,EAAE,SAAS,SAAS;AAAA,EAC3B;AACF;AAEA,eAAsB,UAAU,UAAoC;AAClE,QAAM,SAAS,MAAM,gBAAgB;AAGrC,QAAM,oBAAoB,OACvB,IAAI,WAAS;AACZ,UAAM,WAAW,MAAM,QAAQ,MAAM,KAAK,IAAI,MAAM,MAAM,KAAK,IAAI,IAAI;AACvE,WAAO,KAAK,MAAM,SAAS,KAAK,MAAM,SAAS,YAAY,QAAQ;AAAA,EACrE,CAAC,EACA,KAAK,IAAI;AAEZ,SAAO;AAAA;AAAA;AAAA,EAGP,iBAAiB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,sDAwBmC,aAAa,IAAI,OAAO,SAAS,IAAI;AAAA,mFACR,SAAS,IAAI;AAAA,sFACV,aAAa,IAAI;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,kCAwCrE,cAAc,IAAI;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAyBpD;",
+  "sourcesContent": ["import { type Tool } from '@tool'\nimport { getTools, getReadOnlyTools } from '@tools'\nimport { TaskTool } from './TaskTool'\nimport { getModelManager } from '@utils/model'\nimport { getActiveAgents } from '@utils/agentLoader'\n\n/**\n * Agent-internal tools that should never be exposed to subagents.\n * These are either recursive (TaskTool itself) or admin-only.\n */\nconst EXCLUDED_AGENT_TOOLS = new Set([\n  'Agent', // Prevent recursive TaskTool calls (unless explicitly allowed via toolFilter)\n  'TeamCreate', // Team management is leader-only\n  'TeamDelete', // Team management is leader-only\n])\n\nexport async function getTaskTools(safeMode: boolean): Promise<Tool[]> {\n  return (await (!safeMode ? getTools() : getReadOnlyTools())).filter(\n    _ => !EXCLUDED_AGENT_TOOLS.has(_.name),\n  )\n}\n\nexport async function getPrompt(safeMode: boolean): Promise<string> {\n  const agents = await getActiveAgents()\n\n  // Format: (Tools: tool1, tool2)\n  const agentDescriptions = agents\n    .map(agent => {\n      const toolsStr = Array.isArray(agent.tools) ? agent.tools.join(', ') : '*'\n      return `- ${agent.agentType}: ${agent.whenToUse} (Tools: ${toolsStr})`\n    })\n    .join('\\n')\n\n  return `Launch a new agent to handle complex, multi-step tasks autonomously.\n\nThe Agent tool launches specialized agents (subprocesses) that autonomously handle complex tasks. Each agent type has specific capabilities and tools available to it.\n\nAvailable agent types and the tools they have access to:\n${agentDescriptions}\n\nWhen using the Agent tool, specify a subagent_type parameter to select which agent type to use. If omitted, the general-purpose agent is used.\n\nWhen to use the Agent tool:\n- When you are instructed to execute custom slash commands. Use the Agent tool with the slash command invocation as the entire prompt. The slash command can take arguments. For example: Agent(description=\"Check the file\", prompt=\"/check-file path/to/file.py\")\n\nWhen NOT to use the Agent tool:\n- If you want to read a specific file path, use the Read or Glob tool instead of the Agent tool, to find the match more quickly\n- If you are searching for a specific class definition like \"class Foo\", use the Glob tool instead, to find the match more quickly\n- If you are searching for code within a specific file or set of 2-3 files, use the Read tool instead of the Agent tool, to find the match more quickly\n- Other tasks that are not related to the agent descriptions above\n\n## Parallel Tasks vs Agent Teams \u2014 Decision Framework\n\n**USER INTENT OVERRIDE: If the user explicitly asks for a team, swarm, or multi-agent group, ALWAYS use Agent Teams regardless of the heuristics below.**\n\nYou have TWO ways to run multiple agents. Choose the right one:\n\n### Parallel Tasks (multiple Agent calls in one message) \u2014 DEFAULT CHOICE\nUse when tasks are **independent and fire-and-forget**:\n- Each agent works alone, returns a result, and is done\n- No agent needs to see another agent's output to do its work\n- You (the orchestrator) synthesize all results after they return\n\nExamples: analyze 3 files, search 5 code patterns, run independent checks\n\n### Agent Teams (TeamCreate + SendMessage) \u2014 for collaboration or user-requested teams\nUse when agents **must communicate with each other** during execution, or when the user explicitly requests a team:\n- Agent A's output feeds into Agent B's work (and B may send findings back to A)\n- Agents need a shared task board to coordinate who does what\n- The work requires multiple rounds of back-and-forth between agents\n- Agents need to persist across rounds and be reassigned new tasks\n\n**Important**: Teammates in a team automatically run in background, so you (the team-lead) remain available to process messages and coordinate work.\n\nExamples: researcher finds info \u2192 implementer codes it \u2192 tester validates \u2192 implementer fixes issues\n\n### Decision Checklist\nAsk yourself: \"Did the user ask for a team, OR do agents need to TALK TO EACH OTHER?\"\n- **User asked for a team** \u2192 Use Agent Teams (always honor explicit requests)\n- **No communication needed** \u2192 Use parallel Agent calls (simple, fast, no overhead)\n- **Agents must communicate** \u2192 Use Agent Teams (TeamCreate + spawn teammates + SendMessage)\n\n**Efficiency tip:** For independent tasks, parallel Agent calls are simpler and faster. But always defer to user intent \u2014 if they ask for a team, create one.\n\nUsage notes:\n- Always include a short description (3-5 words) summarizing what the agent will do\n- Launch multiple agents concurrently whenever possible, to maximize performance; to do that, use a single message with multiple tool uses\n- When the agent is done, it will return a single message back to you. The result returned by the agent is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result.\n- **Foreground tasks return results directly** \u2014 when a foreground Agent (including parallel Agents) completes, its result and agentId are returned inline in the tool result. Do NOT call TaskOutput for foreground tasks; their results are already in your context. TaskOutput is ONLY for background tasks started with \\`run_in_background: true\\`.\n- You can optionally run agents in the background using the run_in_background parameter. When an agent runs in the background, you will be automatically notified when it completes \u2014 do NOT sleep, poll, or proactively check on its progress. Continue with other work or respond to the user instead.\n- **Foreground vs background**: Use foreground (default) when you need the agent's results before you can proceed \u2014 e.g., research agents whose findings inform your next steps. Use background when you have genuinely independent work to do in parallel.\n- When using Agent Teams (TeamCreate), teammates automatically run in background so you remain available to coordinate. After spawning all teammates, respond to the user with a brief status (e.g., \"Agents are working...\") and STOP \u2014 do NOT manually read files, check inboxes, or use TaskOutput. Teammate results are delivered to you automatically as new messages.\n- Agents can be resumed using the \\`resume\\` parameter by passing the agent ID from a previous invocation. When resumed, the agent continues with its full previous context preserved. When NOT resuming, each invocation starts fresh and you should provide a detailed task description with all necessary context.\n- When the agent is done, it will return a single message back to you along with its agent ID. You can use this ID to resume the agent later if needed for follow-up work.\n- Provide clear, detailed prompts so the agent can work autonomously and return exactly the information you need.\n- The agent's outputs should generally be trusted\n- Clearly tell the agent whether you expect it to write code or just to do research (search, file reads, web fetches, etc.), since it is not aware of the user's intent\n- If the agent description mentions that it should be used proactively, then you should try your best to use it without the user having to ask for it first. Use your judgement.\n- If the user specifies that they want you to run agents \"in parallel\", you MUST send a single message with multiple Agent tool use content blocks.\n\nExample usage:\n\n<example>\nuser: \"Please write a function that checks if a number is prime\"\nassistant: I'm going to use the Write tool to write the following code:\n<code>\nfunction isPrime(n) {\n  if (n <= 1) return false\n  for (let i = 2; i * i <= n; i++) {\n    if (n % i === 0) return false\n  }\n  return true\n}\n</code>\n<commentary>\nSince a significant piece of code was written and the task was completed, now use the test-runner agent to run the tests\n</commentary>\nassistant: Uses the Agent tool to launch the test-runner agent\n</example>\n\n<example>\nuser: \"Hello\"\n<commentary>\nSince the user is greeting, use the greeting-responder agent to respond with a friendly joke\n</commentary>\nassistant: \"I'm going to use the Agent tool to launch the greeting-responder agent\"\n</example>`\n}\n"],
+  "mappings": "AACA,SAAS,UAAU,wBAAwB;AAG3C,SAAS,uBAAuB;AAMhC,MAAM,uBAAuB,oBAAI,IAAI;AAAA,EACnC;AAAA;AAAA,EACA;AAAA;AAAA,EACA;AAAA;AACF,CAAC;AAED,eAAsB,aAAa,UAAoC;AACrE,UAAQ,OAAO,CAAC,WAAW,SAAS,IAAI,iBAAiB,IAAI;AAAA,IAC3D,OAAK,CAAC,qBAAqB,IAAI,EAAE,IAAI;AAAA,EACvC;AACF;AAEA,eAAsB,UAAU,UAAoC;AAClE,QAAM,SAAS,MAAM,gBAAgB;AAGrC,QAAM,oBAAoB,OACvB,IAAI,WAAS;AACZ,UAAM,WAAW,MAAM,QAAQ,MAAM,KAAK,IAAI,MAAM,MAAM,KAAK,IAAI,IAAI;AACvE,WAAO,KAAK,MAAM,SAAS,KAAK,MAAM,SAAS,YAAY,QAAQ;AAAA,EACrE,CAAC,EACA,KAAK,IAAI;AAEZ,SAAO;AAAA;AAAA;AAAA;AAAA;AAAA,EAKP,iBAAiB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAyFnB;",
   "names": []
 }

package/dist/tools/TaskUpdateTool/TaskUpdateTool.js

@@ -89,7 +89,7 @@ const TaskUpdateTool = {
   async *call(input) {
     try {
       const isDeleting = input.status === "deleted";
-      const task = updateTask({
+      const task = await updateTask({
         taskId: input.taskId,
         status: input.status,
         subject: input.subject,
@@ -108,6 +108,20 @@ const TaskUpdateTool = {
         };
         return;
       }
+      if (task.metadata?._hookRejected) {
+        const feedback = task.metadata._hookFeedback || "Blocked by hook";
+        yield {
+          type: "result",
+          data: {
+            taskId: task.id,
+            status: task.status,
+            hookBlocked: true,
+            hookFeedback: feedback
+          },
+          resultForAssistant: `Task #${task.id} completion was blocked by a hook. Status reverted to in_progress. Feedback: ${feedback}`
+        };
+        return;
+      }
       const result = {
         taskId: task.id,
         status: task.status,

package/dist/tools/TaskUpdateTool/TaskUpdateTool.js.map

@@ -1,7 +1,7 @@
 {
   "version": 3,
   "sources": ["../../../src/tools/TaskUpdateTool/TaskUpdateTool.tsx"],
-  "sourcesContent": ["import { Box, Text } from 'ink'\nimport * as React from 'react'\nimport { z } from 'zod'\nimport { FallbackToolUseRejectedMessage } from '@components/FallbackToolUseRejectedMessage'\nimport { Tool } from '@tool'\nimport { updateTask, getTaskById } from '@services/taskStore'\nimport { DESCRIPTION, PROMPT } from './prompt'\nimport { getTheme } from '@utils/theme'\n\nconst inputSchema = z.strictObject({\n  taskId: z.string().describe('The ID of the task to update'),\n  status: z\n    .enum(['pending', 'in_progress', 'completed', 'deleted'])\n    .optional()\n    .describe('New status for the task'),\n  subject: z.string().optional().describe('New subject for the task'),\n  description: z.string().optional().describe('New description for the task'),\n  activeForm: z\n    .string()\n    .optional()\n    .describe(\n      'Present continuous form shown in spinner when in_progress (e.g., \"Running tests\")',\n    ),\n  owner: z.string().optional().describe('New owner for the task'),\n  metadata: z\n    .record(z.unknown())\n    .optional()\n    .describe(\n      'Metadata keys to merge into the task. Set a key to null to delete it.',\n    ),\n  addBlocks: z\n    .array(z.string())\n    .optional()\n    .describe('Task IDs that this task blocks'),\n  addBlockedBy: z\n    .array(z.string())\n    .optional()\n    .describe('Task IDs that block this task'),\n})\n\nexport const TaskUpdateTool = {\n  name: 'TaskUpdate',\n  async description() {\n    return DESCRIPTION\n  },\n  async prompt() {\n    return PROMPT\n  },\n  inputSchema,\n  userFacingName() {\n    return 'Update Task'\n  },\n  async isEnabled() {\n    return true\n  },\n  isReadOnly() {\n    return false\n  },\n  isConcurrencySafe() {\n    return false\n  },\n  needsPermissions() {\n    return false\n  },\n  renderToolUseMessage(input: z.infer<typeof inputSchema>) {\n    const parts: string[] = [`taskId: ${input.taskId}`]\n    if (input.status) {\n      parts.push(`status: ${input.status}`)\n    }\n    return parts.join(', ')\n  },\n  renderToolUseRejectedMessage() {\n    return <FallbackToolUseRejectedMessage />\n  },\n  renderToolResultMessage(output: {\n    taskId: string\n    status?: string\n    deleted?: boolean\n  }) {\n    if (!output || !output.taskId) {\n      return (\n        <Box flexDirection=\"row\">\n          <Text>&nbsp;&nbsp;\u23BF &nbsp;</Text>\n          <Text>Task updated</Text>\n        </Box>\n      )\n    }\n\n    if (output.deleted) {\n      return (\n        <Box flexDirection=\"row\">\n          <Text>&nbsp;&nbsp;\u23BF &nbsp;</Text>\n          <Text color={getTheme().secondaryText}>\n            Task #{output.taskId} deleted\n          </Text>\n        </Box>\n      )\n    }\n\n    const statusColor =\n      output.status === 'completed'\n        ? getTheme().success\n        : output.status === 'in_progress'\n          ? getTheme().warning\n          : getTheme().secondaryText\n\n    return (\n      <Box flexDirection=\"row\">\n        <Text>&nbsp;&nbsp;\u23BF &nbsp;</Text>\n        <Text>\n          Updated task #{output.taskId}\n          {output.status && <Text color={statusColor}> \u2192 {output.status}</Text>}\n        </Text>\n      </Box>\n    )\n  },\n  renderResultForAssistant(result: {\n    taskId: string\n    status?: string\n    deleted?: boolean\n  }) {\n    if (result.deleted) {\n      return `Task #${result.taskId} has been deleted`\n    }\n    return `Updated task #${result.taskId}${result.status ? ` status` : ''}`\n  },\n  async validateInput({ taskId }: z.infer<typeof inputSchema>) {\n    if (!taskId?.trim()) {\n      return {\n        result: false,\n        message: 'Task ID is required',\n      }\n    }\n\n    const task = getTaskById(taskId)\n    if (!task) {\n      return {\n        result: false,\n        message: `Task with ID '${taskId}' not found`,\n      }\n    }\n\n    return { result: true }\n  },\n  async *call(input: z.infer<typeof inputSchema>) {\n    try {\n      const isDeleting = input.status === 'deleted'\n\n      const task = updateTask({\n        taskId: input.taskId,\n        status: input.status,\n        subject: input.subject,\n        description: input.description,\n        activeForm: input.activeForm,\n        owner: input.owner,\n        metadata: input.metadata,\n        addBlocks: input.addBlocks,\n        addBlockedBy: input.addBlockedBy,\n      })\n\n      if (!task) {\n        yield {\n          type: 'result',\n          data: { error: 'Task not found' },\n          resultForAssistant: `Error: Task with ID '${input.taskId}' not found`,\n        }\n        return\n      }\n\n      const result = {\n        taskId: task.id,\n        status: task.status,\n        deleted: isDeleting,\n      }\n\n      yield {\n        type: 'result',\n        data: result,\n        resultForAssistant: this.renderResultForAssistant(result),\n      }\n    } catch (error) {\n      const errorMessage =\n        error instanceof Error ? error.message : 'Unknown error occurred'\n      yield {\n        type: 'result',\n        data: { error: errorMessage },\n        resultForAssistant: `Error updating task: ${errorMessage}`,\n      }\n    }\n  },\n} satisfies Tool\n"],
-  "mappings": "AAAA,SAAS,KAAK,YAAY;AAC1B,YAAY,WAAW;AACvB,SAAS,SAAS;AAClB,SAAS,sCAAsC;AAE/C,SAAS,YAAY,mBAAmB;AACxC,SAAS,aAAa,cAAc;AACpC,SAAS,gBAAgB;AAEzB,MAAM,cAAc,EAAE,aAAa;AAAA,EACjC,QAAQ,EAAE,OAAO,EAAE,SAAS,8BAA8B;AAAA,EAC1D,QAAQ,EACL,KAAK,CAAC,WAAW,eAAe,aAAa,SAAS,CAAC,EACvD,SAAS,EACT,SAAS,yBAAyB;AAAA,EACrC,SAAS,EAAE,OAAO,EAAE,SAAS,EAAE,SAAS,0BAA0B;AAAA,EAClE,aAAa,EAAE,OAAO,EAAE,SAAS,EAAE,SAAS,8BAA8B;AAAA,EAC1E,YAAY,EACT,OAAO,EACP,SAAS,EACT;AAAA,IACC;AAAA,EACF;AAAA,EACF,OAAO,EAAE,OAAO,EAAE,SAAS,EAAE,SAAS,wBAAwB;AAAA,EAC9D,UAAU,EACP,OAAO,EAAE,QAAQ,CAAC,EAClB,SAAS,EACT;AAAA,IACC;AAAA,EACF;AAAA,EACF,WAAW,EACR,MAAM,EAAE,OAAO,CAAC,EAChB,SAAS,EACT,SAAS,gCAAgC;AAAA,EAC5C,cAAc,EACX,MAAM,EAAE,OAAO,CAAC,EAChB,SAAS,EACT,SAAS,+BAA+B;AAC7C,CAAC;AAEM,MAAM,iBAAiB;AAAA,EAC5B,MAAM;AAAA,EACN,MAAM,cAAc;AAClB,WAAO;AAAA,EACT;AAAA,EACA,MAAM,SAAS;AACb,WAAO;AAAA,EACT;AAAA,EACA;AAAA,EACA,iBAAiB;AACf,WAAO;AAAA,EACT;AAAA,EACA,MAAM,YAAY;AAChB,WAAO;AAAA,EACT;AAAA,EACA,aAAa;AACX,WAAO;AAAA,EACT;AAAA,EACA,oBAAoB;AAClB,WAAO;AAAA,EACT;AAAA,EACA,mBAAmB;AACjB,WAAO;AAAA,EACT;AAAA,EACA,qBAAqB,OAAoC;AACvD,UAAM,QAAkB,CAAC,WAAW,MAAM,MAAM,EAAE;AAClD,QAAI,MAAM,QAAQ;AAChB,YAAM,KAAK,WAAW,MAAM,MAAM,EAAE;AAAA,IACtC;AACA,WAAO,MAAM,KAAK,IAAI;AAAA,EACxB;AAAA,EACA,+BAA+B;AAC7B,WAAO,oCAAC,oCAA+B;AAAA,EACzC;AAAA,EACA,wBAAwB,QAIrB;AACD,QAAI,CAAC,UAAU,CAAC,OAAO,QAAQ;AAC7B,aACE,oCAAC,OAAI,eAAc,SACjB,oCAAC,YAAK,qBAAoB,GAC1B,oCAAC,YAAK,cAAY,CACpB;AAAA,IAEJ;AAEA,QAAI,OAAO,SAAS;AAClB,aACE,oCAAC,OAAI,eAAc,SACjB,oCAAC,YAAK,qBAAoB,GAC1B,oCAAC,QAAK,OAAO,SAAS,EAAE,iBAAe,UAC9B,OAAO,QAAO,UACvB,CACF;AAAA,IAEJ;AAEA,UAAM,cACJ,OAAO,WAAW,cACd,SAAS,EAAE,UACX,OAAO,WAAW,gBAChB,SAAS,EAAE,UACX,SAAS,EAAE;AAEnB,WACE,oCAAC,OAAI,eAAc,SACjB,oCAAC,YAAK,qBAAoB,GAC1B,oCAAC,YAAK,kBACW,OAAO,QACrB,OAAO,UAAU,oCAAC,QAAK,OAAO,eAAa,YAAI,OAAO,MAAO,CAChE,CACF;AAAA,EAEJ;AAAA,EACA,yBAAyB,QAItB;AACD,QAAI,OAAO,SAAS;AAClB,aAAO,SAAS,OAAO,MAAM;AAAA,IAC/B;AACA,WAAO,iBAAiB,OAAO,MAAM,GAAG,OAAO,SAAS,YAAY,EAAE;AAAA,EACxE;AAAA,EACA,MAAM,cAAc,EAAE,OAAO,GAAgC;AAC3D,QAAI,CAAC,QAAQ,KAAK,GAAG;AACnB,aAAO;AAAA,QACL,QAAQ;AAAA,QACR,SAAS;AAAA,MACX;AAAA,IACF;AAEA,UAAM,OAAO,YAAY,MAAM;AAC/B,QAAI,CAAC,MAAM;AACT,aAAO;AAAA,QACL,QAAQ;AAAA,QACR,SAAS,iBAAiB,MAAM;AAAA,MAClC;AAAA,IACF;AAEA,WAAO,EAAE,QAAQ,KAAK;AAAA,EACxB;AAAA,EACA,OAAO,KAAK,OAAoC;AAC9C,QAAI;AACF,YAAM,aAAa,MAAM,WAAW;AAEpC,YAAM,OAAO,WAAW;AAAA,QACtB,QAAQ,MAAM;AAAA,QACd,QAAQ,MAAM;AAAA,QACd,SAAS,MAAM;AAAA,QACf,aAAa,MAAM;AAAA,QACnB,YAAY,MAAM;AAAA,QAClB,OAAO,MAAM;AAAA,QACb,UAAU,MAAM;AAAA,QAChB,WAAW,MAAM;AAAA,QACjB,cAAc,MAAM;AAAA,MACtB,CAAC;AAED,UAAI,CAAC,MAAM;AACT,cAAM;AAAA,UACJ,MAAM;AAAA,UACN,MAAM,EAAE,OAAO,iBAAiB;AAAA,UAChC,oBAAoB,wBAAwB,MAAM,MAAM;AAAA,QAC1D;AACA;AAAA,MACF;AAEA,YAAM,SAAS;AAAA,QACb,QAAQ,KAAK;AAAA,QACb,QAAQ,KAAK;AAAA,QACb,SAAS;AAAA,MACX;AAEA,YAAM;AAAA,QACJ,MAAM;AAAA,QACN,MAAM;AAAA,QACN,oBAAoB,KAAK,yBAAyB,MAAM;AAAA,MAC1D;AAAA,IACF,SAAS,OAAO;AACd,YAAM,eACJ,iBAAiB,QAAQ,MAAM,UAAU;AAC3C,YAAM;AAAA,QACJ,MAAM;AAAA,QACN,MAAM,EAAE,OAAO,aAAa;AAAA,QAC5B,oBAAoB,wBAAwB,YAAY;AAAA,MAC1D;AAAA,IACF;AAAA,EACF;AACF;",
+  "sourcesContent": ["import { Box, Text } from 'ink'\nimport * as React from 'react'\nimport { z } from 'zod'\nimport { FallbackToolUseRejectedMessage } from '@components/FallbackToolUseRejectedMessage'\nimport { Tool } from '@tool'\nimport { updateTask, getTaskById } from '@services/taskStore'\nimport { DESCRIPTION, PROMPT } from './prompt'\nimport { getTheme } from '@utils/theme'\n\nconst inputSchema = z.strictObject({\n  taskId: z.string().describe('The ID of the task to update'),\n  status: z\n    .enum(['pending', 'in_progress', 'completed', 'deleted'])\n    .optional()\n    .describe('New status for the task'),\n  subject: z.string().optional().describe('New subject for the task'),\n  description: z.string().optional().describe('New description for the task'),\n  activeForm: z\n    .string()\n    .optional()\n    .describe(\n      'Present continuous form shown in spinner when in_progress (e.g., \"Running tests\")',\n    ),\n  owner: z.string().optional().describe('New owner for the task'),\n  metadata: z\n    .record(z.unknown())\n    .optional()\n    .describe(\n      'Metadata keys to merge into the task. Set a key to null to delete it.',\n    ),\n  addBlocks: z\n    .array(z.string())\n    .optional()\n    .describe('Task IDs that this task blocks'),\n  addBlockedBy: z\n    .array(z.string())\n    .optional()\n    .describe('Task IDs that block this task'),\n})\n\nexport const TaskUpdateTool = {\n  name: 'TaskUpdate',\n  async description() {\n    return DESCRIPTION\n  },\n  async prompt() {\n    return PROMPT\n  },\n  inputSchema,\n  userFacingName() {\n    return 'Update Task'\n  },\n  async isEnabled() {\n    return true\n  },\n  isReadOnly() {\n    return false\n  },\n  isConcurrencySafe() {\n    return false\n  },\n  needsPermissions() {\n    return false\n  },\n  renderToolUseMessage(input: z.infer<typeof inputSchema>) {\n    const parts: string[] = [`taskId: ${input.taskId}`]\n    if (input.status) {\n      parts.push(`status: ${input.status}`)\n    }\n    return parts.join(', ')\n  },\n  renderToolUseRejectedMessage() {\n    return <FallbackToolUseRejectedMessage />\n  },\n  renderToolResultMessage(output: {\n    taskId: string\n    status?: string\n    deleted?: boolean\n  }) {\n    if (!output || !output.taskId) {\n      return (\n        <Box flexDirection=\"row\">\n          <Text>&nbsp;&nbsp;\u23BF &nbsp;</Text>\n          <Text>Task updated</Text>\n        </Box>\n      )\n    }\n\n    if (output.deleted) {\n      return (\n        <Box flexDirection=\"row\">\n          <Text>&nbsp;&nbsp;\u23BF &nbsp;</Text>\n          <Text color={getTheme().secondaryText}>\n            Task #{output.taskId} deleted\n          </Text>\n        </Box>\n      )\n    }\n\n    const statusColor =\n      output.status === 'completed'\n        ? getTheme().success\n        : output.status === 'in_progress'\n          ? getTheme().warning\n          : getTheme().secondaryText\n\n    return (\n      <Box flexDirection=\"row\">\n        <Text>&nbsp;&nbsp;\u23BF &nbsp;</Text>\n        <Text>\n          Updated task #{output.taskId}\n          {output.status && <Text color={statusColor}> \u2192 {output.status}</Text>}\n        </Text>\n      </Box>\n    )\n  },\n  renderResultForAssistant(result: {\n    taskId: string\n    status?: string\n    deleted?: boolean\n  }) {\n    if (result.deleted) {\n      return `Task #${result.taskId} has been deleted`\n    }\n    return `Updated task #${result.taskId}${result.status ? ` status` : ''}`\n  },\n  async validateInput({ taskId }: z.infer<typeof inputSchema>) {\n    if (!taskId?.trim()) {\n      return {\n        result: false,\n        message: 'Task ID is required',\n      }\n    }\n\n    const task = getTaskById(taskId)\n    if (!task) {\n      return {\n        result: false,\n        message: `Task with ID '${taskId}' not found`,\n      }\n    }\n\n    return { result: true }\n  },\n  async *call(input: z.infer<typeof inputSchema>) {\n    try {\n      const isDeleting = input.status === 'deleted'\n\n      const task = await updateTask({\n        taskId: input.taskId,\n        status: input.status,\n        subject: input.subject,\n        description: input.description,\n        activeForm: input.activeForm,\n        owner: input.owner,\n        metadata: input.metadata,\n        addBlocks: input.addBlocks,\n        addBlockedBy: input.addBlockedBy,\n      })\n\n      if (!task) {\n        yield {\n          type: 'result',\n          data: { error: 'Task not found' },\n          resultForAssistant: `Error: Task with ID '${input.taskId}' not found`,\n        }\n        return\n      }\n\n      // Check if hook blocked task completion\n      if (task.metadata?._hookRejected) {\n        const feedback = task.metadata._hookFeedback || 'Blocked by hook'\n        yield {\n          type: 'result',\n          data: {\n            taskId: task.id,\n            status: task.status,\n            hookBlocked: true,\n            hookFeedback: feedback,\n          },\n          resultForAssistant: `Task #${task.id} completion was blocked by a hook. Status reverted to in_progress. Feedback: ${feedback}`,\n        }\n        return\n      }\n\n      const result = {\n        taskId: task.id,\n        status: task.status,\n        deleted: isDeleting,\n      }\n\n      yield {\n        type: 'result',\n        data: result,\n        resultForAssistant: this.renderResultForAssistant(result),\n      }\n    } catch (error) {\n      const errorMessage =\n        error instanceof Error ? error.message : 'Unknown error occurred'\n      yield {\n        type: 'result',\n        data: { error: errorMessage },\n        resultForAssistant: `Error updating task: ${errorMessage}`,\n      }\n    }\n  },\n} satisfies Tool\n"],
+  "mappings": "AAAA,SAAS,KAAK,YAAY;AAC1B,YAAY,WAAW;AACvB,SAAS,SAAS;AAClB,SAAS,sCAAsC;AAE/C,SAAS,YAAY,mBAAmB;AACxC,SAAS,aAAa,cAAc;AACpC,SAAS,gBAAgB;AAEzB,MAAM,cAAc,EAAE,aAAa;AAAA,EACjC,QAAQ,EAAE,OAAO,EAAE,SAAS,8BAA8B;AAAA,EAC1D,QAAQ,EACL,KAAK,CAAC,WAAW,eAAe,aAAa,SAAS,CAAC,EACvD,SAAS,EACT,SAAS,yBAAyB;AAAA,EACrC,SAAS,EAAE,OAAO,EAAE,SAAS,EAAE,SAAS,0BAA0B;AAAA,EAClE,aAAa,EAAE,OAAO,EAAE,SAAS,EAAE,SAAS,8BAA8B;AAAA,EAC1E,YAAY,EACT,OAAO,EACP,SAAS,EACT;AAAA,IACC;AAAA,EACF;AAAA,EACF,OAAO,EAAE,OAAO,EAAE,SAAS,EAAE,SAAS,wBAAwB;AAAA,EAC9D,UAAU,EACP,OAAO,EAAE,QAAQ,CAAC,EAClB,SAAS,EACT;AAAA,IACC;AAAA,EACF;AAAA,EACF,WAAW,EACR,MAAM,EAAE,OAAO,CAAC,EAChB,SAAS,EACT,SAAS,gCAAgC;AAAA,EAC5C,cAAc,EACX,MAAM,EAAE,OAAO,CAAC,EAChB,SAAS,EACT,SAAS,+BAA+B;AAC7C,CAAC;AAEM,MAAM,iBAAiB;AAAA,EAC5B,MAAM;AAAA,EACN,MAAM,cAAc;AAClB,WAAO;AAAA,EACT;AAAA,EACA,MAAM,SAAS;AACb,WAAO;AAAA,EACT;AAAA,EACA;AAAA,EACA,iBAAiB;AACf,WAAO;AAAA,EACT;AAAA,EACA,MAAM,YAAY;AAChB,WAAO;AAAA,EACT;AAAA,EACA,aAAa;AACX,WAAO;AAAA,EACT;AAAA,EACA,oBAAoB;AAClB,WAAO;AAAA,EACT;AAAA,EACA,mBAAmB;AACjB,WAAO;AAAA,EACT;AAAA,EACA,qBAAqB,OAAoC;AACvD,UAAM,QAAkB,CAAC,WAAW,MAAM,MAAM,EAAE;AAClD,QAAI,MAAM,QAAQ;AAChB,YAAM,KAAK,WAAW,MAAM,MAAM,EAAE;AAAA,IACtC;AACA,WAAO,MAAM,KAAK,IAAI;AAAA,EACxB;AAAA,EACA,+BAA+B;AAC7B,WAAO,oCAAC,oCAA+B;AAAA,EACzC;AAAA,EACA,wBAAwB,QAIrB;AACD,QAAI,CAAC,UAAU,CAAC,OAAO,QAAQ;AAC7B,aACE,oCAAC,OAAI,eAAc,SACjB,oCAAC,YAAK,qBAAoB,GAC1B,oCAAC,YAAK,cAAY,CACpB;AAAA,IAEJ;AAEA,QAAI,OAAO,SAAS;AAClB,aACE,oCAAC,OAAI,eAAc,SACjB,oCAAC,YAAK,qBAAoB,GAC1B,oCAAC,QAAK,OAAO,SAAS,EAAE,iBAAe,UAC9B,OAAO,QAAO,UACvB,CACF;AAAA,IAEJ;AAEA,UAAM,cACJ,OAAO,WAAW,cACd,SAAS,EAAE,UACX,OAAO,WAAW,gBAChB,SAAS,EAAE,UACX,SAAS,EAAE;AAEnB,WACE,oCAAC,OAAI,eAAc,SACjB,oCAAC,YAAK,qBAAoB,GAC1B,oCAAC,YAAK,kBACW,OAAO,QACrB,OAAO,UAAU,oCAAC,QAAK,OAAO,eAAa,YAAI,OAAO,MAAO,CAChE,CACF;AAAA,EAEJ;AAAA,EACA,yBAAyB,QAItB;AACD,QAAI,OAAO,SAAS;AAClB,aAAO,SAAS,OAAO,MAAM;AAAA,IAC/B;AACA,WAAO,iBAAiB,OAAO,MAAM,GAAG,OAAO,SAAS,YAAY,EAAE;AAAA,EACxE;AAAA,EACA,MAAM,cAAc,EAAE,OAAO,GAAgC;AAC3D,QAAI,CAAC,QAAQ,KAAK,GAAG;AACnB,aAAO;AAAA,QACL,QAAQ;AAAA,QACR,SAAS;AAAA,MACX;AAAA,IACF;AAEA,UAAM,OAAO,YAAY,MAAM;AAC/B,QAAI,CAAC,MAAM;AACT,aAAO;AAAA,QACL,QAAQ;AAAA,QACR,SAAS,iBAAiB,MAAM;AAAA,MAClC;AAAA,IACF;AAEA,WAAO,EAAE,QAAQ,KAAK;AAAA,EACxB;AAAA,EACA,OAAO,KAAK,OAAoC;AAC9C,QAAI;AACF,YAAM,aAAa,MAAM,WAAW;AAEpC,YAAM,OAAO,MAAM,WAAW;AAAA,QAC5B,QAAQ,MAAM;AAAA,QACd,QAAQ,MAAM;AAAA,QACd,SAAS,MAAM;AAAA,QACf,aAAa,MAAM;AAAA,QACnB,YAAY,MAAM;AAAA,QAClB,OAAO,MAAM;AAAA,QACb,UAAU,MAAM;AAAA,QAChB,WAAW,MAAM;AAAA,QACjB,cAAc,MAAM;AAAA,MACtB,CAAC;AAED,UAAI,CAAC,MAAM;AACT,cAAM;AAAA,UACJ,MAAM;AAAA,UACN,MAAM,EAAE,OAAO,iBAAiB;AAAA,UAChC,oBAAoB,wBAAwB,MAAM,MAAM;AAAA,QAC1D;AACA;AAAA,MACF;AAGA,UAAI,KAAK,UAAU,eAAe;AAChC,cAAM,WAAW,KAAK,SAAS,iBAAiB;AAChD,cAAM;AAAA,UACJ,MAAM;AAAA,UACN,MAAM;AAAA,YACJ,QAAQ,KAAK;AAAA,YACb,QAAQ,KAAK;AAAA,YACb,aAAa;AAAA,YACb,cAAc;AAAA,UAChB;AAAA,UACA,oBAAoB,SAAS,KAAK,EAAE,gFAAgF,QAAQ;AAAA,QAC9H;AACA;AAAA,MACF;AAEA,YAAM,SAAS;AAAA,QACb,QAAQ,KAAK;AAAA,QACb,QAAQ,KAAK;AAAA,QACb,SAAS;AAAA,MACX;AAEA,YAAM;AAAA,QACJ,MAAM;AAAA,QACN,MAAM;AAAA,QACN,oBAAoB,KAAK,yBAAyB,MAAM;AAAA,MAC1D;AAAA,IACF,SAAS,OAAO;AACd,YAAM,eACJ,iBAAiB,QAAQ,MAAM,UAAU;AAC3C,YAAM;AAAA,QACJ,MAAM;AAAA,QACN,MAAM,EAAE,OAAO,aAAa;AAAA,QAC5B,oBAAoB,wBAAwB,YAAY;AAAA,MAC1D;AAAA,IACF;AAAA,EACF;AACF;",
   "names": []
 }

package/dist/tools/TeamCreateTool/TeamCreateTool.js

@@ -0,0 +1,129 @@
+import { Box, Text } from "ink";
+import * as React from "react";
+import { z } from "zod";
+import { FallbackToolUseRejectedMessage } from "../../components/FallbackToolUseRejectedMessage.js";
+import { createToolErrorResult } from "../../utils/tooling/toolError.js";
+import {
+  isAgentTeamsEnabled,
+  sanitizeTeamName,
+  createTeam,
+  addTeammate
+} from "../../services/agentTeams/index.js";
+import { DESCRIPTION, PROMPT } from "./prompt.js";
+import { getTheme } from "../../utils/theme.js";
+const inputSchema = z.strictObject({
+  team_name: z.string().describe("Name for the new team to create."),
+  description: z.string().optional().describe("Team description/purpose."),
+  agent_type: z.string().optional().describe(
+    'Type/role of the team lead (e.g., "researcher", "test-runner"). Used for team file and inter-agent coordination.'
+  )
+});
+const TeamCreateTool = {
+  name: "TeamCreate",
+  async description() {
+    return DESCRIPTION;
+  },
+  async prompt() {
+    return PROMPT;
+  },
+  inputSchema,
+  userFacingName() {
+    return "Create Team";
+  },
+  async isEnabled() {
+    return isAgentTeamsEnabled();
+  },
+  isReadOnly() {
+    return false;
+  },
+  isConcurrencySafe() {
+    return false;
+  },
+  needsPermissions() {
+    return false;
+  },
+  renderToolUseMessage(input) {
+    return `"${input.team_name || ""}"`;
+  },
+  renderToolUseRejectedMessage() {
+    return /* @__PURE__ */ React.createElement(FallbackToolUseRejectedMessage, null);
+  },
+  renderToolResultMessage(output) {
+    if (!output || !output.team_name) {
+      return /* @__PURE__ */ React.createElement(Box, { flexDirection: "row" }, /* @__PURE__ */ React.createElement(Text, null, "\xA0\xA0\u23BF \xA0"), /* @__PURE__ */ React.createElement(Text, null, "Team created"));
+    }
+    return /* @__PURE__ */ React.createElement(Box, { flexDirection: "row" }, /* @__PURE__ */ React.createElement(Text, null, "\xA0\xA0\u23BF \xA0"), /* @__PURE__ */ React.createElement(Text, { color: getTheme().success }, 'Team "', output.team_name, '" created'));
+  },
+  renderResultForAssistant(result) {
+    if (result.error) {
+      return `Error creating team: ${result.error}`;
+    }
+    return `Team "${result.team_name}" created successfully.
+team_name: ${result.team_name}
+team_file_path: ${result.team_file_path}
+lead_agent_id: ${result.lead_agent_id}
+
+## Next Steps (REQUIRED):
+1. Create tasks with TaskCreate for each unit of work
+2. Spawn teammates with Task tool (team_name="${result.team_name}", name="<agent-name>") \u2014 launch in parallel
+3. Wait for agents to complete (they send idle notifications automatically)
+4. Collect results and summarize for the user
+5. Send shutdown_request to each agent via SendMessage
+6. Call TeamDelete to clean up
+
+IMPORTANT: You MUST actually spawn teammates using the Task tool now. Do NOT just tell the user you spawned them \u2014 call the Task tool with team_name and name parameters.
+
+CRITICAL: After presenting your final answer, you MUST send shutdown_request to ALL teammates, then call TeamDelete. Skipping cleanup leaves a broken team panel visible to the user.`;
+  },
+  async validateInput({ team_name }) {
+    if (!team_name?.trim()) {
+      return {
+        result: false,
+        message: "Team name cannot be empty"
+      };
+    }
+    const sanitized = sanitizeTeamName(team_name);
+    if (!sanitized || !/[a-z0-9]/.test(sanitized)) {
+      return {
+        result: false,
+        message: "Team name must contain at least one alphanumeric character"
+      };
+    }
+    return { result: true };
+  },
+  async *call(input) {
+    try {
+      const sanitizedName = sanitizeTeamName(input.team_name);
+      const team = createTeam({
+        name: sanitizedName,
+        displayMode: "auto",
+        maxTeammates: 10,
+        description: input.description
+      });
+      addTeammate(team.name, {
+        id: `team-lead@${team.name}`,
+        name: "team-lead",
+        agentType: input.agent_type || "leader",
+        status: "idle",
+        prompt: "",
+        color: "white"
+      });
+      const result = {
+        team_name: team.name,
+        team_file_path: `~/.minto/teams/${team.name}/config.json`,
+        lead_agent_id: `team-lead@${team.name}`
+      };
+      yield {
+        type: "result",
+        data: result,
+        resultForAssistant: this.renderResultForAssistant(result)
+      };
+    } catch (error) {
+      yield createToolErrorResult(error, "Error creating team");
+    }
+  }
+};
+export {
+  TeamCreateTool
+};
+//# sourceMappingURL=TeamCreateTool.js.map

package/dist/tools/TeamCreateTool/TeamCreateTool.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/tools/TeamCreateTool/TeamCreateTool.tsx"],
+  "sourcesContent": ["import { Box, Text } from 'ink'\nimport * as React from 'react'\nimport { z } from 'zod'\nimport { FallbackToolUseRejectedMessage } from '@components/FallbackToolUseRejectedMessage'\nimport { Tool } from '@tool'\nimport { createToolErrorResult } from '@utils/tooling/toolError'\nimport {\n  isAgentTeamsEnabled,\n  sanitizeTeamName,\n  createTeam,\n  addTeammate,\n} from '@services/agentTeams'\nimport { DESCRIPTION, PROMPT } from './prompt'\nimport { getTheme } from '@utils/theme'\n\nconst inputSchema = z.strictObject({\n  team_name: z.string().describe('Name for the new team to create.'),\n  description: z.string().optional().describe('Team description/purpose.'),\n  agent_type: z\n    .string()\n    .optional()\n    .describe(\n      'Type/role of the team lead (e.g., \"researcher\", \"test-runner\"). Used for team file and inter-agent coordination.',\n    ),\n})\n\nexport const TeamCreateTool = {\n  name: 'TeamCreate',\n  async description() {\n    return DESCRIPTION\n  },\n  async prompt() {\n    return PROMPT\n  },\n  inputSchema,\n  userFacingName() {\n    return 'Create Team'\n  },\n  async isEnabled() {\n    return isAgentTeamsEnabled()\n  },\n  isReadOnly() {\n    return false\n  },\n  isConcurrencySafe() {\n    return false\n  },\n  needsPermissions() {\n    return false\n  },\n  renderToolUseMessage(input: z.infer<typeof inputSchema>) {\n    return `\"${input.team_name || ''}\"`\n  },\n  renderToolUseRejectedMessage() {\n    return <FallbackToolUseRejectedMessage />\n  },\n  renderToolResultMessage(output: {\n    team_name: string\n    team_file_path: string\n  }) {\n    if (!output || !output.team_name) {\n      return (\n        <Box flexDirection=\"row\">\n          <Text>&nbsp;&nbsp;\u23BF &nbsp;</Text>\n          <Text>Team created</Text>\n        </Box>\n      )\n    }\n\n    return (\n      <Box flexDirection=\"row\">\n        <Text>&nbsp;&nbsp;\u23BF &nbsp;</Text>\n        <Text color={getTheme().success}>\n          Team &quot;{output.team_name}&quot; created\n        </Text>\n      </Box>\n    )\n  },\n  renderResultForAssistant(result: {\n    team_name?: string\n    team_file_path?: string\n    lead_agent_id?: string\n    error?: string\n  }) {\n    if (result.error) {\n      return `Error creating team: ${result.error}`\n    }\n    return `Team \"${result.team_name}\" created successfully.\nteam_name: ${result.team_name}\nteam_file_path: ${result.team_file_path}\nlead_agent_id: ${result.lead_agent_id}\n\n## Next Steps (REQUIRED):\n1. Create tasks with TaskCreate for each unit of work\n2. Spawn teammates with Task tool (team_name=\"${result.team_name}\", name=\"<agent-name>\") \u2014 launch in parallel\n3. Wait for agents to complete (they send idle notifications automatically)\n4. Collect results and summarize for the user\n5. Send shutdown_request to each agent via SendMessage\n6. Call TeamDelete to clean up\n\nIMPORTANT: You MUST actually spawn teammates using the Task tool now. Do NOT just tell the user you spawned them \u2014 call the Task tool with team_name and name parameters.\n\nCRITICAL: After presenting your final answer, you MUST send shutdown_request to ALL teammates, then call TeamDelete. Skipping cleanup leaves a broken team panel visible to the user.`\n  },\n  async validateInput({ team_name }: z.infer<typeof inputSchema>) {\n    if (!team_name?.trim()) {\n      return {\n        result: false as const,\n        message: 'Team name cannot be empty',\n      }\n    }\n    const sanitized = sanitizeTeamName(team_name)\n    if (!sanitized || !/[a-z0-9]/.test(sanitized)) {\n      return {\n        result: false as const,\n        message: 'Team name must contain at least one alphanumeric character',\n      }\n    }\n    return { result: true as const }\n  },\n  async *call(input: z.infer<typeof inputSchema>) {\n    try {\n      const sanitizedName = sanitizeTeamName(input.team_name)\n      const team = createTeam({\n        name: sanitizedName,\n        displayMode: 'auto',\n        maxTeammates: 10,\n        description: input.description,\n      })\n\n      // Register team-lead as initial member so it appears in the panel\n      addTeammate(team.name, {\n        id: `team-lead@${team.name}`,\n        name: 'team-lead',\n        agentType: input.agent_type || 'leader',\n        status: 'idle',\n        prompt: '',\n        color: 'white',\n      })\n\n      const result = {\n        team_name: team.name,\n        team_file_path: `~/.minto/teams/${team.name}/config.json`,\n        lead_agent_id: `team-lead@${team.name}`,\n      }\n\n      yield {\n        type: 'result' as const,\n        data: result,\n        resultForAssistant: this.renderResultForAssistant(result),\n      }\n    } catch (error) {\n      yield createToolErrorResult(error, 'Error creating team')\n    }\n  },\n} satisfies Tool\n"],
+  "mappings": "AAAA,SAAS,KAAK,YAAY;AAC1B,YAAY,WAAW;AACvB,SAAS,SAAS;AAClB,SAAS,sCAAsC;AAE/C,SAAS,6BAA6B;AACtC;AAAA,EACE;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,OACK;AACP,SAAS,aAAa,cAAc;AACpC,SAAS,gBAAgB;AAEzB,MAAM,cAAc,EAAE,aAAa;AAAA,EACjC,WAAW,EAAE,OAAO,EAAE,SAAS,kCAAkC;AAAA,EACjE,aAAa,EAAE,OAAO,EAAE,SAAS,EAAE,SAAS,2BAA2B;AAAA,EACvE,YAAY,EACT,OAAO,EACP,SAAS,EACT;AAAA,IACC;AAAA,EACF;AACJ,CAAC;AAEM,MAAM,iBAAiB;AAAA,EAC5B,MAAM;AAAA,EACN,MAAM,cAAc;AAClB,WAAO;AAAA,EACT;AAAA,EACA,MAAM,SAAS;AACb,WAAO;AAAA,EACT;AAAA,EACA;AAAA,EACA,iBAAiB;AACf,WAAO;AAAA,EACT;AAAA,EACA,MAAM,YAAY;AAChB,WAAO,oBAAoB;AAAA,EAC7B;AAAA,EACA,aAAa;AACX,WAAO;AAAA,EACT;AAAA,EACA,oBAAoB;AAClB,WAAO;AAAA,EACT;AAAA,EACA,mBAAmB;AACjB,WAAO;AAAA,EACT;AAAA,EACA,qBAAqB,OAAoC;AACvD,WAAO,IAAI,MAAM,aAAa,EAAE;AAAA,EAClC;AAAA,EACA,+BAA+B;AAC7B,WAAO,oCAAC,oCAA+B;AAAA,EACzC;AAAA,EACA,wBAAwB,QAGrB;AACD,QAAI,CAAC,UAAU,CAAC,OAAO,WAAW;AAChC,aACE,oCAAC,OAAI,eAAc,SACjB,oCAAC,YAAK,qBAAoB,GAC1B,oCAAC,YAAK,cAAY,CACpB;AAAA,IAEJ;AAEA,WACE,oCAAC,OAAI,eAAc,SACjB,oCAAC,YAAK,qBAAoB,GAC1B,oCAAC,QAAK,OAAO,SAAS,EAAE,WAAS,UACnB,OAAO,WAAU,WAC/B,CACF;AAAA,EAEJ;AAAA,EACA,yBAAyB,QAKtB;AACD,QAAI,OAAO,OAAO;AAChB,aAAO,wBAAwB,OAAO,KAAK;AAAA,IAC7C;AACA,WAAO,SAAS,OAAO,SAAS;AAAA,aACvB,OAAO,SAAS;AAAA,kBACX,OAAO,cAAc;AAAA,iBACtB,OAAO,aAAa;AAAA;AAAA;AAAA;AAAA,gDAIW,OAAO,SAAS;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAS9D;AAAA,EACA,MAAM,cAAc,EAAE,UAAU,GAAgC;AAC9D,QAAI,CAAC,WAAW,KAAK,GAAG;AACtB,aAAO;AAAA,QACL,QAAQ;AAAA,QACR,SAAS;AAAA,MACX;AAAA,IACF;AACA,UAAM,YAAY,iBAAiB,SAAS;AAC5C,QAAI,CAAC,aAAa,CAAC,WAAW,KAAK,SAAS,GAAG;AAC7C,aAAO;AAAA,QACL,QAAQ;AAAA,QACR,SAAS;AAAA,MACX;AAAA,IACF;AACA,WAAO,EAAE,QAAQ,KAAc;AAAA,EACjC;AAAA,EACA,OAAO,KAAK,OAAoC;AAC9C,QAAI;AACF,YAAM,gBAAgB,iBAAiB,MAAM,SAAS;AACtD,YAAM,OAAO,WAAW;AAAA,QACtB,MAAM;AAAA,QACN,aAAa;AAAA,QACb,cAAc;AAAA,QACd,aAAa,MAAM;AAAA,MACrB,CAAC;AAGD,kBAAY,KAAK,MAAM;AAAA,QACrB,IAAI,aAAa,KAAK,IAAI;AAAA,QAC1B,MAAM;AAAA,QACN,WAAW,MAAM,cAAc;AAAA,QAC/B,QAAQ;AAAA,QACR,QAAQ;AAAA,QACR,OAAO;AAAA,MACT,CAAC;AAED,YAAM,SAAS;AAAA,QACb,WAAW,KAAK;AAAA,QAChB,gBAAgB,kBAAkB,KAAK,IAAI;AAAA,QAC3C,eAAe,aAAa,KAAK,IAAI;AAAA,MACvC;AAEA,YAAM;AAAA,QACJ,MAAM;AAAA,QACN,MAAM;AAAA,QACN,oBAAoB,KAAK,yBAAyB,MAAM;AAAA,MAC1D;AAAA,IACF,SAAS,OAAO;AACd,YAAM,sBAAsB,OAAO,qBAAqB;AAAA,IAC1D;AAAA,EACF;AACF;",
+  "names": []
+}

package/dist/tools/TeamCreateTool/prompt.js

@@ -0,0 +1,58 @@
+const PROMPT = `# TeamCreate
+
+## When to Use
+
+Use this tool proactively whenever:
+- The user explicitly asks to use a team, swarm, or group of agents
+- A task benefits from parallel work by multiple agents (e.g., full-stack features, multi-step projects)
+
+When spawning teammates via the Agent tool, choose the \`subagent_type\` based on what tools the agent needs:
+- **Read-only agents** (Explore, Plan): research/planning only, cannot edit files
+- **Full-capability agents** (general-purpose): all tools including editing and bash
+- **Custom agents** (\`.claude/agents/\`): check their descriptions for tool restrictions
+
+**Permission note**: Teammates run with 'acceptEdits' permission mode \u2014 they can edit files and run commands within the project directory without user confirmation.
+
+Create a team to coordinate multiple agents working on a project. Teams have a 1:1 correspondence with task lists.
+
+## Team Workflow
+
+1. **Create a team** with TeamCreate
+2. **Create tasks** using TaskCreate \u2014 they automatically use the team's task list
+3. **Spawn teammates** using the Agent tool with \`team_name\` and \`name\` parameters
+4. **Assign tasks** using TaskUpdate with \`owner\`
+5. **Teammates work** on assigned tasks and mark them completed via TaskUpdate
+6. **Teammates go idle between turns** \u2014 this is normal. Be patient with idle teammates.
+7. **Shutdown your team** \u2014 send shutdown_request via SendMessage, then call TeamDelete to clean up
+
+## CRITICAL: Team Cleanup \u2014 NEVER SKIP
+
+You MUST call TeamDelete after composing your final answer. Failing to do so leaves stale team state.
+
+## Automatic Message Delivery
+
+Messages from teammates are delivered automatically as new conversation turns. You do NOT need to manually check inboxes. When reporting on teammate messages, you do NOT need to quote them \u2014 they're already rendered.
+
+## Teammate Idle State
+
+Teammates go idle after every turn \u2014 this is completely normal. Idle means waiting for input, not done or unavailable. Sending a message to an idle teammate wakes them up. Do not treat idle as an error.
+
+## Task List Coordination
+
+Teams share a task list at \`~/.minto/tasks/{team-name}/\`. Teammates should:
+1. Check TaskList after completing each task to find available work
+2. Claim unassigned tasks with TaskUpdate (prefer lowest ID first)
+3. Mark tasks completed, then check TaskList for next work
+
+**Communication rules**:
+- Always refer to teammates by NAME, never by UUID
+- Your team cannot hear you without SendMessage
+- Do NOT send structured JSON status messages \u2014 use plain text
+- Do NOT reply to simple status/completion notifications \u2014 process silently
+- Use TaskUpdate to mark tasks completed`;
+const DESCRIPTION = `Create a new team to coordinate multiple agents working on a project`;
+export {
+  DESCRIPTION,
+  PROMPT
+};
+//# sourceMappingURL=prompt.js.map

package/dist/tools/TeamCreateTool/prompt.js.map

@@ -0,0 +1,7 @@
+{
+  "version": 3,
+  "sources": ["../../../src/tools/TeamCreateTool/prompt.ts"],
+  "sourcesContent": ["export const PROMPT = `# TeamCreate\n\n## When to Use\n\nUse this tool proactively whenever:\n- The user explicitly asks to use a team, swarm, or group of agents\n- A task benefits from parallel work by multiple agents (e.g., full-stack features, multi-step projects)\n\nWhen spawning teammates via the Agent tool, choose the \\`subagent_type\\` based on what tools the agent needs:\n- **Read-only agents** (Explore, Plan): research/planning only, cannot edit files\n- **Full-capability agents** (general-purpose): all tools including editing and bash\n- **Custom agents** (\\`.claude/agents/\\`): check their descriptions for tool restrictions\n\n**Permission note**: Teammates run with 'acceptEdits' permission mode \u2014 they can edit files and run commands within the project directory without user confirmation.\n\nCreate a team to coordinate multiple agents working on a project. Teams have a 1:1 correspondence with task lists.\n\n## Team Workflow\n\n1. **Create a team** with TeamCreate\n2. **Create tasks** using TaskCreate \u2014 they automatically use the team's task list\n3. **Spawn teammates** using the Agent tool with \\`team_name\\` and \\`name\\` parameters\n4. **Assign tasks** using TaskUpdate with \\`owner\\`\n5. **Teammates work** on assigned tasks and mark them completed via TaskUpdate\n6. **Teammates go idle between turns** \u2014 this is normal. Be patient with idle teammates.\n7. **Shutdown your team** \u2014 send shutdown_request via SendMessage, then call TeamDelete to clean up\n\n## CRITICAL: Team Cleanup \u2014 NEVER SKIP\n\nYou MUST call TeamDelete after composing your final answer. Failing to do so leaves stale team state.\n\n## Automatic Message Delivery\n\nMessages from teammates are delivered automatically as new conversation turns. You do NOT need to manually check inboxes. When reporting on teammate messages, you do NOT need to quote them \u2014 they're already rendered.\n\n## Teammate Idle State\n\nTeammates go idle after every turn \u2014 this is completely normal. Idle means waiting for input, not done or unavailable. Sending a message to an idle teammate wakes them up. Do not treat idle as an error.\n\n## Task List Coordination\n\nTeams share a task list at \\`~/.minto/tasks/{team-name}/\\`. Teammates should:\n1. Check TaskList after completing each task to find available work\n2. Claim unassigned tasks with TaskUpdate (prefer lowest ID first)\n3. Mark tasks completed, then check TaskList for next work\n\n**Communication rules**:\n- Always refer to teammates by NAME, never by UUID\n- Your team cannot hear you without SendMessage\n- Do NOT send structured JSON status messages \u2014 use plain text\n- Do NOT reply to simple status/completion notifications \u2014 process silently\n- Use TaskUpdate to mark tasks completed`\n\nexport const DESCRIPTION = `Create a new team to coordinate multiple agents working on a project`\n"],
+  "mappings": "AAAO,MAAM,SAAS;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAqDf,MAAM,cAAc;",
+  "names": []
+}