Responses API
responses-api-84c7d255·4 events·first seen 28d agoAliases: Responses API
Co-occurring entities
More like this (12)
Recent events (4)
From model to agent: Equipping the Responses API with a computer environment
OpenAI describes how it built an agent runtime by combining the Responses API with a shell tool and hosted containers, enabling agents to operate with persistent files, tools, and state. The architecture supports secure, scalable execution of agentic workflows. This represents a concrete infrastructure layer for deploying agents in production environments.
New Tools and Features in the Responses API
OpenAI announced new tools and features for its Responses API, expanding the capabilities available to developers building on the platform. The update likely includes additional built-in tools, improved function calling, or new modalities accessible through the API. As a Tier 1 source announcement, this represents a meaningful expansion of OpenAI's developer-facing infrastructure. Specific details were not available in the body text provided.
Speeding up agentic workflows with WebSockets in the Responses API
OpenAI published a technical deep dive into the Codex agent loop, detailing how WebSockets and connection-scoped caching were used to reduce API overhead and improve model latency. The post focuses on infrastructure optimizations within the Responses API for agentic workflows. These changes are relevant to developers building multi-step agent pipelines that rely on repeated API calls.
Unrolling the Codex Agent Loop
OpenAI published a technical deep dive into the Codex CLI agent loop, detailing how it orchestrates models, tools, and prompts via the Responses API. The post explains the internal architecture of the agentic coding system, including how the loop manages state, tool calls, and performance. This provides concrete implementation detail on how OpenAI structures production agent workflows on top of its API primitives.