.NET: Promote FoundryChatClient to public, add file/vector-store helpers and ToPromptAgentAsync converter by rogerbarreto · Pull Request #5940 · microsoft/agent-framework

rogerbarreto · 2026-05-18T22:55:01Z

Motivation and Context

This PR adds the .NET equivalent of the Foundry "Agent Framework to Prompt Agents" spec. Today there is no .NET way to take an agent built and tested locally and publish it as a server-side Foundry prompt agent without manually restating the entire definition; this PR closes that gap and adds the file/vector-store helper surface that Python's spec also calls for, matching the Python developer experience.

Description

Two changes ship together because they share infrastructure on the same FoundryChatClient:

FoundryChatClient promoted to public sealed so .NET developers can hold and pass the type directly, mirroring Python. Mode 3 (hosted agent endpoint URL) now materializes an AIProjectClient from the parsed project root, eliminating the per-mode asymmetry that previously hid project-level operations from agents constructed via an agent endpoint URL. GetService<AIProjectClient>() returns a non-null instance for all three construction modes after this change.
Four new instance methods on FoundryChatClient mirroring Python's spec: UploadFileAsync, DeleteFileAsync, CreateVectorStoreAsync (bundles upload + create + wait into one call), DeleteVectorStoreAsync. Single overload each, path-only inputs to start; additional overloads can be added later without breaking callers. Available uniformly across all three construction modes.
ToPromptAgentAsync extension methods on both ChatClientAgent (in namespace Microsoft.Agents.AI.Foundry) and FoundryAgent. Returns a ProjectsAgentDefinition ready to pass to AgentAdministrationClient.CreateAgentVersionAsync. Mode 1 synthesizes a fresh DeclarativeAgentDefinition from the agent's ChatOptions (model id, instructions, temperature, top-p, tools); mode 2 returns the cached or freshly fetched ProjectsAgentVersion.Definition (the AgentReference-only path fetches the latest version from the service); mode 3 throws InvalidOperationException because no local definition exists to convert.
Strict AITool to ResponseTool mapping for mode 1 synthesis: AIFunction becomes ResponseTool.CreateFunctionTool carrying the function's JSON schema; AITool instances that wrap a ResponseTool (everything produced by FoundryAITool factories) unwrap via GetService(typeof(ResponseTool)); anything else throws InvalidOperationException naming the offending tool type. Matches Python's "unsupported tool types raise ValueError" contract.

All new public types and members carry the [Experimental] attribute consistent with the rest of the Microsoft.Agents.AI.Foundry package.

The first commit in this PR (Consolidate Foundry chat client decorators into FoundryChatClient) is the prerequisite consolidation work that unified the previous AzureAIProjectChatClient and AzureAIProjectResponsesChatClient decorators into the single FoundryChatClient type now being promoted here, and aligns the User-Agent contract with Python by adding agent-framework-dotnet/{version} stamping and preserving the combined foundry-hosting/agent-framework-dotnet/{version} segment when hosted.

Verification

dotnet build --tl:off --warnaserror on all five changed projects: 0 errors, 0 warnings.
dotnet format --verify-no-changes --verbosity diagnostic via WSL2 + Docker (mcr.microsoft.com/dotnet/sdk:10.0, the CI image): clean on all five projects.
Unit tests: 334/334 (Foundry net10.0), 272/272 (Foundry net472), 229/229 (Foundry.Hosting net10.0). Zero failures.
Integration tests (Foundry.IntegrationTests full suite against the configured project endpoint): 67 total, 44 passed, 0 failed, 23 intentionally skipped. Matches the baseline origin/main exactly. Zero regressions.

Contribution Checklist

The code builds clean without any errors or warnings
The PR follows the Contribution Guidelines
All unit tests pass, and I have added new tests where possible
Is this a breaking change? No. FoundryChatClient was internal and is now public sealed; existing callers see no change. All other surfaces are additive.

github-actions

Automated Code Review

