Skip to main content
AI NewsAI AgentsOpenAI Agents APICodex harness托管沙箱

OpenAI launches the Agents API public beta with the Codex harness and hosted sandboxes

Developers configure the task, model, tools, and environment in an API call while OpenAI operates the harness; the product remains in public beta.

ENHE AI5 min7 views
OpenAI launches the Agents API public beta with the Codex harness and hosted sandboxes

Key takeaways

OpenAI introduced the Agents API in public beta on September 10, exposing the harness and infrastructure behind Codex to developers. A single API call can define an agent task, model, tools, and environment. Teams may run it in an OpenAI-hosted sandbox, on their own infrastructure, or with listed ecosystem-provider integrations. OpenAI says the API supports MCP, custom functions, built-in tools such as web search, automatic context compaction for long sessions, and optional parallel subagents. The hosted sandbox can be configured with files, packages, skills, and plugins. The API is available to all developers in public beta with no separate API fee beyond token and tool charges. Teams should validate permissions, tool behavior, observability, and recovery paths before treating beta workflows as production-ready.

OpenAI describes the Agents API as a public beta available to all developers, with no additional API fee beyond token and tool usage.
One call can configure a task, model, tools, and environment, using an OpenAI-hosted sandbox, a team's own infrastructure, or listed ecosystem-provider integrations.
OpenAI says the API supports MCP, custom functions, web search, automatic context compaction for long sessions, and optional parallel subagents.

Direct answer

OpenAI introduced the Agents API in public beta on September 10, exposing the harness and infrastructure behind Codex to developers. A single API call can define an agent task, model, tools, and environment. Teams may run it in an OpenAI-hosted sandbox, on their own infrastructure, or with listed ecosystem-provider integrations. OpenAI says the API supports MCP, custom functions, built-in tools such as web search, automatic context compaction for long sessions, and optional parallel subagents. The hosted sandbox can be configured with files, packages, skills, and plugins. The API is available to all developers in public beta with no separate API fee beyond token and tool charges. Teams should validate permissions, tool behavior, observability, and recovery paths before treating beta workflows as production-ready.

Verified facts

OpenAI describes the Agents API as a public beta available to all developers, with no additional API fee beyond token and tool usage.

One call can configure a task, model, tools, and environment, using an OpenAI-hosted sandbox, a team's own infrastructure, or listed ecosystem-provider integrations.

OpenAI says the API supports MCP, custom functions, web search, automatic context compaction for long sessions, and optional parallel subagents.

OpenAI launches the Agents API public beta with the Codex harness and hosted sandboxes cover infographic
ENHE AI original composite: a topic-specific real-work scene with fact-checked editorial copy.

What changed

  • The Codex harness becomes available as a managed API
  • Agent environments can use hosted, self-managed, or ecosystem-provider integrations
  • Long sessions can use OpenAI-provided context compaction
  • Complex work can optionally use parallel subagents
OpenAI launches the Agents API public beta with the Codex harness and hosted sandboxes team operating flow
A four-step path from announcement to testable, reversible, auditable operations.

Impact for AI users

The release moves part of agent orchestration, context handling, and managed execution infrastructure to the platform, letting teams focus on business tools, knowledge, and workflows. Beta availability does not establish a production control plane: implementers still need to define and test external-system permissions, tool side effects, spending limits, audit logs, failure recovery, and human approvals.

Operating checklist

  1. Start in an isolated project with read-only tools and synthetic data, using one repeatable end-to-end task.
  2. For every MCP, function, and web tool, document allowed actions, data scope, call records, and stop conditions.
  3. Compare hosted, self-managed, and partner sandboxes against network, file, secret, region, and logging requirements.
  4. Set token, tool, and concurrency limits, then prepare human takeover for timeouts, errors, and subagent failures.

AI frontier news and analysis, AI software and model tools, AI skill tutorials and validation methods, and AI account and permission guidance

FAQ

Is the Agents API generally available?

No. OpenAI labels it public beta and says it will iterate quickly from feedback while working toward general availability.

Must an agent use an OpenAI-hosted sandbox?

No. OpenAI says teams can choose its hosted sandbox, their own infrastructure, or listed ecosystem-provider integrations.

Is there a separate Agents API platform fee?

OpenAI says there is no additional API fee; teams still pay for the tokens and tools their agents use.

Summary

The Agents API is a reusable starting point for agent infrastructure, not automatic production governance. Establish a minimal loop with constrained tools, explicit permissions, and replayable verification before expanding scope.

This AI-assisted article is checked by ENHE AI automation for official sources, bilingual fields, media rights, page safety, and historical duplication before publication.

