.NET: Fix FoundryAgents_Step15_ComputerUse sample for Azure Agents API#3989
Merged
rogerbarreto merged 2 commits intomicrosoft:mainfrom Feb 19, 2026
Conversation
The Azure Agents API rejects previous_response_id alongside computer_call_output items, unlike the vanilla OpenAI Responses API. This fix: - Send all prior response output items (reasoning, computer_call, etc.) as input items in follow-up calls so the API has full conversation context - Create a fresh session per call to avoid ConversationId/previous_response_id - Use currentCallId instead of initialCallId for computer_call_output - Clear ContinuationToken after polling to prevent stale tokens - Remove unused initialCallId tracking variable Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
rogerbarreto
temporarily deployed
to
integration
GitHub Actions
Inactive
rogerbarreto
temporarily deployed
to
integration
GitHub Actions
Inactive
github-actions
bot
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request fixes the FoundryAgents_Step15_ComputerUse sample to work correctly with the Azure Agents API. The Azure Agents API has specific requirements for computer use that differ from the vanilla OpenAI Responses API—it rejects requests containing previous_response_id alongside computer_call_output items. The fix implements a pattern of creating fresh sessions for each interaction and manually providing full conversation context by re-sending prior response output items.
Changes:
- Move session creation to occur just before initial request (avoiding premature creation)
- Add continuation token clearing after polling completes to prevent stale tokens
- Remove unused
initialCallIdtracking variable that's no longer needed - Use
currentCallIdinstead ofinitialCallIdfor computer_call_output - Implement Azure-specific pattern: re-send all prior response output items as an assistant message alongside computer_call_output in a fresh session
markwallace-microsoft
approved these changes
Feb 17, 2026
westey-m
reviewed
Feb 17, 2026
dotnet/samples/GettingStarted/FoundryAgents/FoundryAgents_Step15_ComputerUse/Program.cs
Outdated
Show resolved
Hide resolved
westey-m
approved these changes
Feb 17, 2026
markwallace-microsoft
added
the
documentation
rogerbarreto
temporarily deployed
to
integration
GitHub Actions
Inactive
rogerbarreto
temporarily deployed
to
integration
GitHub Actions
Inactive
westey-m
approved these changes
Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation and Context
The Azure Agents API rejects previous_response_id alongside computer_call_output items, unlike the vanilla OpenAI Responses API. This fix: