Workflows
Scheduled tasks
Run work while you are away.
Define the work once, put it on a schedule, and let it run headless. Results wait in the project when you return.
#How it works
#Create the task
Write the prompt exactly as you would send it in a session — goal, scope, and definition of done included.
scheduled prompt
Every weekday at 08:00: summarize yesterday's commits on main into three bullets and save to notes/standup.md.- Prompt-first. If it runs in a session, it runs on a schedule.
- Explicit done. State where the output goes so results are findable.
#Pick the project and schedule
Attach the task to a project and set when it runs — once, daily, or on an interval. The run executes headless against that project's workspace.
- Project-scoped. Each run sees the project it was attached to.
- Headless runs. No window, no supervision — check the output when you are back.
#Naming note
Scheduled Tasks was previously called Pulse. Use the new name everywhere — routes, settings, and prompts all say Scheduled Tasks.