AIToday
Large Language ModelsOpenAI BlogPublished: Apr 23, 2026, 04:00 JST

OpenAI's WebSocket API mode speeds agents 40%

3 Key Points

  1. What happened

    OpenAI has launched WebSocket mode for its Responses API after a two-month sprint and alpha testing. Codex users running the latest models and developers like Vercel, Cline, and Cursor have reported latency improvements of up to 40%.

  2. Why it matters

    As model inference gets faster, the API overhead became a bottleneck. With the fast coding model GPT-5.3-Codex-Spark targeting over 1,000 tokens per second, traditional request handling made users wait on CPU servers. The new persistent connection caches state and processes only new input, making the API keep up with faster inference.

  3. What to watch

    The success hinges on developers adopting the new WebSocket mode without rewriting their integrations, which OpenAI has aimed for by keeping the familiar API shape. Watch whether the reported speed gains of up to 39-40% for partners like Cline and Vercel translate broadly across the developer community.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

OpenAI's performance sprint on the Responses API, starting around November 2025, initially cut time to first token by close to 45% through caching and fewer network hops. But that wasn't enough for the new GPT-5.3-Codex-Spark model, which targets over 1,000 tokens per second—an order of magnitude faster than prior flagship models like GPT-5. The deeper problem was structural: each request was treated independently, forcing repeated processing of the entire conversation history even when little had changed.

The solution meant ditching the pattern of many HTTP calls for a single persistent WebSocket connection. An internal prototype showed the potential, and after a two-month build, OpenAI launched a version that keeps the developer-friendly API shape with `response.create` and `previous_response_id`. The server caches prior state in memory, so only new input gets validated, classified for safety, and tokenized, avoiding redundant work across multi-turn agent rollouts.

The public launch has seen immediate adoption, with Codex moving most of its traffic to the new mode and achieving up to 4,000 TPS bursts in production. External partners like Vercel, Cline, and Cursor also report up to 40% latency improvements. The key question is whether broad adoption follows, since the benefit hinges on developers choosing to integrate WebSocket mode to see these gains.

FAQ
What exactly is WebSocket mode for the Responses API?
It's a new way to connect to OpenAI's API that keeps a persistent, in-memory cache of previous conversation state. Instead of rebuilding the full context for every request, follow-up calls only process new information, which cuts down overhead and makes agentic workflows faster.
How much faster are agentic workflows with this new mode?
Alpha users reported up to 40% improvements in their agentic workflows. Specific partners saw results like Vercel's latency decreasing by up to 40% and Cline's multi-file workflows becoming 39% faster.
Who benefits from this immediately?
Codex users running the latest models such as GPT-5.3-Codex and GPT-5.4 benefit from the speed up. It was also integrated into Vercel's AI SDK, and used by Cline and Cursor for their AI features.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAlaska Airlines restructures Amazon cargo deal but says Airbus freighter flights remain unprofitable