Reviewers: 4 | Confidence: 79%

✓ Correctness

No actionable issues found in this dimension.

✓ Security Reliability

The PR is well-structured with proper input validation, idempotency guards, and graceful fallbacks. Two reliability observations: (1) CreateVectorStoreAsync does not clean up previously-uploaded files if a mid-sequence upload fails, leaving orphaned server resources; (2) In mode 3 (hosted agent endpoint), the materialized AIProjectClient for file/vector-store operations does not propagate the caller's clientOptions (Transport, RetryPolicy, NetworkTimeout), creating an inconsistency with how CreateProjectLevelOpenAIClientFromAgentEndpoint carefully propagates those settings. Neither is a security vulnerability, but the options propagation gap could cause unexpected behavior in testing scenarios.

✓ Test Coverage

No actionable issues found in this dimension.

✗ Design Approach

I found two design-level regressions in the new FoundryChatClient: hosted-endpoint helper calls are built on a project client that drops the caller’s configured pipeline/options, and CreateVectorStoreAsync does not implement the wait-until-ready behavior that its own contract promises. I found one design issue in the new mode-3 helper surface: the tests explicitly acknowledge that hosted-agent file uploads run through a separately materialized AIProjectClient with the default transport, which means the new file/vector-store APIs would bypass caller-suplied transport and pipeline settings on that construction path. The existing repo already has a better pattern for agent-endpoint scenarios that preserves those settings when moving between per-agent and project-level clients.

Automated review by rogerbarreto's agents

Copilot

Pull request overview

This PR consolidates Foundry .NET chat-client plumbing around FoundryChatClient, adds prompt-agent conversion helpers, and expands Foundry file/vector-store helper coverage with tests.

Changes:

Replaces the older AzureAIProject chat-client decorators with FoundryChatClient and adds agent-framework User-Agent stamping.
Adds ToPromptAgentAsync conversion extensions for Foundry-backed agents.
Adds file/vector-store helper APIs and broad unit coverage for construction modes, user-agent behavior, and conversion paths.

Reviewed changes

Copilot reviewed 22 out of 22 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
`dotnet/src/Microsoft.Agents.AI.Foundry/FoundryChatClient.cs`	New unified Foundry chat client plus file/vector-store helpers.
`dotnet/src/Microsoft.Agents.AI.Foundry/FoundryPromptAgentConverter.cs`	Shared implementation for prompt-agent conversion.
`dotnet/src/Microsoft.Agents.AI.Foundry/FoundryAgentExtensions.cs`	Adds `FoundryAgent.ToPromptAgentAsync`.
`dotnet/src/Microsoft.Agents.AI.Foundry/ChatClientAgentFoundryExtensions.cs`	Adds `ChatClientAgent.ToPromptAgentAsync`.
`dotnet/src/Microsoft.Agents.AI.Foundry/AgentFrameworkUserAgentPolicy.cs`	Adds agent-framework User-Agent policy.
`dotnet/src/Microsoft.Agents.AI.Foundry/FoundryAgent.cs`	Routes constructors through `FoundryChatClient`.
`dotnet/src/Microsoft.Agents.AI.Foundry/AIProjectClientExtensions.cs`	Updates extension implementation to use `FoundryChatClient`.
`dotnet/src/Microsoft.Agents.AI.Foundry/RequestOptionsExtensions.cs`	Removes local MEAI User-Agent policy.
`dotnet/src/Microsoft.Agents.AI.Foundry/AzureAIProjectChatClient.cs`	Removes replaced decorator.
`dotnet/src/Microsoft.Agents.AI.Foundry/AzureAIProjectResponsesChatClient.cs`	Removes replaced decorator.
`dotnet/src/Microsoft.Agents.AI.Foundry.Hosting/HostedAgentUserAgentPolicy.cs`	Updates hosted User-Agent upgrade behavior.
`dotnet/tests/Microsoft.Agents.AI.Foundry.UnitTests/FoundryChatClientTests.cs`	Adds coverage for `FoundryChatClient` modes and services.
`dotnet/tests/Microsoft.Agents.AI.Foundry.UnitTests/FoundryChatClientVectorStoreTests.cs`	Adds file/vector-store helper tests.
`dotnet/tests/Microsoft.Agents.AI.Foundry.UnitTests/FoundryPromptAgentConverterTests.cs`	Adds prompt-agent converter tests.
`dotnet/tests/Microsoft.Agents.AI.Foundry.UnitTests/AgentFrameworkUserAgentPolicyTests.cs`	Adds User-Agent policy tests.
`dotnet/tests/Microsoft.Agents.AI.Foundry.UnitTests/MeaiAutoUserAgentVerificationTests.cs`	Adds MEAI auto-stamping regression test.
`dotnet/tests/Microsoft.Agents.AI.Foundry.UnitTests/FoundryAgentTests.cs`	Updates FoundryAgent user-agent and metadata tests.
`dotnet/tests/Microsoft.Agents.AI.Foundry.UnitTests/AIProjectClientExtensionsTests.cs`	Updates extension tests for new chat-client wrapper.
`dotnet/tests/Microsoft.Agents.AI.Foundry.UnitTests/RequestOptionsExtensionsTests.cs`	Removes obsolete local MEAI policy tests.
`dotnet/tests/Microsoft.Agents.AI.Foundry.UnitTests/AzureAIProjectChatClientTests.cs`	Removes tests for deleted decorator.
`dotnet/tests/Microsoft.Agents.AI.Foundry.Hosting.UnitTests/HostedOutboundUserAgentTests.cs`	Extends hosted User-Agent tests.
`dotnet/tests/Foundry.IntegrationTests/FoundryVersionedAgentStructuredOutputRunTests.cs`	Updates skipped-test text to `FoundryChatClient`.

