How scheduled tasks work
Onevium schedules run entirely on your machine. The scheduler checks for due tasks every minute, executes the prompt against the Claude API using your key, and stores results in the local database. You can also route results to Feishu, DingTalk, or Discord channels automatically.
Create a scheduled task
Open Automations from the sidebar and click New Automation. Configure the following fields:
- Name — A short label (e.g., "Daily QA pass", "Weekly ops report").
- Prompt — The instructions Claude executes on each run. Write it exactly as you would in a chat message.
- Cron expression — Standard 5-field format: minute, hour, day-of-month, month, day-of-week. Presets are provided for common patterns.
- Project directory — The working directory for the run. Claude has access to the same files and tools as a normal session.
- Model — Choose Opus, Sonnet, or Haiku per task.
- Permission profile — Default (requires approval per action) or Full Access (auto-approves all tools).
Cron expression reference
The cron builder includes preset templates. You can also write custom expressions using standard 5-field syntax.
- */5 * * * * — Every 5 minutes.
- 0 * * * * — Every hour on the hour.
- 0 9 * * * — Daily at 9:00 AM.
- 0 9 * * 1-5 — Weekdays at 9:00 AM.
- 0 9 * * 1 — Weekly on Monday at 9:00 AM.
- 0 17 * * 5 — Every Friday at 5:00 PM.
- 0 0 1 * * — First day of every month at midnight.
Session modes
Each task runs in one of two session modes:
- New session — Creates a fresh session for every run. No context from previous executions. Best for independent jobs like daily reports or monitoring checks.
- Continue session — Reuses the same session across runs. Claude retains full context from all previous executions. Best for iterative tasks like tracking a migration or accumulating data over time.
Notification targets
Route task results to team channels after each run. In the task editor, add notification targets by selecting a channel bot and a specific chat/group. When the task completes, the output is automatically posted to those channels.
This is useful for workflows like: run a daily QA check at 9 AM → post the results to the #qa-reports channel in Feishu.
Manual triggers and run history
Every task can be triggered manually from the Automations page — useful for testing or rerunning a failed job. The run history shows timestamps, status (success/error), and links to the full session conversation for each execution.
Claude can create schedules during chat
The built-in Onevium MCP server exposes schedule management tools to Claude. You can ask Claude to create, list, update, or delete schedules during any conversation. For example: "Create a scheduled task that checks our staging site every morning at 9 AM and posts the results to the ops channel."