You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: add loop detection for same-agent back-to-back invocations in 1.3.0
In agent-framework 1.3.0, GroupChatBuilder makes the Coordinator internal
to AgentBasedGroupChatOrchestrator - its responses never appear in the
streaming loop, making our coordinator-based loop detection dead code.
Additionally, _start_agent_if_needed silently returned when the same
agent was selected consecutively, preventing max_rounds from counting.
Fixes:
- Use response_id from AgentResponseUpdate to detect new invocations
of the same agent (even when executor_id hasn't changed)
- Add participant-side loop detection: if same agent runs 5+
consecutive times, force termination with descriptive message
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
0 commit comments