Skip to content

fix(deps): update dependency @openai/agents-extensions to ^0.11.0#111

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/openai-agents-extensions-0.x
Open

fix(deps): update dependency @openai/agents-extensions to ^0.11.0#111
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/openai-agents-extensions-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 11, 2026 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@openai/agents-extensions (source) ^0.8.0 → ^0.11.0 age confidence

Release Notes

openai/openai-agents-js (@​openai/agents-extensions)

v0.11.4

Compare Source

What's Changed

Documentation & Other Changes

Full Changelog: openai/openai-agents-js@v0.11.3...v0.11.4

v0.11.3

Compare Source

What's Changed

Documentation & Other Changes

Full Changelog: openai/openai-agents-js@v0.11.2...v0.11.3

v0.11.2

Compare Source

What's Changed

Documentation & Other Changes

New Contributors

Full Changelog: openai/openai-agents-js@v0.11.1...v0.11.2

v0.11.1

Compare Source

What's Changed

Documentation & Other Changes

New Contributors

Full Changelog: openai/openai-agents-js@v0.11.0...v0.11.1

v0.11.0

Compare Source

Key Changes

RealtimeAgent's default is now gpt-realtime-2

Since this version, the default model for RealtimeAgents is gpt-realtime-2: https://developers.openai.com/api/docs/models/gpt-realtime-2

Sandbox local source materialization change

In this version, sandbox local source materialization keeps LocalFile.src and LocalDir.src within the materialization baseDir unless the source path is covered by Manifest.extraPathGrants. The baseDir is the SDK process current working directory when the manifest is applied; relative local sources are resolved from that directory, while absolute local sources must already be inside it or under an explicit grant. This closes a local artifact boundary issue, but it can affect applications that intentionally copy trusted host files or directories from outside that base directory into a sandbox workspace.

import { Manifest, localDir, skills } from '@​openai/agents/sandbox';
import { localDirLazySkillSource } from '@​openai/agents/sandbox/local';
import { dirname, join } from 'node:path';
import { fileURLToPath } from 'node:url';

// Outside the base dir
const sharedSkillsDir = '/opt/company/agent-skills';

// Under the base dir
const appRoot = dirname(fileURLToPath(import.meta.url));
const repoDir = join(appRoot, 'repo');

const manifest = new Manifest({
  // Having extraPathGrants for the path outside the baseDir is now required
  extraPathGrants: [
    {
      path: sharedSkillsDir,
      readOnly: true,
      description: 'Shared skill bundle.',
    },
  ],
  entries: {
    // This one doesn't need extraPathGrants
    repo: localDir({ src: repoDir }),
  },
});

const skillCapability = skills({
  lazyFrom: localDirLazySkillSource({
    src: sharedSkillsDir,
  }),
});

What's Changed

Documentation & Other Changes

Full Changelog: openai/openai-agents-js@v0.10.1...v0.11.0

v0.10.1

Compare Source

What's Changed

Documentation & Other Changes

Full Changelog: openai/openai-agents-js@v0.10.0...v0.10.1

v0.10.0

Compare Source

Key Changes

Default model change

In this version, the SDK default model is now gpt-5.4-mini instead of gpt-4.1. This could affect agents and runs that do not explicitly set a model. Because the new default is a GPT-5 model, implicit default model settings now include GPT-5 defaults such as reasoning.effort="none" and verbosity="low".

