ticlawk 0.1.17-dev.5 → 0.1.17-dev.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticlawk",
-  "version": "0.1.17-dev.5",
+  "version": "0.1.17-dev.6",
   "description": "Local connector that links agent harnesses (Claude Code, Codex, OpenClaw, opencode, Pi) to the Ticlawk mobile app.",
   "type": "module",
   "main": "ticlawk.mjs",

package/src/adapters/ticlawk/api.mjs

@@ -375,7 +375,7 @@ export async function getAgentServerInfo({ actingAgentId }) {
 // ── Reminders ──
 
 export async function scheduleAgentReminder({
-  actingAgentId, title, fireAt, anchorConversationId, anchorMessageId,
+  actingAgentId, title, fireAt, anchorConversationId, anchorMessageId, recurrence,
 }) {
   return apiFetch('/api/agent/reminders', {
     method: 'POST',
@@ -385,6 +385,7 @@ export async function scheduleAgentReminder({
       fire_at: fireAt,
       anchor_conversation_id: anchorConversationId,
       anchor_message_id: anchorMessageId ?? null,
+      recurrence: recurrence ?? null,
     }),
   });
 }

package/src/cli/agent-commands.mjs

@@ -557,6 +557,18 @@ export async function runReminderScheduleCommand(args) {
     console.error('--target or --anchor-conversation-id is required');
     return 2;
   }
+  // Optional recurrence: --recur-at HH:MM [--recur-tz <IANA>] [--recur-weekday 1,2,3].
+  // --fire-at remains the FIRST occurrence; the rule advances it after each fire.
+  let recurrence = null;
+  const recurAt = getArg(args, 'recur-at');
+  if (recurAt) {
+    const tz = getArg(args, 'recur-tz') || 'UTC';
+    const wdRaw = getArg(args, 'recur-weekday');
+    const byWeekday = wdRaw
+      ? String(wdRaw).split(',').map((s) => parseInt(s.trim(), 10)).filter((n) => n >= 1 && n <= 7)
+      : [];
+    recurrence = { at: recurAt, tz, ...(byWeekday.length ? { by_weekday: byWeekday } : {}) };
+  }
   const res = await daemonRequest({
     method: 'POST',
     path: '/agent/reminder/schedule',
@@ -567,6 +579,7 @@ export async function runReminderScheduleCommand(args) {
       target,
       anchor_conversation_id: anchorConversationId,
       anchor_message_id: anchorMessageId,
+      recurrence,
     },
   });
   printJson(res.body);
@@ -1425,7 +1438,7 @@ export const AGENT_COMMAND_HELP = {
     to a user, use \`ticlawk message send --attach <file>\` instead.
 `,
   reminder: `ticlawk reminder <schedule|list|snooze|update|cancel|log>
-  ticlawk reminder schedule --title <t> (--fire-at <iso> | --in-seconds N | --in-minutes N) (--target "<target>" | --anchor-conversation-id <id>) [--anchor-message-id <id>]
+  ticlawk reminder schedule --title <t> (--fire-at <iso> | --in-seconds N | --in-minutes N) (--target "<target>" | --anchor-conversation-id <id>) [--anchor-message-id <id>] [--recur-at HH:MM [--recur-tz <IANA>] [--recur-weekday 1,2,3]]
   ticlawk reminder list [--status active|fired|canceled]
   ticlawk reminder snooze <reminder-id> (--fire-at <iso> | --in-seconds N | --in-minutes N)
   ticlawk reminder update <reminder-id> [--title <t>] [--fire-at <iso>]
@@ -1435,6 +1448,17 @@ export const AGENT_COMMAND_HELP = {
   Use reminders for follow-up that depends on future state you cannot resolve
   now. A reminder fires by posting a system message into the anchor
   conversation and waking the owner agent via an explicit delivery.
+
+  RECURRING: for a fixed cadence (e.g. a daily/weekly meal-time check-in), use
+  ONE recurring reminder instead of enumerating many one-shots. Pass --recur-at
+  (local HH:MM), --recur-tz (the owner's IANA timezone), and optionally
+  --recur-weekday (ISO 1=Mon..7=Sun, comma-separated; omit for every day).
+  --fire-at is still the FIRST occurrence; on each fire the reminder
+  auto-advances to the next occurrence and stays active. Example — weekday
+  18:30 Beijing dinner check-in:
+    ticlawk reminder schedule --title "晚餐" --anchor-conversation-id <id> \\
+      --fire-at <next 18:30 Beijing as ISO> \\
+      --recur-at 18:30 --recur-tz Asia/Shanghai --recur-weekday 1,2,3,4,5
 `,
   task: `ticlawk task <create|claim|unclaim|update|list>
   ticlawk task create --target "<target>" [--title <t>] [--assign-agent <agent-id>]

package/src/core/agent-cli-handlers.mjs

@@ -590,6 +590,7 @@ export async function handleReminderSchedule(req, body, ctx) {
       fireAt: body.fire_at,
       anchorConversationId,
       anchorMessageId: body?.anchor_message_id || null,
+      recurrence: body?.recurrence ?? null,
     });
     debugLog('agent-cli', 'reminder.schedule', {
       actingAgentId,

package/src/runtimes/_shared/handbook/SURFACES.md

@@ -39,3 +39,5 @@ Use `ticlawk credential request --name <ENV_VAR>` to create the credential slot.
 ## Reminders
 
 Use reminders only for external/time-based future follow-up or visible, persistent resume conditions. Do not use reminders to defer executable work or an owner decision that should be requested now.
+
+For a fixed cadence (a daily or weekly check-in, e.g. meal-time reminders), use ONE recurring reminder, not many enumerated one-shots: `ticlawk reminder schedule ... --recur-at HH:MM --recur-tz <owner IANA tz> [--recur-weekday 1,2,3]`. It auto-advances to the next occurrence on each fire and stays active, so the cadence never runs out.