Tasks

Schedule prompts, reminders, watchers, and playbook runs

Tasks automate recurring work on a schedule or trigger cadence. They are best used for predictable operations, reminders, and monitoring loops.

Open Tasks from the sidebar to configure them.

Task types

  • Prompt
  • Reminder
  • Watcher
  • Scheduled Playbook runs

Pick the simplest type that matches the outcome.

Reminder modes

  • Plain: send reminder text directly
  • Source: pull context from a source before composing reminder
  • Agent: allow model/tool-assisted reminder generation

Guidance:

  • Start with Plain for predictable delivery
  • Move to Agent when synthesis or tool use is required

Scheduling triggers

  • Once
  • Cron

For production tasks, document schedule intent in the task description so operators understand why it exists.

Destinations

Task output can route to:

  • In-app destination
  • Desktop notification
  • Channel preset destination
  • MCP tool destination

Channel and MCP destinations are validated against current configuration.

Source-aware tasks

Watchers and source-based reminders can summarize updates and extract actionable changes. Keep criteria narrow so signal stays high.

Rollout guidance

  1. Validate in-app delivery first
  2. Move to channel/tool destinations after format is stable
  3. Manually run tasks after edits
  4. Keep one clear purpose per task

Operational tips

  • Prefer channel presets over one-off destination values
  • Keep cron schedules human-readable in descriptions
  • Archive/disable stale tasks instead of leaving unclear automations active