Comments suppressed due to low confidence (4)

dotnet/src/Microsoft.Agents.AI.Foundry/AIProjectClientExtensions.cs:26

Renaming this public extension class is a breaking API change for callers that invoke the extension methods statically (for example, AzureAIProjectChatClientExtensions.AsAIAgent(...)) or reference the type in source/binary compatibility checks. Keep the old public type (for example as an obsolete forwarding partial class) if the PR is intended to be additive.
dotnet/src/Microsoft.Agents.AI.Foundry/FoundryChatClient.cs:45
These public XML docs still describe FoundryChatClient as intentionally internal and say promotion is deferred, which is now false for the newly public type. This will publish misleading API documentation for consumers.

/// The type is intentionally <see langword="internal"/> for now. The public surface remains the
/// existing <c>FoundryAgent</c> and <c>AsAIAgent</c> shapes; promotion is deferred until external
/// callers express need.

dotnet/src/Microsoft.Agents.AI.Foundry/FoundryPromptAgentConverter.cs:81

Use American English in comments: change "synthesise" to "synthesize".

        // Mode 1 (pure responses): synthesise from ChatOptions.

dotnet/src/Microsoft.Agents.AI.Foundry/FoundryPromptAgentConverter.cs:90

Use American English in user-facing error messages: change "synthesise" to "synthesize".

                "ToPromptAgentAsync requires a model id on the agent's ChatOptions to synthesise a prompt agent definition.");

Q-A: poll vector store til status leaves InProgress before return. Exp backoff 250ms-2s. Honor cancel. Q-B: try/catch upload loop. Mid-fail = best-effort DeleteFileAsync on already-uploaded ids. Swallow cleanup errors. Q-C: pinned AgentReference.Version uses GetAgentVersionAsync. Empty/whitespace/'latest' = GetLatest path. Q-D: HostedAgentUserAgentPolicy detects existing combined 'foundry-hosting/...' segment. No double prefix. Q-E: mode-3 vector-store test uses fake transport. No DNS to example.com. Q-F: no shim. Class always [Experimental] (since 8015e00, before dotnet-1.0.0). No compat contract. Callers rename to AIProjectClientExtensions. Verified: 340/340 net10 + 278/278 net472 Foundry unit, 230/230 Foundry.Hosting unit, format clean.

