Automation

Automation

OpenPhoenix supports foreground turns and durable operational work without moving policy into individual channels.

Scheduled jobs

jobs arrays entries use cron expressions and can run a model prompt or a shell script. A job can select a model, perform a precheck, require an expected marker, limit whether it may act, and deliver to chat IDs or a webhook. [job_defaults] supplies shared delivery and action settings. Validate schedules with phoenix jobs.

Heartbeat and dreaming

Heartbeat runs a configured check-in prompt on a fixed cadence. Its default is observe-only, which denies tools that write, execute, send, or drive the browser. Dreaming is an optional idle reflection journal. Both remain disabled until configured.

Background work

The task registry tracks process identity, status, bounded result tails, cancellation, reaping, and retention. Use phoenix tasks or /tasks. Boards hold task cards with status and priority. Commitments track time-bound follow-ups.

Hooks

Lifecycle hooks can subscribe to turn, tool, command, and error events. Hook commands are validated, receive bounded JSON payloads, and run with timeouts. List and test them with phoenix hooks.

See Configuration, Chat-Commands, and Security.