← ClaudeAtlas

looplisted

Schedule the recurring autopilot heartbeat. Calls CronCreate to fire one autopilot tick every ~15 min. Triggers on: /loop, start the loop, run the loop, autonomous mode, kick off the heartbeat.
atrislabs/atris · ★ 67 · AI & Automation · score 72
Install: claude install-skill atrislabs/atris
# /loop Schedules the recurring autopilot heartbeat. One tick fires roughly every 13–17 minutes via Claude Code's cron system. ## What it does 1. Calls `CronCreate` with a recurring schedule (off-clock minute to avoid fleet sync at :00 / :30) 2. The cron prompt first invokes `atris mission run --due --max-ticks 1 --complete-on-pass`; if no mission is due, it invokes `/autopilot` 3. Returns the cron job id so the user can stop it later with `CronDelete` 4. Lists the active cron jobs via `CronList` so the user can see the heartbeat is alive 5. Runs from a dedicated active task for this loop; a completed task is never reused as the scheduler host ## How to invoke User says "run /loop", "start the loop", "kick off autonomous mode", or "make autopilot recurring". The agent then: 1. Checks that the current task is active and dedicated to this loop. If it is complete or belongs to other work, stop and create a new dedicated task before scheduling. 2. Calls `CronCreate` with these args (use whatever off-clock minute you land on, do not pin to :00 or :30): - `cron`: `"*/13 * * * *"` (every 13 min) for tight loops, or `"7 * * * *"` (hourly at :07) for slow loops - `prompt`: `"First run: atris mission run --due --max-ticks 1 --complete-on-pass. If it reports no_due_mission, run /autopilot for one tick. One bounded goal only, then stop. Do not start a conversation."` - `recurring`: `true` - `durable`: `false` (in-memory only, gone when this Claude session ends) 3. Afte