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.
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.
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.
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
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
- Start in an isolated project with read-only tools and synthetic data, using one repeatable end-to-end task.
- For every MCP, function, and web tool, document allowed actions, data scope, call records, and stop conditions.
- Compare hosted, self-managed, and partner sandboxes against network, file, secret, region, and logging requirements.
- 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
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 and Palantir turn supply-chain allocation expertise into a governed Nemotron training loop
NVIDIA published a supply-chain case study with Palantir Foundry on September 10. The workflow combines a governed Ontology, cuOpt optimization, planner decisions and rationales, point-in-time backtesting, and post-training of Nemotron 3.5 Lightning for material allocation recommendations. NVIDIA reports that its post-trained 30B model reached 86.7% allocation-decision accuracy on the development benchmark, compared with 55.5% for Nemotron 3 Ultra and 17.5% for the base Lightning model. The company also says a human planner reviews recommendations and makes the final call, while accepted, edited, and overridden outcomes feed future governed retraining. This is an official case study and development benchmark for a bounded allocation task. It does not establish broader general intelligence or general superiority for the 30B model beyond the specialized data, task, and evaluation design.
OpenAI introduces the Data agent for governed analysis and dashboards in ChatGPT Work
OpenAI introduced the Data agent for ChatGPT Work on September 10. The plugin connects approved company data sources, files, and business context so users can investigate changes in natural language, inspect evidence, and create interactive dashboards that teams can edit, share, and refresh. It can also share findings through connected Slack or email tools and carry out actions that users approve. Administrators control which connections and roles are available, while queries enforce the connected account's existing table, row, and column permissions. Data is listed in the ChatGPT Work Plugins directory; teams install it, complete required account connections, and start with @Data. Before operational use, teams should verify metric definitions, evidence, data scope, and each downstream action.
Salesforce unifies enterprise AI context, action, governance, security, and models in a new Harness
Salesforce introduced its Trusted Enterprise AI Harness on September 10, combining six capabilities for context, agency, action, governance, security, and model choice with an AI Control Plane for managing agents and AI across an enterprise. The company says customers can use the architecture with Salesforce technology, existing technology, or third-party models and systems, and describes headless access through MCP, APIs, Skills, and Plug-ins. Many technologies forming the foundation are available today. However, Salesforce explicitly says new capabilities and the unified experience are planned to begin rolling out in early fiscal FY28; pricing, packaging, regional availability, and upgrade paths will follow closer to general availability. Teams should treat this as an integration direction and validate current product availability before making architecture or purchasing commitments.


