Automations from one sentence

The idea

A message with timing words becomes a card (what, when, next three runs, who, credits); Start creates a schedule or event trigger whose runs report back to the asker.

The problem
Recurring work needed a scheduler UI.
Why it matters
Recurring work is set up from chat and starts only after explicit confirmation.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

Where it lives in the product

  • Completion reports, digest and alert fallback

    Completion reports follow a per-conversation level, a daily digest batches status, quiet hours hold non-urgent messages, and a critical alert open 15 minutes also goes by SMS or email.

  • Command Center and drill-down

    A live console shows totals, a runtime map, a control desk and telemetry from stored records, and every page opens a stacked drill-down down to the step, with a why-trace and question threads.

  • Intake from webhooks, polls, mentions and schedules

    Work arrives from tracker webhooks (signed and deduplicated) or polls, and from @mentions of a worker. Cron schedules also open work, and a schedule can fire only when a watched event happened.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.