Key findings
- Named teams are on record: Harvey evaluates its legal search agent on the SDK's traces, Lark's sandbox runtime and Coinbase's AgentKit ship on it, and Aurelio Labs left it for a framework of its own.
- The small set of primitives earns the most praise: 11 sources credit handoffs, tools, guardrails, and sessions, and 9 report agents built on the SDK.
- Runtime defects lead concerns at 14 sources, covering sessions, streaming, approvals, voice, shell output, and memory; most are closed GitHub issues.
- Latency is raised by 7 sources, the OpenAI-first design by 7, and hosting work by 5, including measured slowdowns and a 0% cache hit rate on nested agents.
- Tracing draws 4 concerns: traces missing from workers, batches dropped on rate limits, and an exporter that stays on beside custom processors.
- Of 5 sources that weigh running the SDK themselves against a hosted runtime, 3 keep it in their own service.
The public accounts behind the OpenAI Agents SDK's Signals explain what builders get from its small runtime and the work it leaves them. The English-language sources span March 2025 to October 2026, from Harvey's engineering team, Lark, Coinbase, Rowboat Labs and Octagon AI to solo developers, benchmark authors, and GitHub issue authors.
What builders keep it for
Builders name the size first. On Hacker News one commenter calls it simpler than Google's ADK, another names it a solid alternative to LangGraph, and a third advises starting minimal with it because most frameworks are overengineered. A developer who moved every older Completions and Responses API project to it finds handoffs and multi-agent orchestration intuitive.
Products run on it. Rowboat's agents runtime and copilot are Python apps on the SDK, Octagon AI open-sourced an MCP server of VC agents on it, and Lark's open-source sandbox runtime runs an SDK agent by default. Coinbase's AgentKit has shipped an SDK extension since March 2025, and a lead-generation builder on Reddit extracted 78 companies from one directory page.
Harvey shows what a company team does with the traces. Its engineers export them over OpenTelemetry to LangSmith and score hallucination, tool recall and retrieval recall offline, and that eval data lifted tool selection precision from near zero to 0.8 to 0.9 (Dec 10, 2025).
Where it breaks in production
Most specific complaints are GitHub issues. Builders report streamed runs that kept calling the model after the consumer stopped, a voice pipeline that waited 16.7 minutes, memory held across runs, and RedisSession failing on Redis Cluster. One measured all 6 tool calls started before a guardrail tripwire in 30 of 30 runs under the default setting.
The 0.22.x line and main drew their own reports: an approval resume on main after #4613 that left an orphaned tool output and killed the conversation, with 0.22.0 failing earlier in the same resume, failed Responses calls that dropped their token usage, and a shell tool that told the model a silent command printed "(no output)". Each issue is closed.
Latency reports span versions. A builder on GPT-4.1 saw one agent call rise from under 4 seconds to over 11 inside the Responses API, and a seven-agent orchestrator logged 90-second calls. A 300-turn run with a fake model spent about 1.2 of its 2.69 seconds re-fingerprinting earlier tool calls.
Tracing and other models
Tracing goes to OpenAI unless the exporter is replaced, and builders found the gaps the hard way. Traces went missing from Celery and FastAPI workers, the exporter dropped whole batches on HTTP 429, and duplicates appeared in LangSmith. A post on X warns that adding a processor leaves OpenAI's exporter on.
Other models work through adapters that OpenAI calls beta. Builders report LiteLLM crashing on Gemini 2.5 Pro, truncated responses returned as success, and the TypeScript AI SDK adapter breaking Gemini on parallel tool calls. Elshad Karimov's same-agent build cost US$0.08 a run on GPT-5 and found the SDK built around OpenAI.
Run it yourself or use a hosted runtime
OpenAI's hosted Agents API, in public beta since September 10, 2026, sharpens a choice builders were already weighing. Builders who host the SDK say a Python service is easy to run and keeps what reaches OpenAI under their control. Others found infrastructure and observability the bigger pain, one prefers Codex's app-server, and one expects teams to develop on the SDK and deploy through the API.
Agent Builder forces the question for some teams. OpenAI retires it on November 30, 2026 and recommends the SDK for workflows that continue as code.
- Will every agent run on OpenAI models for the next year?
- Can your team host the service, its session store, and its trace export?
- Must traces stay out of OpenAI's dashboard?
- Which tool calls must a guardrail or a person stop before they run?
Methodology
GILD synthesis of the 59 English-language public accounts in the OpenAI Agents SDK's Signals, read on October 28, 2026 and published between March 2025 and October 2026. They comprise 21 Hacker News posts and comments, 28 GitHub issues and 1 pull request, 3 Reddit posts read from the Arctic Shift archive because Reddit refused direct access, 2 posts on X, and 4 blog, engineering, and benchmark pages. Harvey's post and Coinbase's pull request state no stance and count toward no figure, and a latency issue whose author's ties to other vendors are unchecked counts toward none. GitHub issues are bug reports, which tilt the record toward problems. OpenAI's own blog and customer stories are left out. Counts describe the sources reviewed and say nothing about SDK users at large. Product behavior is checked against OpenAI's documentation on the same date.
Products in this piece
Sources
- Public source
- 33
- Official documentation
- 6
- Hacker News comment by Rowboat's co-founder on its agents runtime built on the SDK (Apr 22, 2025)
- Hacker News post by Octagon AI on its VC agents MCP server built on the SDK (Apr 26, 2025)
- Hacker News comment on an open-source deep research agent built on the SDK (Apr 2, 2025)
- Hacker News comment on moving every Completions and Responses API project to the SDK (May 29, 2026)
- Hacker News comment on hosting the SDK in a company's own Python service (Sep 11, 2026)
- Reddit r/AI_Agents: Why I combined fetching and extraction in one agent tool (Oct 6, 2026)
- Harvey blog: How agentic search unlocks legal research intelligence at Harvey (Dec 10, 2025)
- Show HN by Lark's builders: Runtime Use, whose default agent runs on the SDK (Mar 18, 2026)
- coinbase/agentkit pull request #550: OpenAI Agents SDK support in Python (Mar 11, 2025)
- Hacker News post on openai-agents-redis, written after SQLite sessions failed to scale (Jul 22, 2025)
- Agents SDK Python issue #5322: RedisSession fails on Redis Cluster (Oct 6, 2026)
- Agents SDK Python issue #5386: a streamed run keeps calling the model after its consumer stops (Oct 17, 2026)
- Agents SDK Python issue #4827: an approval resume on main after #4613 leaves an orphaned tool output (Sep 2, 2026)
- Agents SDK Python issue #5348: ShellTool reports "(no output)" as stdout (Oct 11, 2026)
- Agents SDK Python issue #2020: a 404 for a reasoning item after handoffs on GPT-5 (Oct 31, 2025)
- Agents SDK Python issue #5351: guardrail pattern verified on 0.23.1, with tool calls started before the tripwire (Oct 12, 2026)
- Agents SDK Python issue #1249: agent calls on GPT-4.1 slowed from under 4 to over 11 seconds (Jul 25, 2025)
- Agents SDK Python issue #421: 90-second calls in a seven-agent orchestrator (Apr 2, 2025)
- Agents SDK Python issue #5382: tool-calling runs get quadratically slower (Oct 16, 2026)
- Agents SDK Python issue #5085: nested Agent.as_tool runs never hit the prompt cache (Sep 18, 2026)
- Agents SDK Python issue #2135: traces silently dropped in long-running workers (Nov 29, 2025)
- Agents SDK Python issue #5023: the trace exporter drops a whole batch on HTTP 429 (Sep 14, 2026)
- LangSmith SDK issue #1619: duplicate traces through the OpenAI Agents SDK (Mar 31, 2025)
- Andrew (gocronk) on X: adding a trace processor does not turn off OpenAI's exporter (Oct 7, 2026)
- Agents SDK Python issue #758: LiteLLM with Gemini 2.5 Pro crashes on cached tokens (May 26, 2025)
- Agents SDK Python issue #4885: Any-LLM and LiteLLM return truncated responses as success (Sep 6, 2026)
- Agents SDK TypeScript issue #2048: the AI SDK adapter breaks Gemini on parallel tool calls (Oct 8, 2026)
- Elshad Karimov: Claude Agent SDK vs OpenAI Agents SDK, the same agent built in both (Jun 13, 2026)
- code-with-rashid: agentic-arena measured findings, framework prompt overhead against a hand-rolled loop (Sep 8, 2026)
- Pavitra Bhalla (Superserve): OpenAI Agents SDK Sandboxes, Which Provider Should You Actually Use? (May 19, 2026)
- Hacker News comment on replacing LangChain, LangGraph, and the Agents SDK with an in-house framework (Oct 8, 2025)
- Hacker News comment on infrastructure and observability as the bigger pain around the SDK (Apr 9, 2026)
- Hacker News comment comparing Codex's app-server with the Agents SDK (Sep 10, 2026)
- OpenAI: Introducing AgentKit, with the Jun 3, 2026 update retiring Agent Builder on Nov 30, 2026
- Agents SDK docs (Python): Overview (primitives and the Responses API default)
- Agents SDK docs (Python): Models (default model, OPENAI_DEFAULT_MODEL, LiteLLM and Any-LLM)
- Agents SDK docs (Python): Tracing (default exporter, processors, Zero Data Retention)
- Agents SDK docs (Python): Sessions
- OpenAI: Introducing the Agents API (Sep 10, 2026)