Highlights
- Native Agents have been gaining typed Decisions through
agent.decide(), callback-boundctx.decide(), andOpenAIDecisions. These calls have been taking explicit input and returning a boolean, a constrained choice, or a supported structured value.DecisionHandoffhas been using Decisions to choose among the Agents configured for a native text handoff. Typed Decisions - Native Agents have been supporting application-owned model backends through
ResponsesModel,ChatCompletionsModel, andAiSdkModel, including streamed output within each adapter's limits. Provider and model configuration - Native Realtime and voice have been expanding across Node.js, browsers, React Native, and Workers. The new controls have been covering audio input, response timing, history edits, usage, and SIP or browser call setup. Native voice
- Native LocalStorage has been gaining named profiles, history queries, edits, and forks. The SDK has also been adding memory, artifact, and UI helpers for sandbox workflows. Local profiles · History and checkpoints
- Local executors have been gaining read-only workspaces and opt-in
trusted_workspace_writeon Linux and macOS. Trusted workspace writes have been allowing broader host reads while limiting writes to granted roots. Applications have also been opting intoAGENTS.mddiscovery. Local execution · Project guidance
Upgrade actions
- Tool callbacks can now overlap. Native catalogs with only automatic tools have been admitting callbacks concurrently by default. Shared mutable state or side effects can race. Setting
maxFunctionConcurrency: 1onagent.run()oragent.session()has been preserving one-at-a-time admission per turn. Function admission Session.enqueue()has been rejecting the previously ignoredifBusyoption.session.enqueue(input)has been retaining queueing.session.submit(input, { ifBusy: 'reject' })has been rejecting while the Session is busy. Session methodsAgentOptions<Context, Output>has been requiring a matchingoutputTypefor non-stringOutputtypes. Output configuration- Serialized Classic sandbox restores have been requiring trusted bindings from application configuration. UnixLocal restores have been using
resumeAuthority.workspaceRootPathorresumeAuthority.localSnapshotPathwhere applicable. UnixLocal and Docker remote snapshot restores have been requiring a separately trustedresumeAuthority.remoteSnapshotId. Sandbox resume and snapshots - TypeScript code with exhaustive switches has been gaining new observation variants and the
http_jsonrequest mode to handle. Applications injecting a client into the newOpenAIDecisionsadapter have been requiringopenai7.30.0 or later. Provider and model configuration · Typed Decisions - Bundled installations have been using five matching packages from one version and platform. Checkpoint restores have been requiring the same native Codex revision and the matching trusted declarations, output settings, and executor policy. Local bundle installation · Checkpoint compatibility
Added
- Native tools have been gaining namespaces, concurrency limits, caller restrictions, managed approvals, client-side tool search, and configurable error formatting. Native MCP has been adding discovery filters, cache controls, per-tool approvals, and borrowed aliases. Native tools · MCP configuration
- Native provider options have been adding scoped headers and query parameters, explicit WebSocket routes, provider-managed history, buffered Responses JSON, hosted prompts, and retry controls. Native text sessions have been gaining registered Sign in with ChatGPT and saved Codex CLI login routes. Provider configuration
beforeCompletehas been letting applications inspect proposed output and continue or stop the current turn.turn.acceptedText()has been exposing exact accepted text prefixes during generation. Accepted output
Fixed
- Native Responses HTTP requests, provider-history reads, and Responses WebSocket handshakes have been identifying the SDK as
openai_agents_jsand reporting the installed package version inUser-Agent. Request identity fix - Native ESM and CommonJS imports from one SDK installation have been sharing class and tool identity on supported Node.js configurations. Realtime Node.js entry points have also been sharing one implementation. Module identity
- Native cleanup and recovery have been preserving terminal-tool ownership, child settlement, cancellation, MCP callback errors, and accepted executor grants across supported continuations. Recovery
Bundle installation
The prerelease has been targeting Linux x64, Linux ARM64, macOS Apple silicon, and Windows x64. The Linux bundles have been requiring glibc 2.39 or later and OpenSSL 3. The Windows x64 bundle has been requiring the x64 Visual C++ Redistributable.
| Platform | Starter bundle | SHA-256 checksums |
|---|---|---|
| Linux x64 | Download starter | Checksums |
| Linux ARM64 | Download starter | Checksums |
| macOS Apple silicon | Download starter | Checksums |
| Windows x64 | Download starter | Checksums |
The starter checks have been using Node.js 24. The SHA256SUMS-<platform> file from the release has been providing the expected archive checksum. The following commands have been installing the starter from its extracted agents-starter directory and running the greeting with OPENAI_API_KEY set. The greeting has been making a live model request.
npm ci --ignore-scripts
node hello.mjsThe starter has been bundling the matching five SDK tarballs. For an existing application, the local bundle guide has been showing where to copy the tarballs and how to keep their versions aligned. The table has been listing the version and platform in each release asset name. Local bundle installation