microsoft / microsoft/agent-framework
Python: Tool Outputs No Longer Broadcast Between GroupChat Agents
@TaoChenOSU is already working on this.
Since Mar 10, 2026.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
### Discussed in https://github.com/microsoft/agent-framework/discussions/4458
Originally posted by **jlahteen** March 5, 2026
We have migrated our existing AutoGen app to Agent Framework using the version 1.0.0b260127 (Python). This migration went quite smoothly, and we got the app working on Agent Framework.
However, when we upgraded to RC2 (1.0.0rc2), the functionality of the app did break. After investigations we realized that there is a fundamental change in broadcasting tool outputs in GroupChat. In other words, tool outputs are not broadcasted anymore for downstream agents. This breaking change has been introduced in [PR #3712](https://github.com/microsoft/agent-framework/pull/3712) without any big headlines.
Broadcasting tool outputs to downstream agents would be beneficial in many real world scenarios. For example, if agent A runs a tool with a vast output and then agent B analyses it. Now the only workaround for this is to prompt the agent A to include the tool output in its response causing more token consumption and performance loss.
Please consider making tool output broadcasting a configurable feature in workflows. It could be even configurable per agent or executor.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.