autonomous-loopslisted

# Autonomous Loops An autonomous loop is a recurring job: a prompt that runs as your own agent turn on a schedule, with no user in the chat. The bundled loops live as `LOOP.md` files; the ones you create live as `cron_jobs` rows tagged `source = 'agent'` and owned by the current user. Either way, the cron engine fires them and the user can see and control them. Reach for a loop when something genuinely benefits from happening on a cadence: a morning briefing, a weekly review of open commitments, a periodic sweep of a channel. Do not use a loop for one-off work (just do it now) or for anything time-critical (loops fire on a schedule, not instantly). ## Tools You manage your own loops with these in-loop tools (no slash command needed): - `loop_list` — see your loops, their schedules, and status. **Check this first** so you do not create a duplicate. - `loop_create` — create a loop (name, description, schedule, prompt). Starts enabled by default. - `loop_enable` / `loop_disable` — turn one of your loops on or off by name. - `loop_update` — change a loop's schedule or prompt. - `loop_delete` — remove one of your own (`source: 'agent'`) loops. You can only manage loops you created. Bundled loops and ones the user made are theirs to change (via Settings or the CLI), so `loop_update`/`loop_delete` will refuse them. ## Writing a good loop 1. **Pick a clear, kebab-case name** that says what it does: `daily-standup-prep`, `weekly-commitment-review`. 2. **Choose a schedule.** Tw