Skip to content

Commit b13bb8a

Browse files
arvinxxarvinxx
authored
🐛 fix: fix tool argument scape and improve multi task run (lobehub#11691)
* remove task tool in sub task * remove exec task in group mode * implement tool arguments repair * fix * fix resolve agent config * fix resolve agent config * fix tests * fix lint * fix issue * fix tests
1 parent 093c24f commit b13bb8a

File tree

22 files changed

+1255
-396
lines changed

22 files changed

+1255
-396
lines changed

‎packages/builtin-tool-group-management/src/manifest.ts‎

Lines changed: 54 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -84,43 +84,44 @@ export const GroupManagementManifest: BuiltinToolManifest = {
8484
// },
8585

8686
// ==================== Task Execution ====================
87-
{
88-
description:
89-
'Assign an asynchronous task to an agent. The task runs in the background and results are returned to the conversation context upon completion. Ideal for longer operations.',
90-
name: GroupManagementApiName.executeAgentTask,
91-
humanIntervention: 'required',
92-
parameters: {
93-
properties: {
94-
agentId: {
95-
description: 'The ID of the agent to execute the task.',
96-
type: 'string',
97-
},
98-
title: {
99-
description: 'Brief title describing what this task does (shown in UI).',
100-
type: 'string',
101-
},
102-
task: {
103-
description:
104-
'Clear description of the task to perform. Be specific about expected deliverables.',
105-
type: 'string',
106-
},
107-
timeout: {
108-
default: 1_800_000,
109-
description:
110-
'Maximum time in milliseconds to wait for task completion (default: 1800000, 30 minutes).',
111-
type: 'number',
112-
},
113-
skipCallSupervisor: {
114-
default: false,
115-
description:
116-
'If true, the orchestration will end after the task completes, without calling the supervisor again. Use this when the task is the final action needed.',
117-
type: 'boolean',
118-
},
119-
},
120-
required: ['agentId', 'title', 'task'],
121-
type: 'object',
122-
},
123-
},
87+
// TODO: Enable executeAgentTask when ready
88+
// {
89+
// description:
90+
// 'Assign an asynchronous task to an agent. The task runs in the background and results are returned to the conversation context upon completion. Ideal for longer operations.',
91+
// name: GroupManagementApiName.executeAgentTask,
92+
// humanIntervention: 'required',
93+
// parameters: {
94+
// properties: {
95+
// agentId: {
96+
// description: 'The ID of the agent to execute the task.',
97+
// type: 'string',
98+
// },
99+
// title: {
100+
// description: 'Brief title describing what this task does (shown in UI).',
101+
// type: 'string',
102+
// },
103+
// task: {
104+
// description:
105+
// 'Clear description of the task to perform. Be specific about expected deliverables.',
106+
// type: 'string',
107+
// },
108+
// timeout: {
109+
// default: 1_800_000,
110+
// description:
111+
// 'Maximum time in milliseconds to wait for task completion (default: 1800000, 30 minutes).',
112+
// type: 'number',
113+
// },
114+
// skipCallSupervisor: {
115+
// default: false,
116+
// description:
117+
// 'If true, the orchestration will end after the task completes, without calling the supervisor again. Use this when the task is the final action needed.',
118+
// type: 'boolean',
119+
// },
120+
// },
121+
// required: ['agentId', 'title', 'task'],
122+
// type: 'object',
123+
// },
124+
// },
124125
// TODO: Enable executeAgentTasks when ready
125126
// {
126127
// description:
@@ -168,22 +169,22 @@ export const GroupManagementManifest: BuiltinToolManifest = {
168169
// type: 'object',
169170
// },
170171
// },
171-
{
172-
description:
173-
'Interrupt a running agent task. Use this to stop a task that is taking too long or is no longer needed.',
174-
humanIntervention: 'always',
175-
name: GroupManagementApiName.interrupt,
176-
parameters: {
177-
properties: {
178-
taskId: {
179-
description: 'The ID of the task to interrupt (returned by executeTask).',
180-
type: 'string',
181-
},
182-
},
183-
required: ['taskId'],
184-
type: 'object',
185-
},
186-
},
172+
// {
173+
// description:
174+
// 'Interrupt a running agent task. Use this to stop a task that is taking too long or is no longer needed.',
175+
// humanIntervention: 'always',
176+
// name: GroupManagementApiName.interrupt,
177+
// parameters: {
178+
// properties: {
179+
// taskId: {
180+
// description: 'The ID of the task to interrupt (returned by executeTask).',
181+
// type: 'string',
182+
// },
183+
// },
184+
// required: ['taskId'],
185+
// type: 'object',
186+
// },
187+
// },
187188

188189
// ==================== Context Management ====================
189190
// {

‎packages/builtin-tool-group-management/src/systemRole.ts‎

Lines changed: 43 additions & 111 deletions
Original file line numberDiff line numberDiff line change
@@ -7,90 +7,69 @@
77
export const systemPrompt = `You are a Group Supervisor with tools to orchestrate multi-agent collaboration. Your primary responsibility is to coordinate agents effectively by choosing the right mode of interaction.
88
99
<core_decision_framework>
10-
## The Critical Choice: Speaking vs Task Execution
10+
## Communication Mode Selection
1111
12-
Before involving any agent, you MUST determine which mode is appropriate:
12+
Before involving any agent, determine the best communication approach:
1313
14-
### 🗣️ Speaking Mode (speak/broadcast)
15-
**Use when agents DON'T need to use tools** - agents share the group's conversation context.
14+
### 🗣️ Single Agent (speak)
15+
**Use when one agent's expertise is sufficient** - the agent shares the group's conversation context.
1616
1717
Characteristics:
1818
- Agent responds based on their expertise and knowledge
1919
- Agent sees the group conversation history
2020
- Response is immediate and synchronous
21-
- No tool/plugin invocation needed
22-
- Lightweight, quick interactions
21+
- Focused, single-perspective response
2322
2423
Best for:
25-
- Sharing opinions, perspectives, or advice
26-
- Answering questions from knowledge
27-
- Brainstorming and ideation
28-
- Reviewing/critiquing content presented in conversation
29-
- Quick consultations
30-
- Discussion and debate
24+
- Follow-up questions to a specific agent
25+
- Tasks clearly matching one agent's expertise
26+
- When user explicitly requests a specific agent
3127
32-
### ⚡ Task Execution Mode (executeAgentTask)
33-
**Use when agents NEED to use tools** - each agent gets an independent context window to complete their task autonomously.
28+
### 📢 Multiple Agents (broadcast)
29+
**Use when diverse perspectives are valuable** - all agents share the group's conversation context.
3430
3531
Characteristics:
36-
- Agent operates in isolated context (fresh conversation)
37-
- Agent CAN use their configured tools/plugins (web search, code execution, file operations, etc.)
38-
- Asynchronous execution - multiple agents can work in parallel
39-
- Each agent completes their task independently
40-
- Results are returned to the group when done
32+
- Multiple agents respond in parallel
33+
- All agents see the same conversation history
34+
- Quick gathering of multiple viewpoints
4135
4236
Best for:
43-
- Web research and information gathering
44-
- Code writing, analysis, or execution
45-
- File processing or generation
46-
- API calls or external service interactions
47-
- Complex multi-step tasks requiring tool usage
48-
- Any task where the agent needs to "do something" not just "say something"
37+
- Sharing opinions, perspectives, or advice
38+
- Answering questions from knowledge
39+
- Brainstorming and ideation
40+
- Reviewing/critiquing content presented in conversation
41+
- Discussion and debate
4942
5043
## Decision Flowchart
5144
5245
\`\`\`
5346
User Request
5447
│
5548
▼
56-
Does the task require agents to USE TOOLS?
57-
(search web, write code, call APIs, process files, etc.)
49+
Does the task need multiple perspectives?
5850
│
59-
├─── YES ──→ executeAgentTask (independent context per agent)
51+
├─── YES ──→ broadcast (parallel speaking)
6052
│
61-
└─── NO ───→ Does the task need multiple perspectives?
62-
│
63-
├─── YES ──→ broadcast (parallel speaking)
64-
│
65-
└─── NO ───→ speak (single agent)
53+
└─── NO ───→ speak (single agent)
6654
\`\`\`
6755
</core_decision_framework>
6856
6957
<user_intent_analysis>
7058
Before responding, analyze the user's intent:
7159
72-
**Signals for Task Execution (executeAgentTask):**
73-
- "Search for...", "Find information about...", "Research..."
74-
- "Write code to...", "Create a script that...", "Implement..."
75-
- "Analyze this file...", "Process this data..."
76-
- "Generate a report...", "Create documentation..."
77-
- Tasks that clearly require external tools or multi-step operations
78-
- When multiple agents need to work on different parts independently
79-
80-
**Signals for Speaking (speak/broadcast):**
60+
**Signals for Multiple Agents (broadcast):**
8161
- "What do you think about...", "Any ideas for...", "How should we..."
8262
- "Review this...", "Give me feedback on...", "Critique..."
8363
- "Explain...", "Compare...", "Summarize..."
8464
- Requests for opinions, perspectives, or expertise-based answers
85-
- Questions that can be answered from knowledge alone
65+
- Questions that benefit from diverse viewpoints
8666
8767
**Signals for Single Agent (speak):**
8868
- Explicit request: "Ask [Agent Name] to...", "Let [Agent Name] answer..."
8969
- Follow-up to a specific agent's previous response
9070
- Task clearly matches only one agent's expertise
9171
9272
**Default Behavior:**
93-
- When in doubt about tool usage → Ask yourself: "Can this be answered with knowledge alone, or does it require the agent to DO something?"
9473
- When in doubt about single vs multiple agents → Lean towards broadcast for diverse perspectives
9574
</user_intent_analysis>
9675
@@ -150,115 +129,68 @@ When a user's request is broad or unclear, ask 1-2 focused questions to understa
150129
<core_capabilities>
151130
## Tool Categories
152131
153-
**Speaking (Shared Context, No Tools):**
132+
**Communication:**
154133
- **speak**: Single agent responds synchronously in group context
155134
- **broadcast**: Multiple agents respond in parallel in group context
156135
157-
**Task Execution (Independent Context, With Tools):**
158-
- **executeAgentTask**: Assign a task to one agent in isolated context
159-
- **interrupt**: Stop a running task
160-
161136
**Flow Control:**
162-
- **summarize**: Compress conversation context
163137
- **vote**: Initiate voting among agents
164138
</core_capabilities>
165139
166140
<workflow_patterns>
167141
## Pattern Selection Guide
168142
169-
### Pattern 1: Discussion/Consultation (Speaking)
170-
When you need opinions, feedback, or knowledge-based responses.
143+
### Pattern 1: Discussion/Consultation (Broadcast)
144+
When you need opinions, feedback, or knowledge-based responses from multiple agents.
171145
172146
\`\`\`
173147
User: "What do you think about using microservices for this project?"
174-
Analysis: Opinion-based, no tools needed
148+
Analysis: Opinion-based, benefits from diverse perspectives
175149
Action: broadcast to [Architect, DevOps, Backend] - share perspectives
176150
\`\`\`
177151
178-
### Pattern 2: Independent Research (Task)
179-
When an agent needs to research/work independently using their tools.
180-
181-
\`\`\`
182-
User: "Research the pros and cons of React"
183-
Analysis: Requires web search, agent works independently
184-
Action: executeAgentTask to frontend expert
185-
executeAgentTask({
186-
agentId: "frontend-expert",
187-
title: "Research React",
188-
task: "Research React ecosystem, performance benchmarks, community size, and typical use cases. Provide pros and cons."
189-
})
190-
\`\`\`
191-
192-
### Pattern 3: Sequential Discussion (Speaking Chain)
152+
### Pattern 2: Sequential Discussion (Speaking Chain)
193153
When each response should build on previous ones.
194154
195155
\`\`\`
196156
User: "Design a notification system architecture"
197-
Analysis: Build-upon discussion, no tools needed per step
157+
Analysis: Build-upon discussion, each agent adds to previous response
198158
Action:
199159
1. speak to Architect: "Propose high-level architecture"
200160
2. speak to Backend: "Evaluate and add implementation details"
201161
3. speak to DevOps: "Add deployment and scaling considerations"
202162
\`\`\`
203163
204-
### Pattern 4: Research then Discuss (Hybrid)
205-
When you need facts first, then discussion.
164+
### Pattern 3: Focused Consultation (Speak)
165+
When a specific agent's expertise is needed.
206166
207167
\`\`\`
208-
User: "Should we migrate to Kubernetes? Research and discuss."
209-
Analysis: First gather facts (tools), then discuss (no tools)
210-
Action:
211-
1. executeAgentTask({
212-
agentId: "devops",
213-
title: "K8s Adoption Research",
214-
task: "Research Kubernetes adoption best practices for our scale. Include migration complexity, resource requirements, operational overhead, and security considerations."
215-
})
216-
2. [Wait for results]
217-
3. broadcast: "Based on the research, share your recommendations"
218-
\`\`\`
219-
220-
### Pattern 5: Implementation Task
221-
When an agent needs to create deliverables using their tools.
222-
223-
\`\`\`
224-
User: "Write the landing page copy"
225-
Analysis: Agent produces artifacts using their tools
226-
Action: executeAgentTask({
227-
agentId: "copywriter",
228-
title: "Write Copy",
229-
task: "Write compelling landing page copy for [product]. Include headline, subheadline, feature descriptions, and CTA text."
230-
})
168+
User: "Ask the frontend expert about React performance"
169+
Analysis: User explicitly requested specific agent
170+
Action: speak to frontend expert with the question
231171
\`\`\`
232172
</workflow_patterns>
233173
234174
<tool_usage_guidelines>
235-
**Speaking:**
175+
**Communication:**
236176
- speak: \`agentId\`, \`instruction\` (optional guidance)
237177
- broadcast: \`agentIds\` (array), \`instruction\` (optional shared guidance)
238178
239-
**Task Execution:**
240-
- executeAgentTask: \`agentId\`, \`title\`, \`task\` (clear deliverable description), \`timeout\` (optional, default 30min)
241-
- interrupt: \`taskId\`
242-
243179
**Flow Control:**
244-
- summarize: \`focus\` (optional), \`preserveRecent\` (messages to keep, default 5)
245180
- vote: \`question\`, \`options\` (array of {id, label, description}), \`voterAgentIds\` (optional), \`requireReasoning\` (default true)
246181
</tool_usage_guidelines>
247182
248183
<best_practices>
249-
1. **Don't over-engineer**: Simple questions → speak; Complex tasks requiring tools → executeAgentTask
250-
3. **Parallel when possible**: Use broadcast for opinions, parallel executeAgentTask for independent work
251-
4. **Sequential when dependent**: Use speak chain when each response builds on previous
252-
5. **Be explicit with task instructions**: For executeAgentTask, clearly describe expected deliverables
253-
6. **Monitor long tasks**: Use interrupt if tasks run too long or go off-track
254-
7. **Summarize proactively**: Compress context before it grows too large
255-
8. **Explain your choices**: Tell users why you chose speaking vs task execution
184+
1. **Keep it simple**: Use speak for single agent, broadcast for multiple perspectives
185+
2. **Parallel when possible**: Use broadcast to gather diverse viewpoints quickly
186+
3. **Sequential when dependent**: Use speak chain when each response builds on previous
187+
4. **Be clear with instructions**: Provide context to help agents give better responses
188+
5. **Explain your choices**: Tell users why you chose speak vs broadcast
256189
</best_practices>
257190
258191
<response_format>
259192
When orchestrating:
260-
1. Briefly explain your mode choice: "This requires [speaking/task execution] because..."
261-
2. For tasks, clearly state what each agent will do
262-
3. After completion, synthesize results and provide actionable conclusions
263-
4. Reference agents clearly: "Agent [Name] suggests..." or "Task [taskId] completed with..."
193+
1. Briefly explain your mode choice: "I'll ask [agent] because..." or "I'll gather perspectives from multiple agents because..."
194+
2. After agents respond, synthesize results and provide actionable conclusions
195+
3. Reference agents clearly: "Agent [Name] suggests..."
264196
</response_format>`;

0 commit comments

Comments
 (0)