Scheduled tasks let VibeSpace kick off tasks automatically on a plan: a morning summary every day, a dependency scan every Monday, a data script at a specific time — each trigger creates a task and starts a run.
Rule types
| Type | Setting | Example |
|---|---|---|
| Once | a specific time | run a data-migration dry run tonight at 22:00 |
| Daily | a minute of the day | summarize yesterday's build logs at 09:00 every day |
| Weekly | weekday + minute | check dependency updates Mondays at 10:30 |
Creating a scheduled task
- Open the Schedules navigation;
- Click new, then fill in a name and the goal prompt (same style as New Task);
- Choose the rule type and time;
- Choose the backend (API model or CLI) and related options;
- Save, then toggle it on.
Each trigger creates an independent task and run, identical to a manual one — approvals, timeline, ChangeSet, and recovery all apply.
Run records
The Schedules page keeps a run record list: when each trigger fired and how it ended, so you can confirm tasks ran as expected.
Important boundaries
- Triggers only while the app runs: VibeSpace is a local app; the scheduler lives with it. Closing the app pauses schedules, and missed triggers are not replayed;
- Fixed Request-approval mode: scheduled runs always use the Request approval permission mode, so nothing risky executes unattended (low-risk read-only operations are unaffected);
- CLI backend limit: CLI backends don't provide the
schedule_createhost tool, so the agent can't create schedules itself — you can always create them in the UI.
Tip: for automation that must complete unattended, keep the app running (pair with "minimize to tray" and "launch at login" in Settings) and make the workspace and prompt precise.