We thought people would build their agents on our platform. It turned out they wanted to build them their own way and just hand us the running.

Reddit r/AI_Agents Products

Summary

公司宣布其 Agent 平台 2.0 大幅简化:砍掉 pods、workflow、memory bank 和自研 SDK,改为兼容 OpenAI Agents API,支持任意模型(Claude、Gemini、开源权重、OpenRouter 或用户自带 key),并聚焦于故障恢复、精确成本日志和严格按用户指定模型运行。

The first version of our platform asked people to move in. It had pods for teams of agents, workflows to chain them, a memory bank, and our own SDKs in three languages. The idea was that agents would be built inside our world. Then we watched what people actually ran. Most had a framework they already liked, or a loop they'd written themselves. Some were running agents as a pile of scripts and CLI processes, and hated it. Nobody wanted a nicer way to design an agent. They wanted someone else to keep it running. We'd built a whole kitchen, and people mostly wanted the oven. So 2.0 dropped pods, workflows, the memory bank and the SDKs. The platform now speaks the same API as OpenAI's Agents API. That's only the shape of the calls. The model behind them can be Claude, Gemini, an open-weight model, or anything on OpenRouter or on the user's own key. Anyone already on the openai package changes the base URL and nothing else (the line is in the comments, since posts with links get removed here). Everyone else has an OpenAI client in almost every language, far more than we could ever have maintained. Leaving means changing the URL back. What's left is what people kept asking about: what happens when an agent breaks, what it cost, and whether it ran the model they asked for. When it breaks. Turns fail. A provider has a bad minute, we restart a machine, the credit runs out. We made it so the turn fails and the session survives. Saying "continue" picks it up with its conversation and files intact, without rebuilding context or rerunning the last hour. What it cost. Every model call is logged with its cost, down to a millionth of a dollar, so "what did that run cost?" has an answer without an export. Which model ran. The model someone picks is the model that runs. If it's unavailable, the call fails with an error. Some gateways quietly fall back to a different model, and people find out when the outputs start looking off. We'd rather fail. Under every session is the same open-source harness from our post here a few weeks back, the one where 100 agents updated our docs (link in the comments). It was built to use as few tokens as possible, and that's still its main job. And since someone always asks: we make nothing on tokens. On our credit, people pay OpenRouter's price plus the fee OpenRouter charges for buying credit. On their own key, they pay their provider directly. We charge for plans and machine time. For anyone running agents in production: what did you end up building yourself that you wish you hadn't?
Original Article

Similar Articles

Introducing the Agents API

YouTube AI Channels

OpenAI launches the Agents API, providing a hosted agent runtime framework to help developers handle orchestration, session management, and context management, simplifying the production deployment of AI agents.

Build Hour: Agents SDK

YouTube AI Channels

OpenAI released a major update to the Agents SDK, introducing a Codex-style runtime framework, separation of sandbox and runtime, memory, skills, and other features. It also launched managed Shell tools, container endpoints, a skills API, and a TypeScript version, aiming to simplify building and deploying production-grade agents.

@rohanpaul_ai: Every agent vendor wants your team to standardise on its assistant. @agorcloud sits one layer up: it runs existing agen…

X AI KOLs Following

Agor Cloud 宣布推出 Open Beta 托管版本:一个位于多个 agent harness 之上的协作层,在共享空间看板上统一运行 Claude Code、Codex、Gemini 等现有智能体,支持按任务选择不同 agent/模型、共享知识与显式交接,并可将智能体打包为带调度的"AI 队友"接入 Slack、Discord、GitHub 等平台。

@ba_niu80557: https://x.com/ba_niu80557/status/2062103965517721821

X AI KOLs Timeline

This article breaks down six design paths for the 2026 Agent framework (LangGraph, OpenAI Agents SDK, CrewAI, Dify, vendor-native SDK, Pi) and provides selection recommendations based on dimensions such as state management, process complexity, human-machine interaction, and model flexibility. It is suitable for teams looking to choose an Agent framework in a production environment.

This article systematically reviews AI Agent architecture and engineering practices, covering control flow, context engineering, tool design, memory, multi-agent organization, evaluation, tracing, and security. It is based on the OpenClaw implementation and emphasizes the critical role of Harness (testing and validation infrastructure) for system stability.

X AI KOLs

This article systematically reviews AI Agent architecture and engineering practices, covering control flow, context engineering, tool design, memory, multi-agent organization, evaluation, tracing, and security. It is based on the OpenClaw implementation and emphasizes the critical role of Harness (testing and validation infrastructure) for system stability.