Schedules

Run recurring Vibe Lane tasks against one local project folder. Each schedule keeps the exact Vibe Lane version you approved, so later lane edits do not change unattended work without your confirmation.

Schedules is a tab in Automation. You can open Automation from the application side menu even when no VibeSpace is open.

Before you start

A schedule needs a local folder and a Vibe Lane. If you have not created a lane yet, see Vibe Lanes and Vibes and Skills.

Create a schedule

1. Open Automation from the application side menu.
2. Select the Schedules tab.
3. Click New Schedule.
4. Enter a name for the schedule.
5. Enter the task instruction that the lane should receive on every run.
6. Select a known project or choose any local folder.
7. Select a Vibe Lane.
8. Choose Interval, Daily, or Weekly.
9. Configure the cadence for the selected schedule type.
10. Open Advanced if you need to change the time zone.
11. Under Missed runs, choose what CrispyVibe should do when a run is missed.
12. Choose how to save the schedule.

After you enable the schedule, its next run appears on the Schedules dashboard.

🚨 Warning: Enabling a schedule requires Full Trust confirmation, including from the quick Enable control. Scheduled Vibe Lane checkpoints can edit files and run commands without asking first. Review the project folder, task instruction, and lane before confirming.

Create or edit lanes without losing your draft

From the schedule editor, click Manage Vibe Lanes to create or update a lane. Click Manage Vibes to manage the reusable Vibes used by lane steps.

When you return to Schedules, CrispyVibe restores your in-progress schedule draft. Editing a lane does not silently replace the version selected in the draft; select the updated lane version explicitly when you want to use it.

Pinned Vibe Lane versions

Saving a schedule pins a snapshot of its Vibe Lane. Future runs continue to use that snapshot even if you edit the source lane later.

When an update is available, open the schedule and click Update Vibe Lane. CrispyVibe shows the old version, new version, and updated stage route before you confirm. Tasks that already started keep their original lane version.

Manage scheduled work

The dashboard shows each schedule’s project, lane, cadence, next run, and current status. Use Filter to show All, Active, Attention, or Paused schedules. Open a schedule to review its configuration and run history.

Schedule state and task state are tracked separately. A paused schedule whose task is still running appears under both Active and Paused.

• Run Now starts an extra occurrence without moving the next scheduled time. It does not start if the schedule already has a queued, running, or waiting task.
• Pause prevents future occurrences but does not stop work that already started.
• Open task opens the linked Vibe Lane task and its checkpoint progress.

When you stop a schedule’s active task, CrispyVibe asks Stop this run?:

• Stop Current Run stops the active task but leaves the schedule enabled. Another run can start at the next scheduled time.
• Stop and Pause Schedule stops the active task and prevents the next occurrence.

Stopping the same task from the Vibe Lanes task surface stops only that run; it does not change the schedule.

A schedule does not start overlapping work. If its previous task is queued, running, or waiting for your input, another occurrence is skipped.

Delete a schedule

Deleting a schedule removes it and its run history. Completed tasks remain available in Vibe Lanes.

If the schedule has an active run, CrispyVibe asks you to choose:

• Stop Run and Delete stops the current task and deletes the schedule.
• Keep Run and Delete Schedule lets the current task finish and removes only future scheduling.

When your Mac is asleep or CrispyVibe is closed

Schedules run while CrispyVibe is open. CrispyVibe checks for missed work when it launches, wakes, becomes active, or detects a clock or time-zone change.

Choose the missed-run behavior under Missed runs in Advanced:

CrispyVibe never replays every missed interval. Exact-time execution is not available while CrispyVibe is closed.

Troubleshooting

A schedule is blocked

Open the schedule and confirm that its local project folder still exists. Edit the schedule to select an available folder or valid Vibe Lane, then save it again.

A scheduled run did not start

Check whether the schedule is paused, the project folder is unavailable, or its previous task is still queued, running, or waiting for input. Also check the missed-run setting if your Mac was asleep or CrispyVibe was closed at the scheduled time.

Open the schedule’s run history to see whether the occurrence was skipped or blocked. If the linked task needs input, open it to respond, steer, approve, or stop the work.

A lane edit is not being used

Schedules pin their lane versions, so lane edits do not apply automatically. Open the schedule and click Update Vibe Lane to review and adopt the newer version for future runs.

Changes could not be saved

Check available disk space and confirm that CrispyVibe can write to its application-support folder, then retry. A failed save does not replace the last saved schedule or start a task.

Manage schedules from the CLI

Agents and scripts can create, preview, enable, run, and delete schedules with crispy schedule. The CLI follows the same rules as the app: saving freezes the lane version, adopt-lane corresponds to Update Vibe Lane, and any change that leaves a schedule enabled requires --confirm-full-trust. See Author Automation from the CLI for the full Skill → Vibe → Vibe Lane → Schedule workflow.

Known limitations

• CrispyVibe must be running for exact-time execution. Occurrences missed while CrispyVibe is closed are handled by the missed-run setting when it next launches.
• Schedules target local folders only, not SSH or remote projects.
• Cron expressions, webhooks, file-change triggers, and calendar integration are not supported.
• A schedule skips an overlapping occurrence rather than queueing another task.

Related docs

• Vibe Lanes
• Vibes and Skills
• Agent CLI