๐Ÿค–Stalecollected in 8h

Responses API Adds Agent Computer Environment

PostLinkedIn
๐Ÿค–Read original on OpenAI News

๐Ÿ’กBuild secure, scalable agents with OpenAI's new Responses API runtime

โšก 30-Second TL;DR

What Changed

Agent runtime built with Responses API, shell tool, hosted containers

Why It Matters

Empowers developers to deploy production-grade AI agents easily, accelerating agentic AI adoption in applications requiring persistent state and tools.

What To Do Next

Test the Responses API computer environment by building a simple file-handling agent.

Who should care:Developers & AI Engineers

๐Ÿง  Deep Insight

Web-grounded analysis with 6 cited sources.

๐Ÿ”‘ Enhanced Key Takeaways

  • โ€ขResponses API supports built-in tools including web search using the same engine as ChatGPT, file search, code interpreter, image generation, and remote MCP servers for external system connections[1][3][5].
  • โ€ขComputer use tool is powered by the Computer-Using Agent (CUA) model, achieving 38.1% on OSWorld, 58.1% on WebArena, and 87% on WebVoyager benchmarks, available as research preview for select developers[1].
  • โ€ขOpenAI introduced the open-source Agents SDK alongside Responses API for building multi-agent workflows with primitives like hosted tools, function tools, agents-as-tools, and MCP tools[3][4].
๐Ÿ“Š Competitor Analysisโ–ธ Show
FeatureOpenAI Responses APIAzure AI Foundry
Built-in ToolsWeb search, file search, computer use (CUA), code interpreter, image generationCUA, function calling, file search
IntegrationAgents SDK for multi-agent, stateful chainingAzure AI Agent Service with Semantic Kernel, AutoGen
PricingInput/output pricing for computer use, batch API available, improved caching (40-80%)Enterprise-grade, not specified
BenchmarksCUA: 38.1% OSWorld, 58.1% WebArena, 87% WebVoyagerNot specified [1][2][5]

๐Ÿ› ๏ธ Technical Deep Dive

  • โ€ขComputer use tool processes screenshots as input and outputs actions like click, scroll, or type to control computers or virtual machines[1][4].
  • โ€ขAPI endpoint is /v1/responses, supports text/image inputs, JSON outputs, tool definitions, and state storage with store: true for multi-turn conversations[3][5].
  • โ€ขImproved performance with reasoning models like GPT-5 shows 3% better on SWE-bench; agentic loop handles multiple tool calls in one request[5].

๐Ÿ”ฎ Future ImplicationsAI analysis grounded in cited sources

Assistants API will sunset by August 2026
OpenAI announced deprecation after achieving feature parity in Responses API, with sunset date August 26, 2026[3][4][5].
Responses API adoption will exceed hundreds of thousands of developers
Since March 2025 launch, it has been used at scale for agentic workloads and is recommended for all new projects over Chat Completions[3][5].

โณ Timeline

2025-03
OpenAI launches Responses API with initial tools including web search, file search, and computer use
2025-08
Deprecation of Assistants API begins, targeting full feature parity with Responses API
2026-03
Responses API adds agent computer environment using shell tool and hosted containers for secure agents
2026-08
Assistants API scheduled for sunset after Responses API achieves full parity
๐Ÿ“ฐ

Weekly AI Recap

Read this week's curated digest of top AI events โ†’

๐Ÿ‘‰Related Updates

AI-curated news aggregator. All content rights belong to original publishers.
Original source: OpenAI News โ†—