Scheduled Task Runs

Scheduled tasks are normal tasks with a configured run time and optional recurrence. They are managed from the Schedule page and preserve the task's prompt, model, agent, attachments, project context, and execution boundaries.

Use schedules for work that should happen later or repeatedly without requiring a person to remember to start it.

What Users See

UI Concept	Meaning
Schedule page	Calendar/list surface for one-time and recurring work.
Scheduled category	Tasks can be moved into scheduled work when timing is configured.
Run at	The first or next intended run time.
Next run	The exact computed upcoming execution time shown on schedule cards and task details.
Enabled state	Keeps the schedule record while allowing future runs to pause.
Auto-merge	Lets an eligible repository-backed scheduled task merge to its target branch after completion when enabled in the schedule/task setup.
System schedules	Visible maintenance tasks such as memory consolidation and skill library upkeep.

Supported Recurrence

From a task's Details panel, open Schedule and configure timing in the schedule editor. You can also schedule a new task before sending its first message. Choose a future start time; changes unrelated to timing preserve the existing next run.

OpenVibely supports one-time, second-based, minute-based, hourly, daily, weekly, and monthly schedules. Daily, weekly, and monthly scheduling preserve local time-of-day across daylight-saving transitions by computing through local time.

Choice	Meaning
One-time	Run the task once in the future, then stop.
Seconds/minutes/hours	Repeat at a sub-daily interval.
Daily/weekly/monthly	Repeat on calendar-aware cadence while preserving intended local time.
Disable	Keep the schedule but stop future dispatch.
Delete	Remove the schedule.

Open a schedule card's action menu to pause or resume it, run it immediately, edit its timing, or delete the schedule. Run Now is off-cadence: it queues work without replacing the stored next-run time. Recurring schedules continue advancing to their next occurrence while an earlier run is active.

Manage A Batch

On the Schedule page, Command-click on macOS or Ctrl-click on other systems to select several schedules. Drag one selected card to move the full selection by the same offset while preserving each schedule's relative run time. Disabled schedules can be moved without being enabled.

Skipping Runs And Project Pauses

Select calendar dates or hour ranges and choose Skip to exclude occurrences without deleting their schedules. Use Unskip to restore excluded ranges. Selections can span dates, and partially skipped runs remain identified in the calendar.

Page actions can pause or resume scheduled dispatch for the current project. This does not cancel work already running. Individual schedules retain their own enabled state. The schedule editor provides a shared date/time picker for choosing future runs.

Dispatch Boundary

When a schedule reaches its next run time, the scheduled work enters normal task execution. It still respects worker capacity, project/model limits, task dependencies, and review requirements.

A scheduled run is not a hidden background mutation. It creates visible task activity, can fail like other work, and should be monitored through Schedule, Tasks, Alerts, and review pages.

Good Uses

Run GitHub Dev Inbox and finder prompts as visible issue-to-PR automation.
Run periodic maintenance prompts.
Let system maintenance keep managed memory and reusable skill libraries healthy over time.
Schedule repository health checks.
Repeat documentation, testing, or cleanup tasks.
Start a known task outside normal working hours.
Create a predictable external workflow without relying on a separate cron script.

System Maintenance

OpenVibely can create visible scheduled system tasks for learning maintenance.

System Task	Purpose
`System: Memory Consolidation`	Uses Memory Curator to keep one project's managed memory focused and accurate.
`System: Skill Library Maintenance`	Uses Skill Curator to keep reusable standalone skills useful over time.

Because these are visible schedules, users can inspect when maintenance is configured and see the resulting task history.

Cautions

Recurring loop tasks should be schedule-driven. Do not add a persisted Task Goal unless the work itself needs goal-driven continuation.
A recurring schedule can repeatedly create model cost and repository changes.
Review the task prompt and auto-merge setting before scheduling.
Disable risky schedules instead of deleting them when you may need the history.
Use Alerts and Insights to monitor failures and trends over time.
Treat scheduled repository-changing work with the same review discipline as manual tasks.

Page	Why It Matters
Task Goals	Use goals on implementation work, not as the default recurrence engine.
Schedule	The UI surface for managing scheduled task runs.
Worker Capacity & Dispatch	Scheduled runs wait for execution capacity when needed.
Memory	Memory Curator can consolidate managed project memory through scheduled system work.
Skill Curation	Skill Curator can keep reusable skills healthy through scheduled system work.
Alerts	Failed runs can create alerts.