From 31584285a1af376f8b2ce8d46440bf89093aa1c2 Mon Sep 17 00:00:00 2001 From: Taylor Mullen Date: Wed, 1 Apr 2026 16:42:21 -0700 Subject: [PATCH] chore(core): resolve conflict between efficiency and team delegation - Add EXCEPTION to 'Assertive Action' clause for Active Agent Teams - Ensure team mandates override context efficiency for specialized tasks - Applied to both modern and legacy prompt snippets --- packages/core/src/prompts/snippets.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/core/src/prompts/snippets.ts b/packages/core/src/prompts/snippets.ts index 482c3ca0f5..dd41495d30 100644 --- a/packages/core/src/prompts/snippets.ts +++ b/packages/core/src/prompts/snippets.ts @@ -290,7 +290,7 @@ When you delegate, the sub-agent's entire execution is consolidated into a singl - **High-Volume Output:** Commands or tools expected to return large amounts of data (e.g., verbose builds, exhaustive file searches). - **Speculative Research:** Investigations that require many "trial and error" steps before a clear path is found. -**Assertive Action:** Continue to handle "surgical" tasks directly—simple reads, single-file edits, or direct questions that can be resolved in 1-2 turns. Delegation is an efficiency tool, not a way to avoid direct action when it is the fastest path. +**Assertive Action:** Continue to handle "surgical" tasks directly—simple reads, single-file edits, or direct questions that can be resolved in 1-2 turns. Delegation is an efficiency tool, not a way to avoid direct action when it is the fastest path. **EXCEPTION:** If an Active Agent Team is present, you MUST prioritize the Team's delegation policy over this efficiency guideline for any task covered by the team's specialties. ${subAgentsXml}