agent-self-scheduling

Wrap a one-shot invocation like claude -p or codex exec in cron for intervals of one minute or more, or use a while-sleep loop for sub-minute timing. Alternatively, Hermes provides a built-in scheduler daemon that runs recurring jobs in isolated sessions.

Cron handles intervals of one minute or more with five-field expressions. Systemd timers survive reboots with better logging on Linux. While-sleep loops are required for sub-minute intervals since cron cannot go below one minute.

No, cron has a one-minute floor with five-field expressions and no seconds field. For sub-minute or sub-second intervals, use a while true sleep loop, a TypeScript extension, or an event-driven webhook instead of a timer.

Unattended runs hang on permission prompts when tool allowlists are missing. Pass --allowedTools for Claude Code or a sandbox auto-approve flag for Codex, and use structured JSON output so the wrapper can parse results deterministically.

No, each scheduled run starts as a fresh amnesiac session with no chat history. Persist state to a file the next run reads, resume explicitly with codex exec resume --last, or pass all needed context in the prompt.

No, Hermes enforces loop safety so cron-run sessions cannot create additional cron jobs, preventing runaway recursion. Schedule new jobs from an interactive session instead of from inside a scheduled job.