Crons

LIST — show current reminders

1. Call CronList. Output is plain text, one line per live job:

   <8hex-id> — <cron-expr> (recurring|one-shot) [session-only|durable]: <prompt>
   

   Empty state is the literal string No scheduled jobs..

2. Read the registry:

   cat "$CLAUDE_PROJECT_DIR/memory/crons.json" | jq -c '.entries[]'
   

3. For each registry entry (skip tombstone != null unless the user asks for audit):

   • ✅ alive — harnessTaskId appears in CronList.
   • ⚠️ missing — expected (paused:false, tombstone:null) but not alive.
   • ⏸ paused — paused: true.
   • 🪦 tombstoned — tombstone != null (only show if user asked).

4. Render a compact table. Example:

   #  STATUS  KEY                         CRON              PROMPT
   1  ✅      heartbeat-default           */30 * * * *      Run /agent:heartbeat
   2  ✅      dreaming-default            0 3 * * *         Use the dream tool...
   3  ⏸       harness-abc12345            0 9 * * *         recordame estirarme
   

ADD — create a new reminder

1. If the user's request is ambiguous (e.g. "remind me tomorrow" without a time), use AskUserQuestion to pin down the cron expression:

   question: "A qué hora del día?",
   options: [ "09:00", "14:00", "18:00", "otra" ]
   

2. Call CronCreate(cron, prompt, durable=true, recurring). The PostToolUse hook captures it automatically into the registry with source: ad-hoc and key harness-<task_id>. No extra writeback call needed.

3. Confirm to the user:

   ✅ Listo. Agendado "<prompt>" para <cron>. Va a sobrevivir cierres de sesión.
   

DELETE — remove a reminder

1. Resolve the user's target to a registry key. Accept either:

   • Registry key directly (e.g. harness-abc12345)
   • 1-based index from the last list output

2. Read registry to find the entry's harnessTaskId and display the cron + prompt.

3. Use AskUserQuestion to confirm:

   question: "¿Borrar el recordatorio '<prompt>' (<cron>)?",
   header: "Confirmación",
   options:
     - label: "Sí, borrar"
     - label: "Cancelar"
   

4. If confirmed:

   • Call CronDelete(id=<harnessTaskId>). PostToolUse auto-tombstones on success.
   • If the entry has no harnessTaskId (already dead / paused), manually tombstone it via:

     bash "$CLAUDE_PLUGIN_ROOT/skills/crons/writeback.sh" tombstone --key <key>
     

PAUSE — temporarily stop without deleting

Pause keeps the registry entry but removes the cron from the harness. Useful for "silence this reminder but don't lose it".

1. Touch the suppression marker so PostToolUse won't tombstone on the upcoming CronDelete:

   touch "$CLAUDE_PROJECT_DIR/memory/.reconciling"
   

2. Read the entry's current harnessTaskId. If non-null, call CronDelete(id=<id>).

3. Mark paused in the registry:

   bash "$CLAUDE_PLUGIN_ROOT/skills/crons/writeback.sh" pause --key <key>
   

4. Remove the marker:

   rm -f "$CLAUDE_PROJECT_DIR/memory/.reconciling"
   

5. Confirm: ⏸ <key> pausado. Usa "/agent:crons resume <key>" para reactivar.

RESUME — re-enable a paused reminder

1. Touch the suppression marker:

   touch "$CLAUDE_PROJECT_DIR/memory/.reconciling"
   

2. Read the entry's cron, prompt, recurring from the registry.

3. Call CronCreate(cron, prompt, durable=true, recurring). Capture the new 8hex task_id from the response.

4. Record the new link:

   bash "$CLAUDE_PLUGIN_ROOT/skills/crons/writeback.sh" resume --key <key> --harness-task-id <new_task_id>
   

5. Remove the marker:

   rm -f "$CLAUDE_PROJECT_DIR/memory/.reconciling"
   

6. Confirm: ▶️ <key> reactivado.

RECONCILE — force a sync

Run the same logic as SessionStart reconcile, on demand:

1. Call CronList.
2. For each registry entry (paused:false, tombstone:null) whose harnessTaskId is not in CronList output: CronCreate + writeback.sh set-alive.
3. Pipe CronList output to writeback.sh adopt-unknown to capture any live-but-unknown crons.
4. Print summary.

IMPORT — bring OpenClaw crons into the registry

Used when the user has an existing ~/.openclaw/cron/jobs.json from a previous OpenClaw agent and wants to port those reminders into this workspace.

Setup: suppress PostToolUse capture during the batch

Imports need custom registry keys (openclaw-<uuid>) and source: openclaw-import. Since PostToolUse would otherwise capture each CronCreate as source: ad-hoc with harness-<id> key, suppress it for the duration:

touch "$CLAUDE_PROJECT_DIR/memory/.reconciling"

Remove the marker at the end of the batch (or via trap on error).

1. Read source

cat ~/.openclaw/cron/jobs.json

The file shape is {"version": 1, "jobs": [...]}. Each job:

{
  "id": "uuid",
  "agentId": "main",
  "name": "Job Name",
  "enabled": true,
  "schedule": { "kind": "cron", "expr": "0 14 * * 3,6", "tz": "America/Santiago" },
  "payload": { "kind": "agentTurn", "message": "prompt here", "model": "opus" },
  "delivery": { "mode": "announce", "channel": "whatsapp" }
}

Iterate data["jobs"], not data.

2. Filter by agent

Use the active agent's ID (check IDENTITY.md or agent-config.json). If ambiguous, ask the user with AskUserQuestion.

3. Classify (3 tiers)

HARD_RED='sessions_spawn|gateway config\.patch|http://192\.168\.|canvas\(|remindctl|wacli|openclaw gateway|HEARTBEAT_OK|NO_REPLY|peekaboo'
SOFT_YELLOW='sessions_send|message\(|~/\.openclaw/|\.openclaw/credentials'

Record the specific reason per item (which token matched which field).

4. Present interactive menu via AskUserQuestion