Rituals

A ritual (also called a schedule) is a scheduled, autonomous run of an agent: you provide a prompt and a timing configuration, and the agent executes that prompt on its own, on a cadence, with no chat interaction. Rituals handle repetitive work — morning summaries, periodic monitoring, weekly reports.

Creating a ritual

1. Open the agent’s editor.
2. Go to the Rituals section.
3. Select New ritual to open the configuration.
4. Provide a name (what the ritual is for), a prompt (the exact message the agent receives each run), and a schedule.
5. Save.

Rituals can be enabled, disabled, edited, or removed at any time.

Scheduling

The schedule accepts cron-style expressions, so you can express things like “every weekday at 9:00 AM,” “every hour,” or “first day of the month.” Set timing in your local timezone to avoid unexpected UTC offset surprises.

Schedule logs

Each run creates a log entry showing the timestamp, a status (Success or Failed), an output preview, the full transcript when expanded, and error details for failures. When a ritual fails, start with its most recent log entry.

Common use cases

• Daily email summaries organized by sender.
• Hourly service-status monitoring with notifications.
• Weekly CRM pipeline reports.
• Monthly file-cleanup operations.

Rituals and guardrails

Rituals run with full personality and guardrails — with one critical caveat: there’s no human in the chat to approve anything. Actions marked Needs approval are skipped during a ritual, with a note in the log. Mark anything a ritual must actually do as Allowed. See Personality & Guardrails.

In the enterprise

Team members can schedule their own rituals. Rituals that act on shared systems or take consequential actions are governed like any other automation — the same approved connectors and org-wide guardrails apply. See Governance & Approvals.

Before you rely on a ritual

Make sure the agent has the tools and connectors it needs, review its guardrail settings, and confirm a clean manual run before scheduling it.