What this means for everyday users

The release moves part of agent orchestration, context handling, and managed execution infrastructure to the platform, letting teams focus on business tools, knowledge, and workflows. Beta availability does not establish a production control plane: implementers still need to define and test external-system permissions, tool side effects, spending limits, audit logs, failure recovery, and human approvals.

Tools you may use

Related tutorials

Related Tools And Tutorials

Use the following ENHE AI sections to continue from the news signal into tool selection, account-service guidance, or practical learning.

Related reading

AWS benchmarks OpenAI models by cost per correct outcome instead of token price alone

AWS published an open-source benchmarking approach on September 11 for comparing GPT-5.6 Luna, Terra, and Sol on Amazon Bedrock with GPT-5.4 mini and nano on the OpenAI API. Instead of ranking models by dollars per million tokens, the harness measures cost per correct answer, cost per passing multi-turn research result, and cost per rubric-accepted professional deliverable. It uses one Responses API client and records timestamped result files, frozen grading prompts, and chart inputs. The post also documents important limits: sample sizes range from 48 to 198 items, Bedrock models ran with reasoning disabled, and API baselines used their defaults. AWS describes this as a practical configuration comparison rather than an estimate of intrinsic capability. Teams should rerun the method on 50 to 100 of their own tasks and include failures, retries, turns, latency, review, and rework in the decision.

A voice-agent release checklist for VAD, noise, interruptions, transcription, tools, and failure handoffs

A voice-agent release should not be accepted after one successful conversation in a quiet room. Test cases need to cover speech-activity detection start and stop behavior, silence and background noise, user interruption, transcription evidence and correction, spoken status around tool calls, and state recovery after timeouts or failures. The OpenAI Realtime API reference documents capabilities for real-time sessions, audio input and output, transcription, and server-side voice activity detection. This article turns those capabilities into a general acceptance checklist. It is not a release announcement, a claim about a particular product version, or a performance guarantee. Teams should define their own language, device, privacy, latency, escalation, and human-review criteria before deployment.

GitHub Copilot Usage Metrics Adds Agent-App Activity

GitHub announced on August 7, 2026 that the Copilot Usage Metrics API now reports activity from third-party agent apps. Enterprise, organization, enterprise-user, and organization-user reports can expose the activity in one-day and 28-day windows. The new totals_by_3rd_party_agent data includes a stable agent_id and a display name that may change; the identifier should be the join key. This gives administrators a finer view of cost, permissions, and workflow adoption, but it does not automatically explain business value. Start with a read-only sample, reconcile time zones, pagination, and overlapping windows, then associate agent activity with AI credits, members, repositories, and permission changes before changing budgets or access.

AWS Shows AgentCore Policy Workflows with Tenant Isolation and Versioned Skills

AWS’s August 7, 2026 machine-learning case study describes how Cohere Health uses Amazon Bedrock AgentCore to turn clinical prior-authorization policies into structured data. The architecture combines Runtime microVM isolation, Gateway for unified tool access, Memory for session history, and the Agent Skills open standard for versioned domain capabilities. Skills are evaluated with reference data and expert review before release. The reusable lesson is not to automate medical judgment with one prompt. It is to separate tenants, tools, data sources, versions, feedback, and approval, then begin with public or de-identified documents before connecting sensitive business data. Keep the same evidence trail when the workflow changes.

NVIDIA Expands DGX Spark With 64GB: Evaluate a Local AI Workstation

On October 2, NVIDIA announced a 64GB unified-memory DGX Spark configuration and said partner availability would begin October 23 at a starting price of $4,999. NVIDIA says one unit can run models up to 100 billion parameters and that two systems can pool 128GB; it reports up to 1.7x performance in its own Qwen 3.8 27B test. Availability is forward-looking, and performance figures are vendor results. Model choice, quantization, context length, and concurrency change outcomes. This article offers a practical evaluation checklist for teams comparing local inference with cloud services. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.

Microsoft’s 2026 Defense Report: AI Is Changing the Pace of Cybersecurity

In its October 1 commentary on the 2026 Microsoft Digital Defense Report, Microsoft says threat actors are using AI in parts of existing workflows, including reconnaissance and social engineering. The post does not claim that attacks have become fully autonomous; it highlights changes in speed and scale. Identity controls, least privilege, data protection, monitoring, testing, and secure development remain central. This article separates Microsoft’s observations from independent conclusions and turns the post into a practical checklist. Teams should compare the claims with their own telemetry and incident history before changing priorities. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.

Sources

Table of contents

Latest Insights