You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ported the .NET feature-usage User-Agent telemetry from microsoft/agent-framework#7709 (commit 43b3ce6027c49bdbcd422dc3959e0bbe28cb833f) into the Go SDK. This adds a public telemetry.FeatureUsage API for process-wide feature tracking, threads feature-usage configuration through the OpenAI and Foundry providers, and aligns provider User-Agent behavior so approved Azure OpenAI and Foundry requests can emit the (feat=v1...) token while stale feature tokens are stripped when they should not be sent.
Yes. The OpenAI provider previously prepended agent-framework-go/... to requests sent to any configured endpoint. It now only emits the Agent Framework User-Agent prefix and feature token for approved Azure OpenAI origins, matching the upstream .NET behavior; unapproved/custom OpenAI origins keep the OpenAI SDK User-Agent without the Agent Framework prefix. This is acceptable in the beta Go SDK because it improves parity with the upstream contract and narrows telemetry to the intended destinations.
Tests and Examples
go test ./telemetry ./internal/telemetry ./provider/openaiprovider ./provider/foundryprovider
Added feature-usage API tests plus OpenAI and Foundry User-Agent coverage for approved and unapproved origins
Notes
This PR intentionally keeps the port narrow: it adds the public feature-usage API and wires the existing Go OpenAI/Foundry User-Agent surfaces that correspond to the selected upstream change.
Broader feature-index adoption across additional Go packages can follow separately if maintainers want the full .NET registry coverage beyond the currently affected providers.
This was originally intended as a pull request, but GitHub Actions is not permitted to create or approve pull requests in this repository.
The changes have been pushed to branch copilot/dotnet-port-api-feature-usage-382d915f78f1d7f6.
To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ
Summary
Ported the .NET feature-usage User-Agent telemetry from microsoft/agent-framework#7709 (commit 43b3ce6027c49bdbcd422dc3959e0bbe28cb833f) into the Go SDK. This adds a public
telemetry.FeatureUsageAPI for process-wide feature tracking, threads feature-usage configuration through the OpenAI and Foundry providers, and aligns provider User-Agent behavior so approved Azure OpenAI and Foundry requests can emit the(feat=v1...)token while stale feature tokens are stripped when they should not be sent.Ported .NET PRs
Breaking Changes
Yes. The OpenAI provider previously prepended
agent-framework-go/...to requests sent to any configured endpoint. It now only emits the Agent Framework User-Agent prefix and feature token for approved Azure OpenAI origins, matching the upstream .NET behavior; unapproved/custom OpenAI origins keep the OpenAI SDK User-Agent without the Agent Framework prefix. This is acceptable in the beta Go SDK because it improves parity with the upstream contract and narrows telemetry to the intended destinations.Tests and Examples
go test ./telemetry ./internal/telemetry ./provider/openaiprovider ./provider/foundryproviderNotes
Note
This was originally intended as a pull request, but GitHub Actions is not permitted to create or approve pull requests in this repository.
The changes have been pushed to branch
copilot/dotnet-port-api-feature-usage-382d915f78f1d7f6.Click here to create the pull request
To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ
Show patch preview (500 of 997 lines)