Organize Work
Background Tasks
How Quack keeps background agent work alive — not a scheduler.
There's no scheduler or cron-style automation in Quack yet — this page covers what actually exists: keeping background work alive.
When an agent kicks off a long-running background command, or dispatches a subagent in headless mode, that process can go idle without anyone noticing. Quack watches for it: after a short grace period, if the task looks stalled, it nudges the agent to check in rather than leaving you staring at a silent chat.
What this does not do
- No scheduled or recurring sessions — every chat starts because you (or an agent inside a chat) started it.
- No support for long-lived dev servers that need to keep running past the task that launched them.
If you need a job to run on a schedule, that still lives outside Quack — cron, a CI pipeline, or your own tooling.