Automations

Automations let you run agent tasks on a schedule without any manual intervention. Set up a recurring check, a daily report, or a webhook-triggered workflow — and have the results delivered to Telegram, Discord, Slack, Lark, or your desktop.

Creating an Automation

1. Navigate to Automations in the sidebar (or type /automation)
2. Click + New Automation (or choose a template from the gallery)
3. Fill in the creation form:
   • Name — A short label for the automation (e.g., "Morning News Brief")
   • Description — Optional context about what it does
   • Prompt — The task you want the agent to perform each time it runs
4. Choose a trigger type (see below)
5. Configure agent settings and delivery options
6. Click Create

Trigger Types

Scheduled (Cron)

Run your automation at specific times — daily, weekly, or on a custom schedule.

Three scheduling modes are available:

The visual schedule builder lets you pick a frequency (hourly, daily, weekly, monthly) without writing cron syntax. It shows a preview of the next three run times so you can verify the schedule before saving.

Cron expression examples:

All cron times respect the timezone set in your system preferences.

Heartbeat

Run your automation at a fixed interval — for example, every 30 minutes. Heartbeats are ideal for continuous monitoring.

• Interval — How often to run (in minutes). Default: 30 minutes
• Active hours (optional) — Restrict execution to a time window, e.g., 09:00-17:00. Outside this window, the heartbeat sleeps
• Queue pickup mode — Instead of running a prompt, the heartbeat can pick up tasks from an agent profile's queue. Select a profile and choose between full context or minimal context mode

Heartbeats use a cost-efficient model (Haiku) by default for frequent checks under one hour, keeping costs low for routine monitoring.

Webhook

Run your automation when an external service sends an HTTP request.

When you create a webhook automation, the app generates:

• A unique URL (e.g., https://your-app/automation/webhook/abc123)
• A bearer token for authentication

Share these with the external service. The webhook accepts POST requests with a JSON body (up to 1 MB). The payload data is passed to the agent as context.

Payload templates let you extract specific fields from the incoming webhook body:

• {{payload.issue.title}} — Extract a nested JSON value
• {{headers.x-github-event}} — Capture a request header
• {{meta.timestamp}} — Insert the current timestamp

Manual

The automation only runs when you click Run Now — useful for tasks you want pre-configured but triggered on demand.

Agent Settings

Each automation has its own agent configuration:

Timeout options: 5 minutes, 10 minutes, 30 minutes, or 1 hour.

Delivery

Choose where automation results are sent after each run.

Platforms

Delivery Options

• Suppress empty results — If the agent finds nothing to report, skip the notification entirely. This prevents noise from heartbeats that check for changes but find none
• Only send on failure — Deliver notifications only when a run fails (available for legacy Slack/webhook modes)

Cost Controls

Automations can accumulate costs over time, especially with frequent schedules. Several safeguards are available:

When any limit is reached, you receive a notification and the automation is paused. You can adjust the limits and re-enable it at any time.

Condition Evaluation

For monitoring-style automations, you can add a condition — a natural-language description of when to notify you.

Example: An automation checks your CI/CD status every 2 hours. You set the condition to: "Notify me only if a build failure is detected." The agent evaluates whether the run result satisfies this condition. If nothing noteworthy is found, the delivery is skipped — saving you from unnecessary messages.

The evaluation uses a three-layer approach:

1. Hash check — If the result is identical to the last run, skip delivery
2. Keyword heuristics — Quick pattern matching for common signals
3. AI judge — A lightweight AI model evaluates the condition against the result

Monitoring Your Automations

Automation List

The main Automations page shows a card grid of all your automations. Each card displays:

• Name and description
• Trigger type and schedule
• Status (active or inactive)
• Run count and total cost
• Delivery platform

Filter tabs let you view All, Active, Scheduled (Cron), Webhook, or Heartbeat automations.

Run History

Click any automation to see its detail view with a full run history table:

• Status — Completed, Failed, Timed Out, Cancelled, or in-progress states
• Duration — How long each run took
• Cost — Per-run cost
• Result / Error — Click a row to expand and read the full output

Notifications

Real-time toast notifications appear in the bottom-right corner of the app when:

• A run completes or fails
• An automation is disabled (budget exhausted, max runs reached, or repeated failures)
• An automation expires

Click a notification to open the detail dialog with run history and quick actions (pause, resume, or delete).

Managing Automations

Advanced Settings

Overlap Policy

Controls what happens when an automation fires while a previous run is still executing:

Missed-Fire Policy

Controls what happens when the app was shut down during a scheduled run:

Templates

The template gallery provides pre-configured automations for common use cases:

Each template pre-fills the name, prompt, schedule, and suggested budget. Customize any field before creating.

Limits