claude-code - 💡(How to fix) Fix [BUG] Agent tool with team_name returns err=True but still spawns agent, causing silent duplicate launches [1 comments, 2 participants]

This causes the orchestrating model to correctly interpret the error as a failed launch and retry, resulting in N duplicate agents consuming quota simultaneously for the same task. Either return success (agent launched, registration optional), or roll back the spawn if registration fails — but never return an error while silently leaving the agent running.

Error Messages/Logs

TL;DR

The Agent tool should be modified to either return success when the agent is launched but team registration fails, or roll back the spawn if registration fails, to prevent duplicate agents from consuming quota simultaneously.

Guidance

• Investigate the Agent tool's error handling to determine why it returns an error while still spawning the agent process when team registration fails.
• Consider modifying the Agent tool to catch the "Team does not exist" error and either return success or roll back the spawn, as described in the "What Should Happen?" section.
• Review the orchestrating model's retry logic to ensure it can handle cases where the Agent tool returns success even if team registration fails.
• Verify that the modified Agent tool behaves correctly in scenarios where team registration fails, to prevent duplicate agents from being spawned.

Example

No code snippet is provided, as the issue does not include sufficient code details.

Notes

The root cause of the issue appears to be related to the Agent tool's error handling and the orchestrating model's retry logic. However, without more information about the Agent tool's implementation, it is difficult to provide a more specific solution.

Recommendation

Apply a workaround by modifying the Agent tool to handle team registration failures correctly, as this is likely to be a more immediate solution than waiting for a potential fix in a future version.