The new default model should work better for most use cases (see the report at #​1248), but if you need to keep the previous default model behavior for some reasons, set a model explicitly on the agent or run config or set the OPENAI_DEFAULT_MODEL environment variable.

maxTurns configuration

This version adds a new option maxTurns=null to disable the Agents SDK run turn limit while preserving the existing default of DEFAULT_MAX_TURNS (10) when maxTurns is omitted.

Tool execution concurrency

This version adds a new SDK-side runtime configuration for local function tool execution concurrency: toolExecution.maxFunctionToolConcurrency on RunConfig, preserves default behavior when unset. The change keeps provider-side ModelSettings.parallelToolCalls separate from SDK-side local execution scheduling.

Server-prefixed MCP tool naming

This version adds a new option MCPConfigin Agent to align with the Python SDK. When Its includeServerInToolNames is set to true, the SDK includes the MCP server name in the tool name to prevent tool name conflicts with other MCP servers.

What's Changed

Documentation & Other Changes

Full Changelog: openai/openai-agents-js@v0.9.1...v0.10.0

v0.9.1

Compare Source

What's Changed

Documentation & Other Changes

Full Changelog: openai/openai-agents-js@v0.9.0...v0.9.1

v0.9.0

Compare Source

What's Changed

Sandbox Agents

This release adds Sandbox Agents, a beta SDK surface for running agents with persistent workspaces and sandbox-backed capabilities in JavaScript.

Sandbox agents build on the existing Agent, Runner, and run flow, while adding workspace manifests, sandbox sessions, capabilities, snapshots, memory, and resume support. They let agents inspect files, run commands, edit repositories, apply patches, generate artifacts, and continue work across runs.

Refer to the Sandbox Agents guide and examples/sandbox/ for more details.

Key additions include:

  • SandboxAgent, exported from @openai/agents/sandbox, with sandbox defaults such as defaultManifest, baseInstructions, capabilities, and runAs.
  • Manifest, a workspace contract for synthetic files and directories, local files and directories, Git repositories, environment, users, groups, permissions, and mounts.
  • SandboxRunConfig, which wires sandbox clients, live sessions, serialized session resume, manifest overrides, snapshots, and materialization limits into each run.
  • Built-in capabilities for filesystem access, shell access, patching and editing, image inspection, lazy skills, memory, and compaction.
  • Sandbox-aware RunState serialization for resuming runner-managed sandbox sessions.
Sandbox Clients and Hosted Providers

Sandbox agents support local, containerized, and hosted execution backends:

  • UnixLocalSandboxClient for local development.
  • DockerSandboxClient for container isolation and image parity.
  • Hosted sandbox clients for Blaxel, Cloudflare, Daytona, E2B, Modal, Runloop, and Vercel through @openai/agents-extensions/sandbox/* subpath exports.

Provider-specific examples are available under examples/sandbox/extensions/.

Workspaces, Snapshots, Resume, and Memory

This release adds a workspace model for sandbox sessions, including synthetic files and directories, local files and directories, Git repositories, local bind mounts, Docker volume strategies, and typed remote mounts where supported by the selected backend.

It also adds local and remote snapshot store interfaces for carrying workspace contents across runs, plus runner-managed resume through serialized sandbox session state.

Sandbox memory lets future sandbox-agent runs learn from prior runs by storing extracted lessons in the workspace, injecting concise summaries into later runs, and supporting progressive disclosure through deeper rollout summaries. Memory supports read-only and generate-enabled modes, live updates, automatic generation when sessions are flushed, multi-turn grouping, separate memory layouts, and pluggable MemoryStore implementations.

Examples

A new examples/sandbox/ suite demonstrates:

  • Basic SandboxAgent execution with a manifest.
  • Unix-local and Docker sandbox runners.
  • Interactive Unix-local PTY usage.
  • Sandbox handoffs and sandbox agents as tools.
  • Host-defined tools combined with sandbox agents.
  • Filesystem, shell, image, patch, compaction, lazy skill, and memory capabilities.
  • Snapshot-based resume and multi-agent or multi-turn memory.
  • Hosted provider runners for Blaxel, Cloudflare, Daytona, E2B, Modal, Runloop, and Vercel.
Runtime, Tracing, and Model Plumbing

The release includes the runtime plumbing needed for sandbox agents to work naturally inside the JavaScript SDK:

  • Runner-managed sandbox preparation, capability binding, lifecycle handling, cleanup, and resume.
  • Per-agent sandbox session tracking for handoffs and agents-as-tools flows.
  • Public sandbox agent identity preservation across model filters and runtime hooks.
  • Sandbox operation spans for session startup, command execution, filesystem work, snapshots, memory, and provider operations.
  • runAs support for compatible shell and filesystem operations.
  • Remote sandbox concurrency limits for manifest and local directory materialization.

What's Changed

Documentation & Other Changes

Full Changelog: openai/openai-agents-js@v0.8.5...v0.9.0

v0.8.5

Compare Source

What's Changed

Documentation & Other Changes

New Contributors

Full Changelog: openai/openai-agents-js@v0.8.4...v0.8.5

v0.8.4

Compare Source

What's Changed

Documentation & Other Changes

New Contributors

Full Changelog: openai/openai-agents-js@v0.8.3...v0.8.4

v0.8.3

Compare Source

What's Changed

Documentation & Other Changes

Full Changelog: openai/openai-agents-js@v0.8.2...v0.8.3

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • "before 9am on Monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/openai-agents-extensions-0.x branch 3 times, most recently from 85191bd to dafb5da Compare May 14, 2026 08:46
@renovate renovate Bot force-pushed the renovate/openai-agents-extensions-0.x branch from dafb5da to caad4c3 Compare May 15, 2026 04:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants