How Scheduled Tasks Are Run

Each run initializes a separate conversation from its saved location and permission preset, with restart recovery.

When the scheduled time arrives, Klaus starts a separate conversation to execute the task prompt. The saved plain, project, or workspace location determines its initial directories, and the saved permission preset chooses user approval, automatic review, or full access. Runtime execution uses the ordinary conversation policy, while older tasks retain their previous full-access default. The saved model and thinking effort are carried into that conversation and do not follow the global composer selection.

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.