Required prerequisites
Motivation
Applications that need a "plan → edit → run" workflow must subclass Workforce and override internal methods. Specifically:
- No public planning API —
handle_decompose_append_task() decomposes and immediately appends to the pending queue. There is no way to decompose, inspect/edit the plan, and then execute separately.
- Event metadata insufficient —
WorkerCreatedEvent, TaskAssignedEvent, TaskStartedEvent, TaskCompletedEvent lack fields like agent_id, task_content, failure_count, pool_config. Applications must read internal state to build UI notifications.
task.subtasks out of sync — when a subtask completes or fails, parent.subtasks[*].state/result is not updated. Applications must manually sync with _sync_subtask_to_parent() overrides.
Scope
Workforce orchestration only. ChatAgent callbacks and SingleAgentWorker streaming are tracked separately.
Solution
No response
Alternatives
No response
Additional context
No response
Required prerequisites
Motivation
Applications that need a "plan → edit → run" workflow must subclass
Workforceand override internal methods. Specifically:handle_decompose_append_task()decomposes and immediately appends to the pending queue. There is no way to decompose, inspect/edit the plan, and then execute separately.WorkerCreatedEvent,TaskAssignedEvent,TaskStartedEvent,TaskCompletedEventlack fields likeagent_id,task_content,failure_count,pool_config. Applications must read internal state to build UI notifications.task.subtasksout of sync — when a subtask completes or fails,parent.subtasks[*].state/resultis not updated. Applications must manually sync with_sync_subtask_to_parent()overrides.Scope
Workforceorchestration only. ChatAgent callbacks and SingleAgentWorker streaming are tracked separately.Solution
No response
Alternatives
No response
Additional context
No response