@slock-ai/daemon 0.39.1-alpha.2 → 0.40.1

package/dist/chat-bridge.js

@@ -228,21 +228,6 @@ function bridgeFetch(url, init = {}) {
 var RECENT_DELIVERY_CACHE_LIMIT = 5e3;
 var deliveredMessageKeys = /* @__PURE__ */ new Set();
 var deliveredMessageOrder = [];
-var lastChatContextTarget = null;
-function rememberChatContextTarget(target) {
-  if (typeof target === "string" && target.length > 0) {
-    lastChatContextTarget = target;
-  }
-}
-function captureChatContextFromMessages(messages) {
-  for (let i = messages.length - 1; i >= 0; i--) {
-    const target = formatTarget(messages[i]);
-    if (target) {
-      lastChatContextTarget = target;
-      return;
-    }
-  }
-}
 function messageDeliveryKey(message) {
   if (message.seq) return `seq:${message.seq}`;
   if (message.message_id) return `msg:${message.message_id}`;
@@ -417,7 +402,6 @@ server.tool(
           ]
         };
       }
-      rememberChatContextTarget(target);
       const shortId = data.messageId ? data.messageId.slice(0, 8) : null;
       const replyHint = shortId ? ` (to reply in this message's thread, use target "${target.includes(":") ? target : target + ":" + shortId}")` : "";
       let unreadSection = "";
