openai-dotnet — Engineering Performance

Add ApplyPatchTool for Responses (#1067)

Add support for web search action (#1064)

[Skills] Add Skills API support (#1077) * [Skills] Add Skills API support

Generate ListChatCompletions with pagination (#549)

Prepare 2.2.0-beta.2 release (Part 1) (#349)

Add ChatTools and ResponseTools helper classes (#422) This PR adds functionality for managing OpenAI function tools in chat completions and responses, implementing two utility classes: `ChatTools` and `ResponseTools`. ### Key Features - Unified Tool Management - Both classes handle local and remote MCP (Model Context Protocol) tools - Support for both static method tools and remote MCP server tools - Vectorized tool lookup using embeddings for smart tool filtering - Tool Registration - Local tool registration via reflection from static methods - Remote tool registration from MCP servers - Tool Filtering - Vector-based tool filtering when an `EmbeddingClient` is provided - Configurable similarity thresholds - Customizable maximum tool limits

[Diagnostics] Add Stainless telemetry headers (#1260) * [Diagnostics] Add Stainless telemetry headers Outgoing requests now carry six structured headers describing the SDK and the platform that issued them, bringing the .NET library to parity with the other official OpenAI SDKs: X-Stainless-Lang csharp X-Stainless-Package-Version 2.12.0 X-Stainless-Runtime dotnet X-Stainless-Runtime-Version 8.0.11 X-Stainless-OS Windows X-Stainless-Arch x64 These restate, in a machine-parseable form, information already present in the User-Agent, plus the process CPU architecture, so consumers no longer have to parse the user agent string. The User-Agent header itself is unchanged, as Azure services depend on its current shape. System.ClientModel's UserAgentPolicy could not be reused: it exposes only the composed string, and the structured inputs behind it are internal. Parsing that string back apart would reintroduce exactly the fragility this change exists to remove, so the values are derived directly. Also adds an opt-out, via the OpenAI.TelemetryDisabled AppContext switch or the OPENAI_TELEMETRY_DISABLED environment variable. When set, the library sends neither these headers nor the User-Agent it would otherwise add; a User-Agent supplied by the caller is still honored, as are the Authorization, OpenAI-Organization, and OpenAI-Project headers. The setting is read once when a pipeline is built, matching how the experimental OpenTelemetry switch behaves. Implementation notes: - Headers are applied by the single shared per-call policy that every client is built on, so no client can be constructed without them. - Values are computed once per process and are never allowed to fail a request; every path degrades to "unknown" rather than throwing. - Platform detection is netstandard2.0-safe. OSPlatform.FreeBSD and the mobile and browser platforms do not exist in that reference assembly, so they are created by name. Android and the Apple mobile platforms are evaluated before Linux and macOS, because Mono and legacy Xamarin report them as their base platform. - Free-form platform text is normalized to printable ASCII and bounded in length. The package version is not: it is reproduced verbatim so that it always matches the User-Agent, and falls back to "unknown" if it could not be transmitted unaltered, rather than being rewritten into a value that would silently disagree. - Realtime WebSocket handshakes deliberately omit these headers, matching the other official OpenAI SDKs. Regular HTTP requests from RealtimeClient include them. Existing session recordings are unaffected. A RemoveHeaderSanitizer in OpenAIRecordedTestBase strips the headers before the proxy matches a playback request and before a recording is written, so nothing needed to be re-recorded and future recordings will not capture machine-specific values. Coverage lives in 80 new mock-based tests spanning normalization, every OS and architecture branch, never-throw behavior, header application and override, retry de-duplication, and opt-out scope, plus a guard asserting the package version header never drifts from the User-Agent. Measured cost is roughly 590 ns, 912 bytes, and 183 wire bytes per request. No public API change and no new dependencies. * Addressing PR feedback * Addressing additional PR feedback. * Removing arbitrary length for ApplicationId segment of the User-Agent header and allowing a more reasonable 512 characters. * Renaming AppContext switch for telemetry opt-out to better follow naming patterns. * Updating to avoid creating telemetry details when opt-out is active.

Add `ResponseItem` constructors (#625) All the classes derived from `ResponseItem` now have public constructors, and these constructors are generated. A side effect of making these classes behave as both, inputs and outputs, was that their required properties got setters. Setters make sense when the values of these properties can be updated, but in this particular case they should only be settable at construction time. This is a limitation in the code generator being tracked by the following issue: 🔗 https://github.com/microsoft/typespec/issues/5175#issuecomment-3222039076

Generate GetChatCompletionMessages with pagination (#569)

[Audio] Add ChunkingStrategy for audio transcription (#1036) * [Audio] Add ChunkingStrategy for audio transcription