Michael Guo (@Michaelzsguo) “OpenAI 推出了能够让Agent长时间连续运行的 /goal。不少人已经成功实践。 Peter Stein” — TopicDigg

ran a codex session yesterday. closed the laptop at minute 57. came back 5.5 hours later. /goal had already resumed on its own. it injected its own developer message ("Continue working toward the active thread goal") and kept going. no re-prompt. no recovery steps. i opened the lid and it was four turns in. the full session: 6h 44min wall time, ~41 min actual model compute. 6.8M cumulative input tokens at 94% cache hit. final status TASK_COMPLETE. all four target end-to-end test scenarios passed. this is /goal in codex v0.128.0. it's the ralph loop, made first-class. native persistence, runtime continuation, tui controls. the goal survives sleeps, network drops, deliberate pauses. you don't have to be there. what surprised me: the prompt is the contract. mine was 600+ words. structured xml blocks, a reading list, working rules, anti-pattern fences, a done_when block. "/goal do thing" is not the interface. the prompt is. would love to hear what you think.