Skip to content
Tanzanite Docs

Schedules & Triggers

Beyond one-off chats and plans, Tanzanite can start work for you on its own — on a clock, or when your project’s code changes.

Schedules

Section titled “Schedules”

A schedule runs on a recurring cadence — for example, a morning briefing or a nightly check. Each time it fires it can run a script from your project, start an agent with a prompt, or both. Set the cadence (a cron expression, in your time zone) and Tanzanite handles the rest; every fire is recorded in the schedule’s run history.

Manage schedules under Schedules in the sidebar. Cloud and Device projects can be scheduled; a Device project’s runs need its desktop to be connected. Local projects run on your machine, so they cannot be scheduled.

Triggers

Section titled “Triggers”

A trigger is a schedule whose clock is a commit: when a commit lands on a branch you choose (optionally only when certain paths change), it starts the same kind of run. Triggers live on the Triggers tab of the Schedules screen, each with a daily fire cap so a busy branch cannot run away.

Next steps

Section titled “Next steps”