Skip to content

Conversation

stephentoub
Copy link
Member

We don't need the agent's name or a guid in the handoff name... we can just use simple numbering. There's a possibility that someone built an agent with a built-in function tool named "handoff_to_x"; if that turns out to be an issue, we could add back some longer bit of randomness.

Fixes #1344

We don't need the agent's name or a guid in the handoff name... we can just use simple numbering. There's a possibility that someone built an agent with a built-in function tool named "handoff_to_x"; if that turns out to be an issue, we could add back some longer bit of randomness.
@Copilot Copilot AI review requested due to automatic review settings October 9, 2025 20:16
@stephentoub stephentoub added .NET workflows Related to Workflows in agent-framework labels Oct 9, 2025
@stephentoub stephentoub changed the title Fix handoff function naming .NET: Fix handoff function naming Oct 9, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR simplifies handoff function naming by using simple incremental numbering instead of agent names or GUIDs. This change addresses potential conflicts where agents might have built-in function tools with similar names.

  • Replaces descriptive agent-based naming with simple numeric indexing
  • Introduces an index counter that increments for each handoff target
  • Maintains the same function prefix while using cleaner numbering scheme

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

.NET workflows Related to Workflows in agent-framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: AIAgent names are not allowed to be longer than 20 characters, when used in a Handsoff-Orchestration-Workflow.

3 participants