You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
? `- delegate-task: You may use this for bounded side work when needed. You have a budget of ${config.member_delegate_task_budget} calls for this team run.`
6
+
: "- delegate-task: Do not call this. Member delegate budget is disabled for this team run."
7
+
8
+
return`
9
+
# Team Communication
10
+
11
+
You are running as a team member. Your text responses are NOT visible to other team members or the lead.
12
+
13
+
IMPORTANT: For ALL team_* tool calls, use the TeamRunId shown above as the \`teamRunId\` parameter. Do NOT use the team name.
14
+
15
+
Do not call lead-only lifecycle tools such as \`team_shutdown_request\`, \`team_delete\`, \`team_approve_shutdown\`, or \`team_reject_shutdown\`.
16
+
17
+
Use these tools instead:
18
+
- team_send_message: Send results, blockers, or completion updates to the lead. Use \`to: "lead"\` for the lead, \`to: "<name>"\` for a specific member. Include \`summary\` and \`references\` when they help the lead triage quickly.
19
+
- team_task_update: Update your task status. Move to \`status: "in_progress"\` when you start working, and \`status: "completed"\` when done. \`status: "claimed"\` is optional if you want to explicitly claim before you begin.
20
+
- team_task_list: See all team tasks and their status.
21
+
- team_task_get: Get details of a specific task.
22
+
${delegateTaskGuidance}
23
+
24
+
When you finish your assigned work, ALWAYS:
25
+
1. Send your results to lead via team_send_message
26
+
2. Mark your task as completed via team_task_update
27
+
3. Send a completion message to lead so the lead can decide whether to request shutdown
@@ -94,32 +95,17 @@ async function waitForTaskSessionId(bgMgr: BackgroundManager, task: BackgroundTa
94
95
returnsessionId
95
96
}
96
97
97
-
constTEAMMATE_COMMUNICATION_ADDENDUM=`
98
-
# Team Communication
99
-
100
-
You are running as a team member. Your text responses are NOT visible to other team members or the lead.
101
-
102
-
IMPORTANT: For ALL team_* tool calls, use the TeamRunId shown above as the \`teamRunId\` parameter. Do NOT use the team name.
103
-
104
-
Do not call lead-only lifecycle tools such as \`team_shutdown_request\`, \`team_delete\`, \`team_approve_shutdown\`, or \`team_reject_shutdown\`.
105
-
106
-
Use these tools instead:
107
-
- team_send_message: Send results, blockers, or completion updates to the lead. Use \`to: "lead"\` for the lead, \`to: "<name>"\` for a specific member.
108
-
- team_task_update: Update your task status. Use \`status: "claimed"\` when starting, \`status: "in_progress"\` while working, \`status: "completed"\` when done.
109
-
- team_task_list: See all team tasks and their status.
110
-
- team_task_get: Get details of a specific task.
111
-
112
-
When you finish your assigned work, ALWAYS:
113
-
1. Send your results to lead via team_send_message
114
-
2. Mark your task as completed via team_task_update
115
-
3. Send a completion message to lead so the lead can decide whether to request shutdown
0 commit comments