Description
The TeamCreate tool documentation (part of the system prompt) explicitly references TaskCreate, TaskList, and TaskUpdate as available tools for team coordination:
"2. Create tasks using the Task tools (TaskCreate, TaskList, etc.) — they automatically use the team's task list"
"4. Assign tasks using TaskUpdate with owner to give tasks to idle teammates"
"5. Teammates work on assigned tasks and mark them completed via TaskUpdate"
These tools do not exist at runtime — not for the main session, not for spawned agents (general-purpose with "Tools: *"), and not as deferred tools via ToolSearch.
Environment
- Claude Code v2.1.34 (also tested on 2.1.32)
- VSCode extension
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is set to "1" in ~/.claude/settings.json
TeamCreate, TeamDelete, and SendMessage all work — only the task management tools are missing
Steps to Reproduce
- Enable experimental agent teams:
{ "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" } }
- Create a team with
TeamCreate — works, creates ~/.claude/teams/{name}/ and ~/.claude/tasks/{name}/
- Attempt to call
TaskCreate to populate the task board — tool does not exist
- Search via
ToolSearch for TaskCreate, TaskList, TaskUpdate — no results
- Spawned general-purpose agents ("Tools: *") also cannot find these tools
Impact
The TeamCreate documentation describes a task board coordination workflow (create tasks → assign to agents → agents claim and complete tasks → dependency gating). This is the core orchestration mechanism for agent teams. Without TaskCreate/TaskList/TaskUpdate, there is no way to use the task board that TeamCreate itself sets up.
The team infrastructure directory (~/.claude/tasks/{team-name}/) gets created but has no tool-based interface to populate or read it. The only coordination available is SendMessage for peer-to-peer messaging, which works but is a fundamentally different (and less capable) coordination model than what the documentation describes.
Expected Behavior
TaskCreate, TaskList, and TaskUpdate should be available as tools when CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is enabled, matching the TeamCreate documentation.
Workaround
Currently none that preserves the documented task board workflow. Agents can coordinate through SendMessage and prompt-based instructions, but without the task tools there is no shared task board, no dependency gating, and no self-coordination.
Description
The
TeamCreatetool documentation (part of the system prompt) explicitly referencesTaskCreate,TaskList, andTaskUpdateas available tools for team coordination:These tools do not exist at runtime — not for the main session, not for spawned agents (general-purpose with "Tools: *"), and not as deferred tools via
ToolSearch.Environment
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMSis set to"1"in~/.claude/settings.jsonTeamCreate,TeamDelete, andSendMessageall work — only the task management tools are missingSteps to Reproduce
{ "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" } }TeamCreate— works, creates~/.claude/teams/{name}/and~/.claude/tasks/{name}/TaskCreateto populate the task board — tool does not existToolSearchfor TaskCreate, TaskList, TaskUpdate — no resultsImpact
The
TeamCreatedocumentation describes a task board coordination workflow (create tasks → assign to agents → agents claim and complete tasks → dependency gating). This is the core orchestration mechanism for agent teams. WithoutTaskCreate/TaskList/TaskUpdate, there is no way to use the task board thatTeamCreateitself sets up.The team infrastructure directory (
~/.claude/tasks/{team-name}/) gets created but has no tool-based interface to populate or read it. The only coordination available isSendMessagefor peer-to-peer messaging, which works but is a fundamentally different (and less capable) coordination model than what the documentation describes.Expected Behavior
TaskCreate,TaskList, andTaskUpdateshould be available as tools whenCLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMSis enabled, matching theTeamCreatedocumentation.Workaround
Currently none that preserves the documented task board workflow. Agents can coordinate through
SendMessageand prompt-based instructions, but without the task tools there is no shared task board, no dependency gating, and no self-coordination.