automation

You can schedule recurring tasks and periodic checks using cron-expression driven jobs that run in isolated, stateless chats for daily reports, timed reminders, or any scheduled prompt execution. Cron expressions define precise timing intervals for these automated actions.

A persistent heartbeat monitoring agent is a context-aware chat that follows a shared checklist to batch ambient monitoring like inbox scans, pending follow-ups, and health checks. You need one for routine maintenance tasks requiring continuous context across recurring intervals.

Yes, you can use both together: schedule a daily cron job for team summaries at specific times while simultaneously running a persistent heartbeat every 30 minutes to check for urgent messages and incomplete tasks, combining precise scheduling with ambient monitoring.

Manage cron jobs and heartbeat intervals through CLI controls, Settings UI, or REST API to configure timing, view status, and handle failures automatically. The CLI provides direct commands for interval configuration and status monitoring of scheduled automation tasks.

Automatic failure handling disables jobs after repeated failures to prevent cascading errors in scheduled agent prompts. Memory is kept disabled to avoid contamination, ensuring failed cron runs or heartbeat checks do not corrupt subsequent scheduled task execution.

No external dependencies are required to set up timed reminders and routine maintenance automation. The system provides built-in cron expression scheduling, persistent heartbeat context, configurable intervals, and CLI controls for managing periodic agent check-ins and scheduled actions independently.