macroclaw 0.46.0 → 0.47.0

package/src/setup.ts

@@ -63,12 +63,13 @@ export class SetupWizard {
       this.#io.write("  3. Copy the token it gives you (looks like 123456:ABC-DEF...)\n\n");
       const { botToken, bot } = await this.#askBotToken();
 
-      // Chat ID
-      this.#io.write("Next, we need a chat ID. Macroclaw only accepts messages from a single\n");
-      this.#io.write("authorized chat — send /chatid to the bot in Telegram to get yours.\n\n");
-      const defaultChatId = this.#default("chatId");
-      const chatIdPrompt = defaultChatId ? `Chat ID [${defaultChatId}]: ` : "Chat ID: ";
-      const chatId = await this.#askValidated("chatId", chatIdPrompt, defaultChatId);
+      // Admin chat ID
+      this.#io.write("Next, we need the admin chat ID. This is the bootstrap chat with full\n");
+      this.#io.write("control — send /chatid to the bot in Telegram to get yours. Additional\n");
+      this.#io.write("chats can be authorized at runtime via /chatsadd from the admin chat.\n\n");
+      const defaultAdminChatId = this.#default("adminChatId");
+      const adminChatIdPrompt = defaultAdminChatId ? `Admin chat ID [${defaultAdminChatId}]: ` : "Admin chat ID: ";
+      const adminChatId = await this.#askValidated("adminChatId", adminChatIdPrompt, defaultAdminChatId);
 
       // Stop setup bot after chat ID is collected
       await bot.stop();
@@ -103,7 +104,7 @@ export class SetupWizard {
 
       const settings: Settings = settingsSchema.parse({
         botToken,
-        chatId,
+        adminChatId,
         model,
         workspace,
         timeZone,

package/workspace-template/.claude/skills/schedule-event/SKILL.md

@@ -21,10 +21,21 @@ Schedule a new event by adding it to `data/schedule.json`.
 3. Determine job type:
    - **Recurring** → convert to a cron expression in local time. See reference below.
    - **One-time** → compute an ISO 8601 timestamp with the user's timezone offset for `fireAt`
-4. **Be proactive about timing**: if the user says "next week" or "tomorrow" without a specific time, pick the best time based on what you know (their routine, calendar, context)
-5. Append the new job to the `jobs` array
-6. Write the updated file
-7. Confirm: what was scheduled, when it will fire, and offer to adjust
+4. **Route the job to a chat via the `chat` field** — see [Chat routing](#chat-routing) below. When scheduling from a conversation, target the chat the user is talking to you in (read the `<event chat="...">` attribute on the incoming event).
+5. **Be proactive about timing**: if the user says "next week" or "tomorrow" without a specific time, pick the best time based on what you know (their routine, calendar, context)
+6. Append the new job to the `jobs` array
+7. Write the updated file
+8. Confirm: what was scheduled, when it will fire, and offer to adjust
+
+## Chat routing
+
+Every incoming `<event>` has a `chat="<name>"` attribute identifying which chat it came from (e.g. `admin`, `family`). When a scheduled job fires, the bridge delivers the response to the chat named in the job's `chat` field.
+
+- **Default (no `chat` field)** — response goes to the admin chat.
+- **Explicit chat name** — e.g. `"chat": "family"`. Response goes to that chat.
+- **Broadcast** — `"chat": "*"`. The same prompt runs once per authorized chat, and each response is delivered to that chat. Use sparingly — only for genuinely universal reminders.
+
+When the user asks you to schedule something, set `chat` to the chat name from the incoming event's `chat` attribute so the reminder comes back to the same chat. Don't omit `chat` unless you know the job should reach the admin chat specifically.
 
 ## Natural language → job format
 
@@ -52,18 +63,27 @@ Two job types, discriminated by field:
     {
       "name": "morning-summary",
       "cron": "0 7 * * 1-5",
-      "prompt": "Give me a morning summary of my tasks"
+      "prompt": "Give me a morning summary of my tasks",
+      "chat": "admin"
+    },
+    {
+      "name": "family-dinner-poll",
+      "cron": "0 17 * * 5",
+      "prompt": "Ask what everyone wants for dinner",
+      "chat": "family"
     },
     {
       "name": "email-check",
       "cron": "*/30 * * * *",
       "prompt": "Check if any important emails arrived",
-      "model": "haiku"
+      "model": "haiku",
+      "chat": "admin"
     },
     {
       "name": "dentist-reminder",
       "fireAt": "2026-03-15T08:00:00",
-      "prompt": "Reminder: call the dentist to reschedule your appointment"
+      "prompt": "Reminder: call the dentist to reschedule your appointment",
+      "chat": "admin"
     }
   ]
 }
@@ -77,6 +97,7 @@ Two job types, discriminated by field:
 | `cron` | for recurring | Standard cron expression (local time). See reference below. |
 | `fireAt` | for one-time | ISO 8601 timestamp (e.g. `2026-03-15T08:00:00`). Can include a timezone offset (e.g. `2026-03-15T08:00:00+01:00`); without one, the time is interpreted in the configured timezone. |
 | `prompt` | yes | The message sent to the agent when the event fires. Write it as a natural instruction. |
+| `chat` | no | Name of the chat to deliver the response to (e.g. `admin`, `family`). Defaults to `admin`. Use `"*"` to broadcast the prompt to every authorized chat. Match the `chat` attribute from the incoming `<event>` when scheduling from a conversation. |
 | `model` | no | Override the model. Use `haiku` for cheap checks, `opus` for complex reasoning. Omit for default. |
 
 Each job must have exactly one of `cron` or `fireAt` (not both).

package/workspace-template/data/schedule.json

@@ -4,12 +4,14 @@
       "name": "memory-capture",
       "cron": "0 */4 * * *",
       "model": "haiku",
+      "chat": "*",
       "prompt": "Append today's noteworthy events to memory/YYYY-MM-DD.md (create the file and directory if needed). Add a ## HH:MM heading with bullet points underneath. Capture: decisions made, facts learned, user preferences expressed, tasks completed or started, problems solved. Be factual and concise — one line per item. If the file already exists, APPEND only — never overwrite. If nothing meaningful happened since the last entry, respond silently."
     },
     {
       "name": "memory-consolidate",
       "cron": "0 3 * * *",
       "model": "opus",
+      "chat": "admin",
       "prompt": "Read daily logs in memory/ from the past 3 days. Distill durable knowledge into MEMORY.md: confirmed facts, recurring patterns, stable preferences, key decisions, and important context. Remove entries from MEMORY.md that are outdated or contradicted by recent logs. Keep MEMORY.md concise and organized by topic (not chronologically). Do not duplicate entries. If daily logs contain new personal facts about the user (preferences, routines, family, work, interests), update USER.md accordingly. Respond silently."
     }
   ]