OpenAI turned its coding agent into general-purpose infrastructure — what the new Agents API means for AI product builds

OpenAI launched its Agents API in public beta on 10 September 2026, exposing the session orchestration, context compaction and sandboxed execution it built for its Codex coding agent as general-purpose infrastructure any developer can build on, billed through normal model and tool usage rather than a separate fee.

On 10 September 2026, OpenAI put its Codex agent harness behind a public API. The Agents API hands developers the same machinery OpenAI built to run its own coding agent — durable sessions that continue across turns, automatic context compaction for long-running work, coordination across subagents, support for MCP and custom tools, and execution inside an OpenAI-hosted sandbox or a developer’s own compute environment. There’s no separate charge for the API itself; usage is billed through whichever underlying models and tools a session calls. OpenAI also shipped GPT-Live-1 to general availability the same week, adding full-duplex voice conversation that can run alongside a backend agent handling reasoning and tools.

Why this is bigger than a coding-tools story

The interesting part isn’t that OpenAI improved its coding agent — it’s that the hard infrastructure problems behind any AI agent (keeping a session alive over hours or days, compacting context so it doesn’t blow the window, running tools safely in a sandbox, coordinating several subagents on one task) are now something a team can call an API for, rather than something they have to build themselves. That’s the same trajectory cloud computing took: undifferentiated heavy lifting turns into a managed service, and the competitive question shifts from “can you build the plumbing” to “what does your agent actually do, and how well is it scoped to the problem.”

So what

If you’re a founder or product lead weighing whether to commission an AI agent product — not a chatbot bolted onto a website, but something that does multi-step work on a user’s behalf — this lowers the cost and risk of the infrastructure layer, but it raises the bar on everything else: the scoping, the guardrails, and the judgement about what the agent should and shouldn’t be trusted to do unsupervised. That’s the part that still needs a team who’s built agentic products before, not just a team that knows the API exists. Get in touch through our contact page if you’re scoping something in this space and want a straight read on what’s realistic.

← All research

More research.

GitHub Copilot SDK is becoming the Microsoft Copilot SDK: what builders of AI products should know

On 28 October 2026 GitHub said its Copilot SDK is being renamed Microsoft Copilot SDK, the programmable layer for the shared Microsoft and GitHub agent harness. No immediate action is needed.

Read ›

GitHub Agent Merge: Copilot now watches your pull requests and fixes what blocks the merge

On 28 October 2026 GitHub added Agent Merge to pull requests: a 'Watch and fix' option where Copilot repairs failing Actions workflows and merge conflicts in the cloud, optionally with auto-merge.

Read ›

Claude Code 2.1.314 adds a setting that blocks AI file writes outside the project folder

Claude Code 2.1.314 (30 October 2026) adds permissions.blockWritesOutsideWorkingDirectories, so Claude's file-editing tools refuse any path outside the project in every permission mode.

Read ›

GitHub Enterprise now includes Copilot: seats are bundled, AI usage moves to your budget

From 28 October 2026 account-team customers can get Copilot included with every GitHub Enterprise licence, with AI usage metered against an enterprise budget from the first request. Standalone Copilot is $10 per user per month.

Read ›

GitHub Copilot Fusion goes GA: one pick, many models, and a 30% launch discount

On 28 October 2026 GitHub made Copilot Fusion generally available: instead of choosing a model, developers pick an effort level and Copilot routes each task across models. Paid plans get 30% off model costs for a limited time.

Read ›

GitHub Agentic Workflows is generally available: automations written in plain Markdown

On 28 October 2026 GitHub made Agentic Workflows generally available: AI agents that triage issues, analyse CI failures and update docs, defined in Markdown and run inside GitHub Actions with read-only defaults.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work