How Scheduled Tasks Are Run

When the scheduled time arrives, Klaus starts a separate session to execute the task prompt, and that session ends when the run is done. Because nobody is watching, this session's permissions are fixed to "allow everything": it will never stop and wait for your confirmation, so do not put anything in the task prompt that you would not be comfortable letting it do outright. The model and thinking effort level you picked in the task are carried into that session; they do not follow your global selection in the composer.

The timeout for a single run defaults to 5 minutes; if the task specifies its own "timeout in seconds", the scheduler uses that value, capped at 24 hours. If the process exits unexpectedly mid-run, records stuck in "running" are marked as failed immediately at the next startup (as "interrupted (app restart)") rather than spinning forever; a separate fallback also reclaims any running row that has stayed unfinished for more than 24 hours. Scheduling and delivery logs are written to ~/.klaus/electron-host.log, as the lines whose kind is cron.