Experimenting with Codex deciding its own next steps

Thanks! I’ve also been looking into /goal and related long-running objective workflows. There is definitely some overlap.

The angle I’m exploring with CodexLoop is automatic expansion + usability for longer runs. When Codex works on a broad goal, it often discovers follow-up work: bugs, missing tests, docs gaps, polish, product ideas, etc. I want the loop to capture those discoveries, organize what is active vs deferred, and still know when to converge.

So CodexLoop keeps external state like checklist, deferred ideas, review history, audit logs, and restart/continue behavior. The goal is to make longer Codex runs easier to inspect, resume, and control.