Agent workflows got even faster. You can spin up containers for skills, shell and code interpreter about 10x faster. We added a container pool to the Responses API, so requests can reuse warm infrastructure instead of creating a full container creation each session. https://t.co/lmvwsaf5HN
OpenAI Responses API Gets Container Pool for 10x Faster Agent Workflows
OpenAI· Updated
OpenAI added a container pool to the Responses API, cutting container startup time by around 10x for skills, shell, and code interpreter. Requests now reuse warm infrastructure instead of creating a fresh container each session, reducing latency for agent workflows.
This matters for developers building multi-step agent workflows. Container startup overhead added latency at every step — shell commands, code interpreter sessions, and skill-based tasks all waited for fresh containers. Reusing warm containers keeps the agent loop tighter and more responsive.
Build agent workflows against the Responses API with shell, skills, or code interpreter — the container pool is live now, and requests reuse warm infrastructure by default.
Every HeadsUpAI update is written based on its original source and reviewed before it's published. Read our editorial standards →


