[FEATURE] Global "pause all routines" switch to prevent a catch-up burst of missed runs on app launch
Problem Statement:
When the desktop app has been closed for a while, every scheduled task (Routine) that missed its slot catches up at once on next launch — I have multiple routines, and booting the app after some downtime started all of them simultaneously. That's a real problem when I'm intentionally low on token budget: I didn't choose to spend usage on N routine runs at that moment, the app did, just because I opened it. There's currently no way to prevent this short of manually opening each routine and disabling it, then remembering to go back and re-enable each one individually later. With several routines that's tedious and error-prone (easy to forget to re-enable one).
Proposed Solution:
Add a single, global "Pause all routines" switch (Settings, or a toggle in the Routines list) that suspends every routine's automatic firing — including catch-up runs — without touching each task's individual enabled state. Flipping it back off should restore exactly what was enabled before, with no per-task bookkeeping required. This is distinct from (and complements) a per-task "skip missed runs" policy: the global pause is for "I don't want ANY routine spending tokens right now," the per-task setting is for "this specific routine's late runs are pointless."
Alternative Solutions:
Currently the only workaround is opening each routine and toggling enabled: false individually, then manually re-enabling each one later when I'm ready to resume spending on them. This doesn't scale past a couple of routines and risks forgetting to re-enable one.
Priority: High - Significant impact on productivity
Feature Category: Configuration and settings
Use Case Example:
- I have several daily/weekly Routines (log checks, ads checks, etc.) that missed their slots while the app was closed.
- I open the app while intentionally trying to conserve token usage.
- All missed routines fire at once, consuming tokens I did not plan to spend right then.
- With this feature, I'd flip one "pause all routines" switch before opening the app (or as soon as I notice I'm low), preventing any catch-up burst, then flip it back on later without having to remember which of my routines were enabled.
Additional Context:
Related to the broader missed-run/catch-up behavior discussed in #88408 and #81360, but this request is specifically about a global kill-switch for the whole routine set, not fixing catch-up logic per task.