- Replace AzureAIProjectChatClient and AzureAIProjectResponsesChatClient with a single internal sealed FoundryChatClient that covers three modes (pure responses, server-side agent reference, hosted agent endpoint). - Rename AzureAIProjectChatClientExtensions to AIProjectClientExtensions to reflect that it extends AIProjectClient. - All four AsAIAgent extension overloads and both FoundryAgent constructors now construct FoundryChatClient internally so the microsoft.foundry telemetry tag is uniform across paths. - Introduce AgentFrameworkUserAgentPolicy that stamps agent-framework-dotnet/{version} on outbound requests, mirroring the Python agent-framework-python/{version} contract. - Delete the Foundry-local MeaiUserAgentPolicy duplicate; rely on MEAI 10.5.1 to stamp MEAI/{version} automatically. - HostedAgentUserAgentPolicy keeps the combined foundry-hosting/agent-framework-dotnet/{version} segment (Python parity) and upgrades the bare segment in place to avoid duplication. - Tests reorganized: FoundryChatClientTests, AIProjectClientExtensionsTests, AgentFrameworkUserAgentPolicyTests, MeaiAutoUserAgentVerificationTests, plus in-place upgrade unit tests in HostedOutboundUserAgentTests.

…d ToPromptAgentAsync converter - Promote FoundryChatClient from internal sealed to public sealed for Python parity, so .NET developers can hold and pass a FoundryChatClient directly the way Python developers do. - Mode 3 (hosted agent endpoint) now materializes an AIProjectClient from the parsed project root, making GetService<AIProjectClient>() non-null across all three construction modes. This eliminates the per-mode asymmetry that previously hid project-level helpers from agents constructed via an agent endpoint URL. - Add four new instance methods on FoundryChatClient mirroring Python's spec: UploadFileAsync, DeleteFileAsync, CreateVectorStoreAsync (bundles upload + create + wait), DeleteVectorStoreAsync. Single overload each, path-only inputs to start; additional overloads can be added later without breaking callers. All are Experimental, consistent with the rest of the Foundry package. - Add ToPromptAgentAsync extension methods on ChatClientAgent and FoundryAgent for the agent-to-prompt-agent converter described in the Foundry spec. Mode 1 (responses API) synthesizes a DeclarativeAgentDefinition from the agent's ChatOptions; mode 2 (server-side agent reference, version, or record) returns the cached or freshly fetched Definition; mode 3 throws InvalidOperationException because no local definition exists to convert. - Strict AITool to ResponseTool mapping for mode 1: AIFunction becomes CreateFunctionTool with the function's JSON schema; AITool instances that wrap a ResponseTool unwrap via GetService(typeof(ResponseTool)); anything else throws InvalidOperationException naming the offending tool type. Matches the Python spec's unsupported-tools-raise-ValueError contract. - New unit tests: FoundryChatClientVectorStoreTests (22 tests covering all four helpers across the three FoundryChatClient construction modes plus validation and cancellation), FoundryPromptAgentConverterTests (16 tests covering both extension entry points across mode 1 synthesis, mode 2 cached and fetched paths, all failure modes, and a Python-parity guard asserting both extensions produce equivalent definitions for equivalent inputs), plus four new tests in FoundryChatClientTests for the mode 3 AIProjectClient materialization.

