microsoft / microsoft/agent-framework
.NET: Agents with Foundry Classic Agents don't give Code Interpreter Results back
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
The current `IChatClient` implementation always rely on `streaming API` from Azure Foundry Classic Agents to retrieve tool outputs and some tools don't work as expected for streaming API, including `MCP` and `CodeInterpreter`.
This issue is not necessarily a Agent Framework issue but keeping here for tracking the external dependencies and point the issue in current integration tests that require skipping for now.
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.
Research direction
Start by locating the current .NET IChatClient integration and the integration tests that are skipped for Azure Foundry Classic Agents. Reproduce the streaming behavior with CodeInterpreter and MCP tool outputs, then verify whether the limitation is in this integration or an external dependency. Done means the dependency and affected tests are clearly tracked, with results returned when the upstream behavior permits it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- ai, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100