openai just quietly changed how long-running agents are supposed to work.
This is a vibe coding post classified by Jev as Agent infra & costs (a workflow), kept by the Vibe Coding Radar because it carries real work, not commentary.
openai just quietly changed how long-running agents are supposed to work. the new Agents SDK setup gives GPT-6 Astra an actual sandboxed workspace instead of forcing every task through one giant prompt. [this takes ~5 mins to understand… but the architecture is worth stealing] 1. give each agent its own isolated workspace 2. keep state + files between runs 3. gate tool access with permissions + guardrails 4. resume the same job after a crash instead of restarting it [the flow] → task enters the agent desk → Astra reasons + calls tools → sandbox keeps execution isolated → guardrails verify
Posted by Gipp 🦅 (10.7k followers) 9 days ago · 88 likes · 4.6k views · view the original post on X. Kept by the Vibe Coding Radar as Agent infra & costs.
More vibe coding work like this
- SpaceXAI is testing Remote Control in Grok Build. — @blankspeaker
- bonsai 2 27b just built this from one paragraph of prompt in one shot, all of it out of… — @sudoingX
- you can also use Jev to cut costs and token usage! — @tamarajtran
- Polsia now runs all company operations through a network of 9 agents, with a single… — @testingcatalog
- another terrible day for the “SaaS is dead” crowd — @tibo_maker
- Okay THIS is where agent infrastructure gets interesting. — @tonysimons_
- 3 settings inside my Hermes agent that turn it from "assistant" into "operator" 🚀🪽 — @BkashJosi
- 1 customer from $10k MRR 💸 — @tibo_maker
Every post is read and classified by Jev (TypeSafe): what it is, which market it belongs to, and whether the link is a real tool. 1.8k posts from 1.8k X accounts over the last 14 days, 141 tools, 12 markets. Collected every 5 minutes, fully re-ranked every hour — last update 2026-09-19 01:18 UTC. Full method.