Persistent agent infra: Codex Hooks and Loopndroll
Codex added 'Hooks' that teams are using to build persistent agents — exemplified by Loopndroll, a macOS toolbar that keeps agents running across updates — highlighting patterns for reliable, always‑on agent processes without downtime. This points to managed infra patterns for DevX and persistent orchestration. (x.com)
Codex’s Hooks feature is an extensibility framework that lets teams inject user-defined handlers at lifecycle events such as SessionStart and Stop, and it lists example uses including custom logging, prompt scanning, summarization for persistent memory, and validators; the feature is exposed behind a config flag (features.codex_hooks = true). (developers.openai.com(developers.openai.com)) OpenAI delivered the experimental hooks engine in the rust-v0.114.0 Codex release that was published March 11, 2026, which also added GET /readyz and GET /healthz endpoints for WebSocket app-server deployments. (sourceforge.net(sourceforge.net)) (newreleases.io(newreleases.io)) Loopndroll is a community macOS menu‑bar app that explicitly uses Codex Hooks to “keep Codex running forever” by installing a global Stop hook at ~/.codex and offering either indefinite sessions or per‑thread turn budgets; the project repo shows 44 stars and active commits within the past day. ) A separate open-source utility, codex-hooks by hatayama, replays a compatible subset of Claude‑style command hooks by watching Codex session JSONL files, deliberateing toward a macOS‑focused Python runner that decides when hooks should fire and which commands to run. ) The pairing of Hooks plus health endpoints formalizes a managed‑infra pattern: lifecycle hooks let teams centralize policy and telemetry at deterministic agent boundaries while GET /readyz and /healthz enable platform-level liveness/readiness checks for orchestration and autoscaling. (developers.openai.com(developers.openai.com)) (newreleases.io(newreleases.io)) Community projects demonstrate two concrete reliability patterns for always‑on agents: persistency at the OS level (menu‑bar app + ~/.codex hook used by Loopndroll) and replay/watch‑based orchestration (session JSONL watchers used by codex-hooks), both of which surface clear integration points for observability (logs, validators, summaries) at the hook boundary. ) )
