[Michelle Clayton (michelle-clayton-work)]

Summary

Added openaiprovider.ResponsesIncludeReasoningEncryptedContent(bool) so Go Responses agents can opt out of automatically requesting reasoning.encrypted_content while store=false, matching the split control that upstream .NET added around stateless stored-output handling. The existing default behavior stays intact, and the Foundry provider docs/tests now cover the same run-option passthrough.

Upstream commit: 4ca093371ebbf42b549093aa73f7788d7b7416a0 (microsoft/agent-framework@4ca0933).

Ported .NET PRs

• .NET: Add Options for Hosted Agent to Allow Backend Storage agent-framework#7572 - Add hosted Responses storage options, including independent control over encrypted reasoning replay when stored output is disabled.

Breaking Changes

No. Existing store=false behavior still auto-includes encrypted reasoning content by default; this change only adds a new public opt-out control.

Tests and Examples

• go test ./provider/openaiprovider ./provider/foundryprovider
• Added targeted coverage for direct OpenAI Responses usage and Foundry RunOptions passthrough with the new option.

Notes

• Related Go parity already landed in Add DisableStoreOutput for Responses agents #428 (DisableStoreOutput) and Carry reasoning EncryptedContent through the OpenAI Responses streaming path for store=false replay #683 (carrying encrypted reasoning content for store=false replay). This PR ports the remaining public control surfaced by .NET #7572 without changing the default behavior.
• No example changes were needed for this narrow provider option.

Generated by .NET to Go API Porting Agent · gpt54 · 230.1 AIC · ⌖ 9.67 AIC · ⊞ 24.2K · ◷

Closes #827

[Copilot]

🟢 Approval recommended

The new option is correctly wired behind existing store=false behavior, preserves defaults, and includes targeted coverage for both direct OpenAI and Foundry passthrough scenarios.

Pull request overview

Adds a new per-run OpenAI Responses provider option to control whether reasoning.encrypted_content is automatically included when Responses output storage is disabled (store=false), aligning Go behavior with upstream .NET’s split control while keeping the existing default behavior unchanged.

Changes:

• Introduced openaiprovider.ResponsesIncludeReasoningEncryptedContent(bool) and gated the automatic include behavior behind it (default true).
• Documented the default include behavior and the opt-out mechanism for both OpenAI and Foundry agent configs.
• Added targeted tests covering direct OpenAI Responses usage and Foundry RunOptions passthrough.

File summaries

File	Description
provider/openaiprovider/responses.go	Adds the new option type + helper and gates automatic reasoning.encrypted_content inclusion on the option.
provider/openaiprovider/responses_test.go	Adds a test ensuring include is omitted when the option disables automatic encrypted reasoning include while store=false.
provider/openaiprovider/chat.go	Updates DisableStoreOutput docs to mention the default encrypted reasoning include and the per-run opt-out.
provider/foundryprovider/agent.go	Updates Foundry agent config docs to describe the default include behavior and the opt-out via RunOptions.
provider/foundryprovider/agent_test.go	Adds a test verifying Foundry RunOptions can disable the automatic include passthrough.

Review details

• Files reviewed: 5/5 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

Scope: public API

Changed Go contract: New exported openaiprovider.ResponsesIncludeReasoningEncryptedContent(bool) agent.Option, consumed via agent.GetOption in responsesBuildCompletionParams (provider/openaiprovider/responses.go) and documented on AgentConfig.DisableStoreOutput in both provider/openaiprovider/chat.go and provider/foundryprovider/agent.go.

Upstream evidence reviewed: dotnet/src/Microsoft.Agents.AI.Foundry.Hosting/FoundryResponsesOptions.cs (IncludeReasoningEncryptedContent, default true, applies only while AllowStoredOutputEnabled is false) and dotnet/src/Microsoft.Agents.AI.Foundry.Hosting/InputConverter.cs (DisableStoredOutput/LocalDisableStoredOutput, which conditionally adds IncludedResponseProperty.ReasoningEncryptedContent only when the flag is true), from commit 4ca093371ebbf42b549093aa73f7788d7b7416a0 (upstream PR microsoft/agent-framework#7572).

Result: aligned. The Go option preserves the existing default behavior (auto-include reasoning.encrypted_content while store=false) and adds an opt-out matching the semantics and default of .NET's IncludeReasoningEncryptedContent (default true, effective only when output storage is disabled). Naming is idiomatic (Go functional option vs. .NET settable property) but conceptually equivalent. Tests in responses_test.go and foundryprovider/agent_test.go verify both the default and opt-out paths. No divergence found.

Generated by Go API Consistency Review Agent for #966 · copilot · auto · 28.9 AIC · ⌖ 6.44 AIC · ⊞ 9.5K · ◷