Schedules
A schedule is recurring work that runs as you — a briefing or report on a cadence, or work done through your connected apps and the web, like “write 2-3 blog posts a week and open a PR on my repo”. Each run reports into the chat it was created in — your workspace chat when you create it on the Schedule page.
Creating a Schedule
Via Chat
Simply tell Chat what you need in plain English:
- “Report every Monday at 9am about all agent activity.”
- “Every Friday, summarize the Marketing project progress.”
- “Write 2-3 blog posts a week and open a PR on my GitHub repo.”
Chat turns the cadence into a cron expression in your time zone and shows one confirm card: the cadence, what each run will do, where it delivers, and which apps it may write to. Nothing is created until you confirm.
Name an agent (“@Research Agent, run the competitor digest every Monday”) and the schedule triggers that agent instead — see Triggers.
Via the Schedule Page
Manage your schedules from Schedule in the workspace sidebar:
New Schedule
Click “New Schedule”. The name is optional — it defaults to the first line of the instructions.
Recurrence
Pick a preset (Daily, Weekly) or write a custom cron expression, and the time zone.
Instructions
Write what each run should do.
Save
Click “Save”. A schedule created here is read-only: it reads your connected apps but changes none. Ask in chat to let it write to an app.
Write Access
Every run may read your connected apps and the web. It may write only to the apps granted on the chat’s confirm card — a write to any other app is refused and fails the run. You can take an app off a schedule’s write list on the Schedule page; adding one always goes through chat, where you confirm it on a card.
Execution Workflow
Interval Check
Tulsk checks for due schedules every 15 minutes. A schedule whose previous run is still in progress skips that fire.
The Run
The run works on your workspace computer, as you, with the board’s tasks and recent agent activity as context. Its model tokens and compute draw on your plan allowance.
Delivery
The result is posted in the schedule’s chat and sent to any email or connected-app destinations, and you get an inbox notification. A run that does not finish — out of time, out of steps, a refused write — says why in the chat.
Scheduling
The system automatically computes the next run time from the cron rule and time zone.
Run Now
Run now, in a schedule’s edit dialog, starts a real run immediately — it can act, exactly as a scheduled fire would. One run of a schedule happens at a time.
Who Can Change a Schedule
A schedule runs as its owner, so only the owner can edit, resume, run or delete it. Anyone in the workspace can pause it.
Cron Presets Reference
| Recurrence | Cron Expression |
|---|---|
| Daily at 9am | 0 9 * * * |
| Mon at 9am | 0 9 * * 1 |
| Fri at 5pm | 0 17 * * 5 |
| Monthly (1st) | 0 9 1 * * |