What You’ll Build
Automated scheduled tasks that:- Run at specified times (cron expressions)
- Execute in your deployed workspace
- Have full file and shell access
- Report results via webhooks
How It Works
Configuration
Define cron jobs in your.chucky.json:
Cron Expression Reference
| Expression | Description |
|---|---|
0 9 * * * | Every day at 9:00 AM |
0 9 * * 1-5 | Weekdays at 9:00 AM |
0 0 * * 0 | Every Sunday at midnight |
0 */6 * * * | Every 6 hours |
0 9 1 * * | First of every month at 9:00 AM |
*/30 * * * * | Every 30 minutes |
Use Case Examples
Daily Code Quality Check
Weekly Security Audit
Daily Dependency Updates
Weekly Documentation Sync
Nightly Test Coverage Report
Monthly Compliance Check
Webhook Integration
Slack Notifications
GitHub Issue Creation
Email Reports
Configuration Options
Full Schema
Option Reference
| Option | Type | Description |
|---|---|---|
cron | string | Cron expression |
message | string | Prompt to send |
timezone | string | IANA timezone (default: UTC) |
model | string | Model to use |
maxTurns | number | Maximum conversation turns |
maxBudgetUsd | number | Budget limit for this job |
systemPrompt | object | System prompt configuration |
tools | object | Tool configuration |
allowedTools | string[] | Whitelist of tools |
disallowedTools | string[] | Blacklist of tools |
permissionMode | string | Permission handling |
callback | object | Webhook configuration |
Managing Cron Jobs
View Active Jobs
Update Schedule
Edit.chucky.json and redeploy:
Disable Temporarily
Comment out or remove the cron entry and deploy:Test Before Scheduling
Run the prompt manually first:Best Practices
1. Set Budget Limits
Always setmaxBudgetUsd to prevent runaway costs:
2. Use Appropriate Models
- Haiku for simple, frequent tasks
- Sonnet for most tasks (good balance)
- Opus for complex analysis (sparingly)