scheduled-jobs

To schedule recurring tasks, you configure self-contained prompts with defined output destinations and set a frequency using Desktop scheduled tasks for always-on jobs or Claude Code /loop sessions for short-term polling. This automates daily briefings and periodic reflections without manual initiation.

Desktop scheduled tasks are always-on recurring jobs that survive system restarts for long-term automation like daily briefings, while /loop sessions are session-scoped polling mechanisms for short-term automation such as checking deployment status every few minutes during an active session.

Yes, scheduled tasks apply to personal workflow automation by using standard self-contained prompt templates that read from and write to personal-os files. This enables automated daily briefings, weekly summaries, and reflection passes to update your system files directly.

To set up a daily morning briefing, define a self-contained prompt that reads your priorities and writes a summary to the logs folder, then configure the daily frequency using Desktop scheduled tasks. Test the prompt manually before scheduling to ensure correct file outputs.

Safety guidelines for automated recurring jobs require defining self-contained prompts, explicitly defining output destinations for generated summaries, and testing tasks manually before scheduling them to prevent unintended file overwrites within your personal-os structure.

No external dependencies are required. You can run periodic reflections and weekly summaries by configuring self-contained prompts within Desktop scheduled tasks or Claude Code /loop sessions, relying entirely on your existing personal-os files for reading and writing outputs.