TeamCreate silently ignores team_name parameter, assigns random name
Resolved 💬 1 comment Opened Apr 9, 2026 by cbockenstette-commits Closed Apr 9, 2026
Bug
TeamCreate ignores the team_name parameter and silently assigns a random 3-word name (e.g., "greedy-sparking-raven"). No error or warning is produced.
Steps to Reproduce
- Call
TeamCreate(team_name: "plan-team-44a5bd90", description: "Planning team") - Observe response:
{"team_name": "greedy-sparking-raven", ...} - The requested name
"plan-team-44a5bd90"is silently discarded
Expected Behavior
Either:
- Use the requested
team_name, OR - Return an error explaining why the name was rejected
Actual Behavior
The team_name parameter is silently ignored. A random 3-word name is assigned with no indication that the requested name was discarded.
Impact
- Breaks deterministic team naming conventions (e.g., session-scoped names for multi-session collision avoidance)
- Subsequent
Agent(team_name: "plan-team-44a5bd90")calls fail because the team doesn't exist under that name - This triggers the orphan-spawn bug (Agent spawns anyway on team-not-found error)
- Cascading failure: silent rename → lookup failure → orphan spawns → token waste
Environment
- Claude Code CLI
- Observed: 2026-04-08
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