正在加载视频...
视频加载失败
OpenAI's new Agents API is a hosted Codex runtime that can connect to sandboxes like E2B. OpenAI manages the model, harness, and agent sessions, while code executes on an isolated E2B machine with its own filesystem and preinstalled tools. We built an agent workbench where each chat runs on... show more
21,634 次观看 • 2 天前 •via X (Twitter)
10 条评论

@OpenAI @e2b LETS GO! Big Day for all the devs out there

@OpenAI @e2b 这组合起来终于像能干活的 agent 了

@OpenAI @e2b auto-pause + fork is the important part. the durable primitive isn't a long-running machine. it's replayable task state that can hydrate into a clean machine, branch, and resume.

@OpenAI @e2b hosted harness, isolated execution — the right split

@OpenAI @e2b The way it handles orchestration and long-running sessions is actually quite impressive.

@OpenAI @e2b auto-pausing each sandbox between turns could make long agent sessions much cheaper; how quickly does a resumed machine come back?

@OpenAI @e2b The isolated filesystem plus preinstalled tools is the part that matters most in practice. Most of my agent failures used to come from environment drift, not the model. Good to see that getting solved at the infra layer instead of every project rebuilding it.

@OpenAI @e2b Auto-pause between turns is the product, not a missing automation. A hosted harness that keeps going with no human gate is just a runaway script with better branding. Forks only help if the failed branch can’t write back by default.

@OpenAI @e2b The fork is the part I'd like to see explored more. A side-by-side view of what each attempt changed would make "try another approach" much easier to judge than scrolling two chat histories.

@OpenAI @e2b how's your cold start time on spinning up a fresh e2b sandbox per session?