…point ctor After Plan #2's mode-3 AIProjectClient materialization, the inner FoundryChatClient already exposes a project-level AIProjectClient (via GetService) that internally provides the project-level ProjectOpenAIClient via GetProjectOpenAIClient(). FoundryAgent's agent-endpoint constructor was still independently constructing a second project-level ProjectOpenAIClient via the now-redundant CreateProjectLevelOpenAIClientFromAgentEndpoint helper — two handles to the same logical resource. Refactor: the agent-endpoint constructor now reads the inner FoundryChatClient's materialized AIProjectClient via base.GetService(typeof(AIProjectClient)) and derives the project-level ProjectOpenAIClient from it. The dead helper on both FoundryAgent (private static wrapper) and FoundryChatClient (the actual implementation) is removed. The user-supplied per-agent ClientPipelineOptions primitives (Transport, RetryPolicy, NetworkTimeout, UserAgentApplicationId) are propagated into the materialized AIProjectClientOptions so test-injected transports and explicit retry / timeout / user-agent settings reach the project-level pipeline — preserving the behavior the dead helper used to provide. Updated AgentEndpointConstructor_GetServiceAIProjectClient_ReturnsNull to its now-correct counterpart AgentEndpointConstructor_GetServiceAIProjectClient_ReturnsNonNull, since after Plan #2 the agent-endpoint ctor surfaces a non-null AIProjectClient (per user direction in Plan #2 Q2).

…ryAgent Both _aiProjectClient and _projectOpenAIClient fields on FoundryAgent were redundant: - _aiProjectClient: FoundryAgent's GetService<AIProjectClient> override returned this field, but DelegatingAIAgent.GetService → ChatClientAgent.GetService → FoundryChatClient.GetService<AIProjectClient> already returns the same instance through the delegating chain. Field + override are pure duplication. - _projectOpenAIClient: only used by FoundryAgent's own GetService<ProjectOpenAIClient> override and by CreateConversationSessionAsync. Per user direction, ProjectOpenAIClient is no longer exposed via GetService on either FoundryChatClient or FoundryAgent — callers retrieve it from the AIProjectClient themselves (aiProjectClient.GetProjectOpenAIClient()) the same way the framework does internally. This eliminates the mode-3 asymmetry where the chat client's stored ProjectOpenAIClient was per-agent (URL /agents/{name}/endpoint/protocols/openai) while the agent's was project-level. Refactor: - Delete both fields on FoundryAgent and the GetService override. - Delete the ProjectOpenAIClient branch from FoundryChatClient.GetService. - CreateConversationSessionAsync now resolves AIProjectClient at call time via this.GetService<AIProjectClient>() and derives the conversations client from it. - Update FoundryChatClient tests that asserted on GetService<ProjectOpenAIClient> to assert Null (deliberate removal). - Update FoundryAgent tests AgentEndpointConstructor_GetServiceProjectOpenAIClient_ReturnsNonNull and ProjectEndpointConstructor_GetServiceProjectOpenAIClient_ReturnsNonNull to ...ReturnsNull, and rewrite AgentEndpointConstructor_PropagatesUserAgentApplicationId_ToProjectLevelClient to look up AIProjectClient instead. No production code (only tests) referenced GetService<ProjectOpenAIClient>, so this is a safe surface reduction. Net: 30 insertions, 61 deletions; FoundryAgent shrinks to a pure delegator with only the two convenience methods (CreateSessionAsync, CreateConversationSessionAsync) on top of the delegating chain.

… for mode 2 The previous name implied a mode 3 only property tied to the hosted-agent endpoint URL. Today only hosted endpoints surface this name, but conceptually an agent name exists for every server-side agent the client talks to. Renaming to AgentName makes the property general-purpose and ready for future modes where the same chat client may target other server-side agent shapes that are not necessarily 'hosted'. Mode 2 (server-side agent reference) now mirrors AgentReference.Name into AgentName so callers have a uniform handle regardless of construction mode: * Mode 1 (pure responses): AgentName is null. There is no agent. * Mode 2 (AgentReference): AgentName == AgentReference.Name. * Mode 3 (agent endpoint URL): AgentName is parsed from the URL segment as before. Converter discriminator update: FoundryPromptAgentConverter previously used 'HostedAgentName is not null' to detect mode 3 and reject it. Now that mode 2 also populates AgentName, the mode 3 guard moves to the end of the resolution chain and uses the unambiguous 'AgentName is set AND no AgentReference exists' test. The user-visible error message and behavior are preserved. Dead-state cleanup spotted during format verify: * IDE0052 surfaced that FoundryChatClient._projectOpenAIClient is never read since the prior refactor stopped exposing ProjectOpenAIClient via GetService and rewired CreateConversationSessionAsync to resolve the AIProjectClient through the delegating chain. The field is deleted and its three ctor assignments removed. * HostedAgentEndpointInner.PerAgentClient only existed to plumb the per-agent ProjectOpenAIClient into that now-deleted field, so the property and its ctor parameter are removed. The local 'perAgentClient' variable inside BuildHostedAgentEndpointInner is still needed to derive the inner IChatClient, but no longer escapes the helper. Tests: * Mode1_PureResponses_ReturnsNullForAgentSpecificServices now also asserts AgentName is null. * New Mode2_AgentReference_PopulatesAgentNameFromAgentReference asserts the mode 2 mirror. * Mode3_HostedAgentEndpoint_ParsesAgentNameFromUrl renamed assertion target HostedAgentName to AgentName. Verification: 335/335 net10.0, 273/273 net472 Foundry unit; 229/229 Foundry.Hosting unit; format-verify (WSL2 + Docker mcr.microsoft.com/dotnet/sdk:10.0) clean on Microsoft.Agents.AI.Foundry.

…oint Three FoundryChatClient construction modes now have one canonical noun used everywhere. * Responses Agent (Mode 1): inline ChatClientAgent, project-level Responses API, no server-side def. * Prompt Agent (Mode 2): server-side ProjectsAgentDefinition invoked by AgentReference. * Agent Endpoint (Mode 3): per-agent URL /agents/{name}/endpoint/protocols/openai. Hosted-or-not. 'Hosted' stays the kind of agent (Microsoft.Agents.AI.Foundry.Hosting). Not synonym of Mode 3. Rings: 1. XML docs + error messages use canonical names. en-GB to en-US: centralises, synthesise. 2. HostedAgentEndpointInner -> AgentEndpointInner, BuildHostedAgentEndpointInner -> BuildAgentEndpointInner. 3. Tests: Mode1_PureResponses_* -> Mode1_ResponsesAgent_*, Mode2_AgentReference_* -> Mode2_PromptAgent_*, Mode3_HostedAgentEndpoint_* -> Mode3_AgentEndpoint_*. Pure rename. No behavior change. 335/335 net10 + 273/273 net472 unit, format clean.

Q-A: poll vector store til status leaves InProgress before return. Exp backoff 250ms-2s. Honor cancel. Q-B: try/catch upload loop. Mid-fail = best-effort DeleteFileAsync on already-uploaded ids. Swallow cleanup errors. Q-C: pinned AgentReference.Version uses GetAgentVersionAsync. Empty/whitespace/'latest' = GetLatest path. Q-D: HostedAgentUserAgentPolicy detects existing combined 'foundry-hosting/...' segment. No double prefix. Q-E: mode-3 vector-store test uses fake transport. No DNS to example.com. Q-F: no shim. Class always [Experimental] (since 8015e00, before dotnet-1.0.0). No compat contract. Callers rename to AIProjectClientExtensions. Rebase onto origin/main reconciliation: aad20c2 added public AsAIAgent(this AIProjectClient, Uri agentEndpoint, ...) extension that calls an internal FoundryAgent(AIProjectClient, Uri, ...) ctor. Reintroduced that ctor + a new FoundryChatClient(AIProjectClient, Uri, ProjectOpenAIClientOptions?) overload that reuses the supplied AIProjectClient's pipeline (via GetProjectResponsesClientForAgentEndpoint) instead of stamping a fresh credential. Verified: 346/346 net10 + 284/284 net472 Foundry unit, 230/230 Foundry.Hosting unit, format clean.

…rStore/DeleteVectorStore 4 thin forwarders on FoundryAgent that route to the inner FoundryChatClient's helpers via agent.GetService<FoundryChatClient>().X(). Live in existing FoundryAgentExtensions.cs alongside ToPromptAgentAsync. Throws InvalidOperationException when agent does not expose a FoundryChatClient via GetService (same pattern as ToPromptAgentAsync). Unit tests: FoundryAgentExtensionsTests covers all 4 forwarders + null-agent ArgumentNullException for each. 8 new tests, 354/354 net10 + 292/292 net472. Integration tests: parallel FoundryAgentExtensionsTests under Foundry.IntegrationTests mirrors the existing CreateAgent_CreatesAgentWithVectorStoresAsync shape (upload -> create vector store -> FileSearch tool answers question -> cleanup), but routes every helper call through the new FoundryAgent extensions. 4 new IT tests, all verified pass live against the real Foundry project (12-30s each). Skipped by default like the existing vector-store IT.

#1 (FoundryAgent.cs:139): drop unused aiProjectClient param from internal FoundryAgent(AIProjectClient, ChatClientAgent) ctor. Was discarded after null-check. Inner FoundryChatClient already surfaces AIProjectClient via GetService. 3 call sites in AIProjectClientExtensions updated. #2 (FoundryChatClient.cs:376): add pollingTimeout param to CreateVectorStoreAsync. Defaults to 5 min, configurable, Timeout.InfiniteTimeSpan disables. Throws TimeoutException with vector store id and elapsed seconds when bound exceeded. CancellationToken still wins. New unit test PollingTimeout_ThrowsTimeoutExceptionAsync. FoundryAgentExtensions forwarder updated to plumb the new param. Verified: 355/355 net10 + 293/293 net472 Foundry unit, 230/230 Foundry.Hosting unit, format clean.

Copilot AI review requested due to automatic review settings May 18, 2026 22:55

moonbox3 added the .NET label May 18, 2026

Copilot started reviewing on behalf of rogerbarreto May 18, 2026 22:57 View session

github-actions Bot reviewed May 18, 2026

View reviewed changes

Copilot AI reviewed May 18, 2026

View reviewed changes

rogerbarreto added 6 commits May 19, 2026 20:41

rogerbarreto force-pushed the issues/to-prompt-agent branch from ead2a15 to 0a53130 Compare May 19, 2026 19:52

rogerbarreto temporarily deployed to integration May 19, 2026 19:58 — with GitHub Actions Inactive

rogerbarreto force-pushed the issues/to-prompt-agent branch from 0a53130 to 4725e03 Compare May 20, 2026 06:32

rogerbarreto temporarily deployed to integration May 20, 2026 06:34 — with GitHub Actions Inactive

rogerbarreto self-assigned this May 20, 2026

rogerbarreto marked this pull request as ready for review May 20, 2026 06:36

SergeyMenshykh approved these changes May 20, 2026

View reviewed changes

Comment thread dotnet/src/Microsoft.Agents.AI.Foundry/FoundryAgent.cs Outdated

Comment thread dotnet/src/Microsoft.Agents.AI.Foundry/FoundryChatClient.cs

rogerbarreto temporarily deployed to integration May 20, 2026 13:49 — with GitHub Actions Inactive

peibekwe approved these changes May 20, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

.NET: Promote FoundryChatClient to public, add file/vector-store helpers and ToPromptAgentAsync converter#5940

.NET: Promote FoundryChatClient to public, add file/vector-store helpers and ToPromptAgentAsync converter#5940
rogerbarreto wants to merge 9 commits into
microsoft:mainfrom
rogerbarreto:issues/to-prompt-agent

rogerbarreto commented May 18, 2026 •

edited

Loading

Uh oh!

github-actions Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

rogerbarreto commented May 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Motivation and Context

Description

Verification

Contribution Checklist

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Automated Code Review

✓ Correctness

✓ Security Reliability

✓ Test Coverage

✗ Design Approach

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

rogerbarreto commented May 18, 2026 •

edited

Loading