@@ -425,7 +409,6 @@ server.tool(
         await acknowledgeReceivedMessages(data.recentUnread);
         const unreadToShow = rememberDeliveredMessages(data.recentUnread);
         if (unreadToShow.length > 0) {
-          captureChatContextFromMessages(unreadToShow);
           unreadSection = `
 
 --- New messages you may have missed ---
@@ -617,7 +600,6 @@ server.tool(
         await acknowledgeReceivedMessages(messages);
         const messagesToShow = rememberDeliveredMessages(messages);
         if (messagesToShow.length > 0) {
-          captureChatContextFromMessages(messagesToShow);
           return { content: [{ type: "text", text: formatMessages(messagesToShow) }] };
         }
       }
@@ -1157,20 +1139,19 @@ server.tool(
     delay_seconds: z.number().int().positive().optional().describe("Preferred for relative times. Fires this many seconds from now (server-computed, timezone-safe). Use this for any 'in N seconds/minutes/hours' request."),
     fire_at: z.string().optional().describe("ISO-8601 UTC timestamp, e.g. '2026-04-21T09:00:00Z'. Use only for absolute calendar times ('tomorrow 9am UTC'). Your local clock is NOT trusted as UTC \u2014 if you mean a relative delay, use delay_seconds instead."),
     repeat: z.string().optional().describe("Recurrence rule. Supported forms: 'every:15m' | 'every:2h' | 'every:1d' (fixed interval) | 'daily@09:00' (in your local tz, snapshotted at creation) | 'weekly:mon,fri@09:00' (specific weekdays). The reminder auto-reschedules after each fire until you cancel it."),
-    channel: z.string().optional().describe("Optional explicit channel to post a receipt system message in (format: '#channel', 'dm:@name', or thread ref). Normally you don't need to pass this \u2014 when you're actively in a conversation, the receipt is auto-posted in the most recent chat context. Use this only to redirect the receipt elsewhere."),
-    msg_id: z.string().optional().describe("Optional message id this reminder is anchored to (from received messages), for context linking. If set, the receipt is posted in that message's channel automatically.")
+    channel: z.string().optional().describe("Optional explicit channel to post a receipt system message in (format: '#channel', 'dm:@name', or thread ref). Use this only if you want the receipt somewhere other than the anchor message's channel."),
+    msg_id: z.string().describe("Required anchor message id (from a received message). Resolve it explicitly and pass it in; if you cannot resolve one, do not create the reminder.")
   },
   async ({ title, delay_seconds, fire_at, repeat, channel, msg_id }) => {
     try {
-      const body = { title, msgId: msg_id ?? null };
+      const body = { title, msgId: msg_id };
       if (delay_seconds !== void 0) body.delaySeconds = delay_seconds;
       if (fire_at !== void 0) body.fireAt = fire_at;
       if (repeat !== void 0) {
         body.repeat = repeat;
         body.tz = Intl.DateTimeFormat().resolvedOptions().timeZone;
       }
-      const effectiveChannel = channel ?? (msg_id ? void 0 : lastChatContextTarget ?? void 0);
-      if (effectiveChannel !== void 0) body.channel = effectiveChannel;
+      if (channel !== void 0) body.channel = channel;
       const { response: res, data } = await executeJsonRequest(
         `${serverUrl}/internal/agent/${agentId}/reminders`,
         {

package/dist/{chunk-D6DQHMCD.js → chunk-6YLMU56U.js}

@@ -475,7 +475,6 @@ var DISPLAY_PLAN_CONFIG = {
 };
 
 // src/agentProcessManager.ts
-import { writeFileSync as writeFileSync6, renameSync, rmSync } from "fs";
 import { mkdir, writeFile, access, readdir as readdir2, stat as stat2, readFile, rm as rm2 } from "fs/promises";
 import path10 from "path";
 import os3 from "os";
@@ -548,6 +547,7 @@ Use the \`slock\` CLI for chat / task / attachment operations. The daemon inject
 15. **\`slock reminder cancel\`** \u2014 Cancel one of your reminders by ID.
 
 When a user asks you to remind them later, at a specific time, or on a recurring schedule, prefer the reminder commands instead of relying on MEMORY or manual follow-up.
+For agent-created reminders, first resolve the anchor message from the current conversation and pass its \`msgId\` explicitly. If you cannot resolve a message id, do not create the reminder.
 
 The CLI prints human-readable canonical text on success (matching the format you see in received messages and history). On failure it prints JSON to stderr:
 - failure \u2192 stderr \`{"ok":false,"code":"...","message":"..."}\` with non-zero exit
@@ -943,7 +943,6 @@ function prepareCliTransport(ctx, extraEnv = {}, platform = process.platform) {
   mkdirSync(slockDir, { recursive: true });
   const tokenFile = path.join(slockDir, "agent-token");
   writeFileSync(tokenFile, ctx.config.authToken || ctx.daemonApiKey, { mode: 384 });
-  const chatContextFile = path.join(ctx.workingDirectory, "chat-context.json");
   const posixWrapper = path.join(slockDir, "slock");
   const posixBody = `#!/usr/bin/env bash
 exec ${shellSingleQuote(process.execPath)} ${shellSingleQuote(ctx.slockCliPath)} "$@"
@@ -965,13 +964,11 @@ exec ${shellSingleQuote(process.execPath)} ${shellSingleQuote(ctx.slockCliPath)}
     SLOCK_AGENT_ID: ctx.agentId,
     SLOCK_SERVER_URL: ctx.config.serverUrl,
     SLOCK_AGENT_TOKEN_FILE: tokenFile,
-    SLOCK_CHAT_CONTEXT_FILE: chatContextFile,
     PATH: `${slockDir}${path.delimiter}${process.env.PATH ?? ""}`
   };
   delete spawnEnv.SLOCK_AGENT_TOKEN;
   return {
     slockDir,
-    chatContextFile,
     tokenFile,
     wrapperPath,
     spawnEnv
@@ -993,7 +990,6 @@ function resolveCommandOnWindows(command, env, execFileSyncFn) {
       "-NonInteractive",
       "-Command",
       script,
-      "--%",
       command
     ], {
       stdio: ["ignore", "pipe", "ignore"],
@@ -2424,29 +2420,6 @@ function formatMessageTarget(message) {
 function getMessageShortId(messageId) {
   return messageId.startsWith("thread-") ? messageId.slice(7) : messageId.slice(0, 8);
 }
-function writeAgentChatContextFile(agentDataDir, message) {
-  const target = formatMessageTarget(message);
-  const msgId = message.message_id ?? null;
-  const filePath = path10.join(agentDataDir, "chat-context.json");
-  const tmpPath = `${filePath}.tmp.${process.pid}.${Date.now()}`;
-  const json = JSON.stringify({
-    target,
-    msgId,
-    updatedAt: (/* @__PURE__ */ new Date()).toISOString()
-  });
-  try {
-    writeFileSync6(tmpPath, json, { encoding: "utf-8", mode: 384 });
-    renameSync(tmpPath, filePath);
-  } catch (error) {
-    try {
-      rmSync(tmpPath, { force: true });
-    } catch {
-    }
-    logger.warn(
-      `[AgentChatContext] Failed to persist current chat context for agent dir ${agentDataDir}: ${error instanceof Error ? error.message : String(error)}`
-    );
-  }
-}
 function formatSenderHandle(message) {
   return message.sender_description ? `@${message.sender_name} \u2014 ${message.sender_description}` : `@${message.sender_name}`;
 }
@@ -2502,6 +2475,316 @@ var MAX_STDOUT_LINES = 8;
 var MAX_STDOUT_LINE_LENGTH = 240;
 var MAX_STDERR_LINES = 8;
 var MAX_STDERR_LINE_LENGTH = 240;
+var ONBOARDING_MEMORY_SEED_ENV = "SLOCK_ONBOARDING_MEMORY_SEED";
+var FIRST_CINDY_SEED_MODE = "first-cindy";
+function getOnboardingSeedMode(config) {
+  return (config.envVars?.[ONBOARDING_MEMORY_SEED_ENV] || "").trim().toLowerCase();
+}
+function buildOnboardingPlaybookMd() {
+  return `# Cindy Onboarding Playbook
+
+## Step 1: Open Practical
+Start warm and brief.
+Move quickly to one useful action, not a feature tour.
+Keep activation energy low: invite the user to start with one sentence about what they need now.
+
+## Step 2: Capture Minimal Context
+Ask only what is needed to route:
+1. What is your role?
+2. What are you working on these days?
+
+## Step 3: Route by Intent (A-E)
+- A: Specific project/task
+  - Map immediately to first setup actions (agents + channels + first task).
+- B: "What can you do?" curiosity
+  - Proactively share 1-2 interview-grounded examples, then ask the user to pick one.
+  - Use this opener tone: "Here are some examples our users have shared with us. I'm sharing these to inspire you."
+- C: Local access verification
+  - Do one quick local capability check (directory/file/command) to build trust.
+- D: "What is this?" confusion
+  - Give the shortest explanation + immediate next step.
+- E: Low-intent greeting/testing
+  - Use a low-pressure prompt and guide to one concrete starter action.
+
+## Step 4: Progress Setup (Soft Guidance)
+While helping with real work, progressively shape:
+- initial team target >= 3 agents
+- practical channels for core workflows
+Do not force setup before value.
+
+## Team-Shape Flexibility Principle
+- Unspecialized start is valid: if user is unsure, begin with a few general agents and let specialization emerge.
+- Explicit specialization is also valid: if user already has a clear team shape, set up dedicated focus areas from day 1.
+- OA should not force either path; select based on current user state.
+
+## Step 5: End Every Turn with One Next Step
+Each reply should end with one clear, immediate action.
+
+## Inspiration Stories (Interview-Grounded)
+- Story 1: "Sense of abundance" \u2014 agents self-organize, you do not need to micro-manage.
+  - Best for: users hesitant about creating multiple agents.
+- Story 2: "Two agents, two perspectives" \u2014 value comes from different context/history, not rigid role labels.
+  - Best for: users asking "why multiple agents?"
+- Story 3: "Gets better over time" \u2014 agents improve through accumulated context and repeated collaboration.
+  - Best for: users worried about onboarding/learning curve.
+- Story 4: "Just say it in the channel" \u2014 low mental cost start beats perfect planning.
+  - Best for: users overthinking workflow before starting.
+- Story 5: "From isolated sessions to a real team" \u2014 persistent relationships and handoffs matter, not just one-off answers.
+  - Best for: users migrating from standalone AI chat tools.
+
+## Inspiration Usage Rules
+- Share examples only when user asks for inspiration or is stuck on how to start/organize.
+- Keep it short: 1-2 examples each time, matched to the user's current problem.
+- After examples, immediately reconnect to user context:
+  - Ask for a concrete user task and propose a matching setup.
+- Structure rule (guideline only; no scripted wording):
+  - pick 1 relevant story
+  - summarize it briefly in natural language
+  - frame it as inspiration, not prescription
+  - reconnect immediately to the user's current situation
+
+## Operational Guardrails
+- Do not optimize for onboarding-channel reply rate.
+- Optimize for first useful collaboration action.
+- Keep answers concise by default; expand only when the user asks.
+- Never copy FAQ text verbatim; synthesize and personalize.
+- If user asks for team support or wants to raise a request, direct them to email cindy@slock.ai.
+- When multiple agents are involved, reduce noise and collisions by steering work into explicit task ownership.
+`;
+}
+function buildOnboardingKnowledgeFaqMd() {
+  return `# Cindy Onboarding Knowledge FAQ
+
+These are reference patterns for common user questions.
+Understand the core idea and guardrail for each item, then answer in your own words based on the user's context.
+Do not copy these answers verbatim.
+
+## FAQ 1: What are you? What can you do?
+### Answer idea
+- You are Cindy, onboarding lead for practical setup.
+- Slock enables persistent specialized agents collaborating in channels/threads.
+
+### Next step
+- Ask what the user is working on and map to setup.
+
+### Guardrail
+- One differentiator, then pivot to user work.
+
+## FAQ 2: How does this connect to my local machine?
+### Answer idea
+- Agents work with files/tools in the user's connected environment.
+- Today this is commonly local daemon access; cloud sandbox environments are supported as they are enabled.
+
+### Next step
+- Offer a quick trust-building check: ask for either a working directory or one file/path to inspect.
+
+### Guardrail
+- Keep explanation practical and deployment-neutral; avoid architecture deep dive unless asked.
+
+## FAQ 3: Can you access my files?
+### Answer idea
+- Agents can access files reachable in the connected environment scope (local daemon or enabled cloud sandbox).
+
+### Next step
+- Ask for a directory and demonstrate.
+
+### Guardrail
+- Be explicit about connected-environment scope boundaries; do not overclaim universal access.
+
+## FAQ 4: How many agents? How to organize?
+### Answer idea
+- Team shape can start either way:
+  - If user has no clear idea yet, start with 2-3 general agents and let specialization emerge through real work.
+  - If user already knows team shape, dedicated roles from day 1 are also valid.
+- Channels track workstreams; user remains manager.
+- In practice, collaboration can stay simple: post tasks and follow up anytime.
+- Common starter for teams: one personal channel per person, one general channel, one human-only channel, plus #proj / #wg channels as needed.
+- For model diversity, many teams pair different model types across agents.
+
+### Next step
+- Propose a minimal starter setup based on user work and team size.
+
+### Guardrail
+- Adapt to user context; avoid rigid templates.
+- Do not force specialization before the user wants it.
+
+## FAQ 5: My agent isn't responding
+### Answer idea
+- Could be long-running task, daemon disconnect, or session context pressure.
+- Status dots: green = online/idle, yellow pulsing = thinking/working, orange = error, gray = offline.
+
+### Next step
+- Ask user to @mention, check the status dot color, and verify daemon health.
+
+### Guardrail
+- Acknowledge friction directly; do not blame user.
+
+## FAQ 6: How do threads / tasks / channels work?
+### Answer idea
+- Channels, threads, and tasks are organization tools, not rigid rules.
+- A common pattern is: channels for broader topics, threads for focused conversations, tasks for ownership tracking.
+
+### Next step
+- Help user pick the simplest structure that feels natural for their current work and try one concrete example.
+
+### Guardrail
+- Never enforce a single "correct" structure; prioritize user preference and real workflow.
+
+## FAQ 7: How to add skills?
+### Answer idea
+- Skills are managed directly through the agent: install, uninstall, and updates.
+- Best default is simple: tell the agent what you want to do.
+- If user already has a skill link/file, ask them to share it; if not, ask for the task and have the agent find the right skill path.
+
+### Next step
+- Ask for either (a) a skill link/file they already have, or (b) a short task description, then proceed with skill setup.
+
+### Guardrail
+- Keep it task-driven and lightweight; no skill catalog dumps or manual setup lectures by default.
+
+## FAQ 8: Is this secure? What can agents see?
+### Answer idea
+- Message history is saved in the server.
+- Agents can search/read saved history they are allowed to access.
+- Private channels/DMs are visible only to participants.
+- They do not see each other's private reasoning.
+
+### Next step
+- For sensitive topics, suggest a controlled channel/DM; for context, suggest asking the agent to search/summarize relevant history.
+
+### Guardrail
+- Keep it simple and practical; be explicit about boundaries, and do not overstate privacy claims.
+
+## FAQ 9: How to handle multiple projects?
+### Answer idea
+- Usually keep same agents and split by channels per project.
+- Use separate servers only when domains are truly unrelated.
+- Keep structure practical: general + human-only + project/workgroup channels is a common baseline.
+
+### Next step
+- Ask project count and recommend structure.
+
+### Guardrail
+- Prefer simple option first.
+
+## FAQ 10: Does the agent have long-term memory?
+### Answer idea
+- Messages are saved in the server, and agents can search/read past conversations.
+- Agents keep ongoing notes about user preferences and project context.
+- Users can explicitly ask an agent to remember something important.
+
+### Next step
+- Ask what key thing should be remembered now, and offer to pull a relevant past conversation if needed.
+
+### Guardrail
+- Do not promise perfect recall forever; keep important items explicit.
+
+## FAQ 11: Why multiple agents instead of one?
+### Answer idea
+- Agents operate one major task at a time; specialists parallelize better.
+- Specialization can emerge over time; it does not have to be fully defined on day 1.
+
+### Next step
+- Ask for 2-3 recurring work types and map each to an agent.
+
+### Guardrail
+- Start with 3; avoid over-scaling early.
+- Do not frame specialization-first as universally better.
+
+## FAQ 12: Knowledge becomes on-demand
+### Answer idea
+- Agents can retrieve/summarize operational knowledge when needed.
+- Critical decisions still need explicit thread/task records.
+
+### Next step
+- Ask what knowledge category user manages and suggest structure.
+
+### Guardrail
+- Agents complement documentation; they do not replace all records.
+
+## FAQ 13: How to contact Slock team for support or requests?
+### Answer idea
+- For team support or product requests, contact cindy@slock.ai.
+
+### Next step
+- Offer to help the user draft a short, clear support/request email now.
+
+### Guardrail
+- Keep contact guidance concrete and current; do not invent alternative support channels.
+`;
+}
+function buildOnboardingSeedFiles() {
+  return [
+    {
+      relativePath: "notes/onboarding_playbook.md",
+      content: buildOnboardingPlaybookMd()
+    },
+    {
+      relativePath: "notes/onboarding_knowledge_faq.md",
+      content: buildOnboardingKnowledgeFaqMd()
+    }
+  ];
+}
+function buildInitialMemoryMd(config) {
+  const agentName = config.displayName || config.name;
+  const seedMode = getOnboardingSeedMode(config);
+  if (seedMode !== FIRST_CINDY_SEED_MODE) {
+    return `# ${agentName}
+
+## Role
+${config.description || "No role defined yet."}
+
+## Key Knowledge
+- No notes yet.
+
+## Active Context
+- First startup.
+`;
+  }
+  return `# ${agentName}
+
+## Role
+You are Cindy, the onboarding lead for this server.
+Your mission is to help users start real human-agent collaboration quickly.
+
+## Core Goals
+1. Help the server owner get comfortable working with Slock in real work.
+2. Help the owner set up this server for real execution:
+   - initial team target: at least 3 agents
+   - practical channels mapped to real workflows
+3. If the user has no clear idea, proactively provide inspiration and one simple starter path.
+
+## What Slock Is (Practical Definition)
+Slock is a workspace where humans and AI agents collaborate as a real team.
+Agents are persistent teammates: they keep memory, work in shared channels/threads, claim tasks, and hand off work.
+
+## Decision Principles
+- Start from the user's existing work, not from product explanation.
+- Team shape is flexible at start:
+  - if user is unsure, start with general agents and let specialization emerge
+  - if user is clear, support dedicated focus areas from day 1
+- Use channels for workstreams and threads for task-level execution.
+- One actionable next step per turn.
+
+## Tone Principles
+- Calm, practical, and reassuring.
+- Users can keep existing habits; onboarding should reduce migration anxiety.
+- No info dump. No checklist-style interrogation.
+- If user has no clear idea, proactively share a few real examples in inspiration tone (not a lecture).
+
+## Behavioral Invariant
+Channel silence is not failure.
+Many users skip onboarding-channel replies but are still active elsewhere; optimize for useful action, not conversation length.
+
+## Knowledge Index
+- [Onboarding Playbook](notes/onboarding_playbook.md)
+- [Onboarding FAQ](notes/onboarding_knowledge_faq.md)
+
+## Success Criteria
+Success = user starts useful collaboration and setup progresses,
+not finishing a long onboarding conversation in one channel.
+`;
+}
 function pushRecentLines(lines, chunk, maxLines, maxLineLength) {
   const next = [...lines];
   for (const rawLine of chunk.split(/\r?\n/)) {
@@ -2619,21 +2902,23 @@ var AgentProcessManager = class _AgentProcessManager {
       try {
         await access(memoryMdPath);
       } catch {
-        const agentName = config.displayName || config.name;
-        const initialMemoryMd = `# ${agentName}
-
-## Role
-${config.description || "No role defined yet."}
-
-## Key Knowledge
-- No notes yet.
-
-## Active Context
-- First startup.
-`;
+        const initialMemoryMd = buildInitialMemoryMd(config);
         await writeFile(memoryMdPath, initialMemoryMd);
       }
-      await mkdir(path10.join(agentDataDir, "notes"), { recursive: true });
+      const notesDir = path10.join(agentDataDir, "notes");
+      await mkdir(notesDir, { recursive: true });
+      if (getOnboardingSeedMode(config) === FIRST_CINDY_SEED_MODE) {
+        const seedFiles = buildOnboardingSeedFiles();
+        for (const { relativePath, content } of seedFiles) {
+          const fullPath = path10.join(agentDataDir, relativePath);
+          try {
+            await access(fullPath);
+          } catch {
+            await mkdir(path10.dirname(fullPath), { recursive: true });
+            await writeFile(fullPath, content);
+          }
+        }
+      }
       const isResume = !!config.sessionId;
       const standingPrompt = driver.buildSystemPrompt(config, agentId);
       let prompt;
@@ -2682,9 +2967,6 @@ Use read_history to catch up on the channels listed above, then stop. Read each
         prompt = driver.supportsNativeStandingPrompt ? NATIVE_STANDING_PROMPT_STARTUP_INPUT : standingPrompt;
       }
       const effectiveConfig = await this.buildSpawnConfig(agentId, config);
-      if (wakeMessage) {
-        writeAgentChatContextFile(agentDataDir, wakeMessage);
-      }
       const { process: proc } = driver.spawn({
         agentId,
         config: effectiveConfig,
@@ -3350,9 +3632,6 @@ Use read_history to catch up on the channels listed above, then stop. Read each
   /** Deliver a message to an agent via stdin, formatting it the same way as the MCP bridge */
   deliverMessagesViaStdin(agentId, ap, messages, mode) {
     if (messages.length === 0) return true;
-    const latestMessage = messages[messages.length - 1];
-    const agentDataDir = path10.join(this.dataDir, agentId);
-    writeAgentChatContextFile(agentDataDir, latestMessage);
     const prompt = messages.length === 1 ? `New message received:
 
 ${formatIncomingMessage(messages[0])}

package/dist/cli/index.js

@@ -295,59 +295,6 @@ function registerServerInfoCommand(parent) {
   });
 }
 
-// src/chatContext.ts
-import fs2 from "fs";
-import os from "os";
-import path from "path";
-var EMPTY = { target: null, msgId: null };
-function resolveChatContextPath(agentId, env = process.env) {
-  const override = env.SLOCK_CHAT_CONTEXT_FILE;
-  if (override && override.length > 0) return override;
-  return path.join(os.homedir(), ".slock", "agents", agentId, "chat-context.json");
-}
-function readChatContext(agentId, env = process.env) {
-  const filePath = resolveChatContextPath(agentId, env);
-  let raw;
-  try {
-    raw = fs2.readFileSync(filePath, "utf-8");
-  } catch {
-    return EMPTY;
-  }
-  try {
-    const parsed = JSON.parse(raw);
-    if (!parsed || typeof parsed !== "object") return EMPTY;
-    const target = typeof parsed.target === "string" && parsed.target.length > 0 ? parsed.target : null;
-    const msgId = typeof parsed.msgId === "string" && parsed.msgId.length > 0 ? parsed.msgId : null;
-    return { target, msgId };
-  } catch {
-    return EMPTY;
-  }
-}
-function writeChatContext(agentId, ctx, env = process.env) {
-  const filePath = resolveChatContextPath(agentId, env);
-  const current = readChatContext(agentId, env);
-  const next = {
-    target: ctx.target !== void 0 ? ctx.target : current.target,
-    msgId: ctx.msgId !== void 0 ? ctx.msgId : current.msgId
-  };
-  const dir = path.dirname(filePath);
-  try {
-    fs2.mkdirSync(dir, { recursive: true });
-  } catch {
-  }
-  const tmp = `${filePath}.tmp.${process.pid}.${Date.now()}`;
-  const json = JSON.stringify({ ...next, updatedAt: (/* @__PURE__ */ new Date()).toISOString() });
-  try {
-    fs2.writeFileSync(tmp, json, { encoding: "utf-8", mode: 384 });
-    fs2.renameSync(tmp, filePath);
-  } catch {
-    try {
-      fs2.unlinkSync(tmp);
-    } catch {
-    }
-  }
-}
-
 // src/commands/message/_format.ts
 function toLocalTime(iso) {
   const d = new Date(iso);
@@ -580,10 +527,6 @@ function registerSendCommand(parent) {
       fail(code, res.error ?? `HTTP ${res.status}`);
     }
     const data = res.data;
-    writeChatContext(ctx.agentId, {
-      target: opts.target,
-      msgId: typeof data.messageId === "string" ? data.messageId : null
-    });
     const shortId = data.messageId ? data.messageId.slice(0, 8) : null;
     const replyHint = shortId ? ` (to reply in this message's thread, use target "${opts.target.includes(":") ? opts.target : opts.target + ":" + shortId}")` : "";
     let unreadSection = "";
@@ -606,8 +549,8 @@ async function drainInbox(ctx, opts) {
   const query = [];
   if (opts.block) query.push("block=true");
   if (opts.block && opts.timeoutMs !== void 0) query.push(`timeout=${opts.timeoutMs}`);
-  const path2 = query.length > 0 ? `${agentPath}/receive?${query.join("&")}` : `${agentPath}/receive`;
-  const res = await client.request("GET", path2);
+  const path = query.length > 0 ? `${agentPath}/receive?${query.join("&")}` : `${agentPath}/receive`;
+  const res = await client.request("GET", path);
   if (!res.ok) {
     const code = res.status >= 500 ? "SERVER_5XX" : failCode;
     fail(code, res.error ?? `HTTP ${res.status}`);
@@ -633,13 +576,6 @@ function registerCheckCommand(parent) {
       throw err;
     }
     const result = await drainInbox(ctx, { block: false });
-    if (result.messages.length > 0) {
-      const latest = result.messages[result.messages.length - 1];
-      const target = formatTarget(latest);
-      const rawMsgId = latest.message_id;
-      const msgId = typeof rawMsgId === "string" ? rawMsgId : null;
-      writeChatContext(ctx.agentId, { target, msgId });
-    }
     process.stdout.write(formatMessages(result.messages) + "\n");
   });
 }
@@ -1072,7 +1008,7 @@ function formatReminderCanceled(r) {
 }
 
 // src/commands/reminder/schedule.ts
-function buildScheduleBody(opts, cached, now = () => Intl.DateTimeFormat().resolvedOptions().timeZone) {
+function buildScheduleBody(opts, now = () => Intl.DateTimeFormat().resolvedOptions().timeZone) {
   if (!opts.delaySeconds && !opts.fireAt && !opts.repeat) {
     return {
       body: {},
@@ -1108,9 +1044,14 @@ function buildScheduleBody(opts, cached, now = () => Intl.DateTimeFormat().resol
     body.tz = now();
   }
   if (opts.channel !== void 0) body.channel = opts.channel;
-  if (opts.channel === void 0 && opts.msgId === void 0) {
-    if (cached.target) body.channel = cached.target;
-    if (cached.msgId) body.msgId = cached.msgId;
+  if (body.msgId == null) {
+    return {
+      body: {},
+      error: {
+        code: "INVALID_ARG",
+        message: "Reminder create requires an anchor msgId; resolve a message first and pass --msg-id"
+      }
+    };
   }
   return { body };
 }
@@ -1126,8 +1067,11 @@ function registerReminderScheduleCommand(parent) {
     "Recurrence rule: every:15m | every:2h | every:1d | daily@09:00 | weekly:mon,fri@09:00"
   ).option(
     "--channel <ref>",
-    "Optional channel to post a receipt message in (e.g. #general, dm:@alice). Without --channel or --msg-id, receipt inherits the agent's current chat context (last message received/sent)."
-  ).option("--msg-id <id>", "Optional message id this reminder is anchored to").action(async (opts) => {
+    "Optional channel to post a receipt message in (e.g. #general, dm:@alice)."
+  ).requiredOption(
+    "--msg-id <id>",
+    "Message id this reminder is anchored to. Required for agent-created reminders."
+  ).action(async (opts) => {
     let ctx;
     try {
       ctx = loadAgentContext();
@@ -1135,8 +1079,7 @@ function registerReminderScheduleCommand(parent) {
       if (err instanceof AgentBootstrapError) fail(err.code, err.message);
       throw err;
     }
-    const cached = readChatContext(ctx.agentId);
-    const built = buildScheduleBody(opts, cached);
+    const built = buildScheduleBody(opts);
     if (built.error) fail(built.error.code, built.error.message);
     const client = new ApiClient(ctx);
     const res = await client.request(

package/dist/core.js

@@ -9,7 +9,7 @@ import {
   resolveSlockCliPath,
   resolveWorkspaceDirectoryPath,
   scanWorkspaceDirectories
-} from "./chunk-D6DQHMCD.js";
+} from "./chunk-6YLMU56U.js";
 import {
   subscribeDaemonLogs
 } from "./chunk-E6OOH3IC.js";

package/dist/index.js

@@ -3,7 +3,7 @@ import {
   DAEMON_CLI_USAGE,
   DaemonCore,
   parseDaemonCliArgs
-} from "./chunk-D6DQHMCD.js";
+} from "./chunk-6YLMU56U.js";
 import "./chunk-E6OOH3IC.js";
 
 // src/index.ts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@slock-ai/daemon",
-  "version": "0.39.1-alpha.2",
+  "version": "0.40.1",
   "type": "module",
   "bin": {
     "slock-daemon": "dist/index.js"
@@ -22,30 +22,33 @@
   "publishConfig": {
     "access": "public"
   },
+  "scripts": {
+    "dev": "pnpm --filter @slock-ai/cli build && tsx watch src/index.ts",
+    "start": "tsx src/index.ts",
+    "build": "pnpm --filter @slock-ai/cli build && tsup && node -e \"require('fs').cpSync('../cli/dist','dist/cli',{recursive:true})\"",
+    "test": "node --import tsx --test --test-force-exit 'src/**/*.test.ts'",
+    "prepack": "pnpm run build",
+    "prepublishOnly": "pnpm run build",
+    "typecheck": "tsc --noEmit",
+    "release:patch": "npm version patch --no-git-tag-version && cd ../.. && pnpm install --lockfile-only && git add packages/daemon/package.json pnpm-lock.yaml && git commit -m \"chore: bump @slock-ai/daemon to v$(node -p \"require('./packages/daemon/package.json').version\")\" && git tag daemon-v$(node -p \"require('./packages/daemon/package.json').version\") && git push && git push --tags",
+    "release:minor": "npm version minor --no-git-tag-version && cd ../.. && pnpm install --lockfile-only && git add packages/daemon/package.json pnpm-lock.yaml && git commit -m \"chore: bump @slock-ai/daemon to v$(node -p \"require('./packages/daemon/package.json').version\")\" && git tag daemon-v$(node -p \"require('./packages/daemon/package.json').version\") && git push && git push --tags",
+    "release:major": "npm version major --no-git-tag-version && cd ../.. && pnpm install --lockfile-only && git add packages/daemon/package.json pnpm-lock.yaml && git commit -m \"chore: bump @slock-ai/daemon to v$(node -p \"require('./packages/daemon/package.json').version\")\" && git tag daemon-v$(node -p \"require('./packages/daemon/package.json').version\") && git push && git push --tags",
+    "release:alpha": "npm version prerelease --preid=alpha --no-git-tag-version && cd ../.. && pnpm install --lockfile-only && git add packages/daemon/package.json pnpm-lock.yaml && git commit -m \"chore: bump @slock-ai/daemon to v$(node -p \"require('./packages/daemon/package.json').version\")\" && git tag daemon-v$(node -p \"require('./packages/daemon/package.json').version\") && git push && git push --tags"
+  },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
+    "commander": "^12.1.0",
     "https-proxy-agent": "^7.0.6",
     "undici": "^7.24.7",
     "ws": "^8.20.0",
     "zod": "^4.3.6"
   },
   "devDependencies": {
+    "@slock-ai/cli": "workspace:*",
+    "@slock-ai/shared": "workspace:*",
     "@types/node": "^25.5.0",
     "@types/ws": "^8.18.1",
     "tsup": "^8.5.1",
-    "typescript": "^5.9.3",
-    "@slock-ai/cli": "0.0.1",
-    "@slock-ai/shared": "0.1.0"
-  },
-  "scripts": {
-    "dev": "pnpm --filter @slock-ai/cli build && tsx watch src/index.ts",
-    "start": "tsx src/index.ts",
-    "build": "pnpm --filter @slock-ai/cli build && tsup && node -e \"require('fs').cpSync('../cli/dist','dist/cli',{recursive:true})\"",
-    "test": "node --import tsx --test --test-force-exit 'src/**/*.test.ts'",
-    "typecheck": "tsc --noEmit",
-    "release:patch": "npm version patch --no-git-tag-version && cd ../.. && pnpm install --lockfile-only && git add packages/daemon/package.json pnpm-lock.yaml && git commit -m \"chore: bump @slock-ai/daemon to v$(node -p \"require('./packages/daemon/package.json').version\")\" && git tag daemon-v$(node -p \"require('./packages/daemon/package.json').version\") && git push && git push --tags",
-    "release:minor": "npm version minor --no-git-tag-version && cd ../.. && pnpm install --lockfile-only && git add packages/daemon/package.json pnpm-lock.yaml && git commit -m \"chore: bump @slock-ai/daemon to v$(node -p \"require('./packages/daemon/package.json').version\")\" && git tag daemon-v$(node -p \"require('./packages/daemon/package.json').version\") && git push && git push --tags",
-    "release:major": "npm version major --no-git-tag-version && cd ../.. && pnpm install --lockfile-only && git add packages/daemon/package.json pnpm-lock.yaml && git commit -m \"chore: bump @slock-ai/daemon to v$(node -p \"require('./packages/daemon/package.json').version\")\" && git tag daemon-v$(node -p \"require('./packages/daemon/package.json').version\") && git push && git push --tags",
-    "release:alpha": "npm version prerelease --preid=alpha --no-git-tag-version && cd ../.. && pnpm install --lockfile-only && git add packages/daemon/package.json pnpm-lock.yaml && git commit -m \"chore: bump @slock-ai/daemon to v$(node -p \"require('./packages/daemon/package.json').version\")\" && git tag daemon-v$(node -p \"require('./packages/daemon/package.json').version\") && git push && git push --tags"
+    "typescript": "^5.9.3"
   }
-}
+}