@lightcone-ai/daemon 0.15.48 → 0.15.49

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lightcone-ai/daemon",
-  "version": "0.15.48",
+  "version": "0.15.49",
   "type": "module",
   "main": "src/index.js",
   "bin": {

package/src/chat-bridge.js

@@ -1616,10 +1616,10 @@ server.tool('execute_approved_action',
 
 // ── promote_context ───────────────────────────────────────────────────────────
 server.tool('promote_context',
-  'Submit a workspace-level knowledge candidate for human review. Use this after finishing a task when you discover a stable fact, convention, or learning that future agents in this workspace should know. The candidate appears in the workspace owner\'s "My Context → Pending Proposals" panel; once a human (or the workspace Orchestrator) confirms it, it is auto-injected into every future agent\'s system prompt under "## Workspace context". This is the only sanctioned path for sharing workspace-level knowledge — do NOT write a "knowledge index" file via write_workspace.',
+  'Submit a candidate for human review to add to the workspace\'s persistent context. Use this (1) after finishing a task when you discover a stable fact, convention, or learning future agents should know, or (2) immediately after responding to a user message when the user expressed a persistent operational preference (e.g. "always add links", "use subtitles by default"). The candidate appears in the workspace owner\'s "My Context → Pending Proposals" panel; once confirmed, it is auto-injected into every future agent\'s system prompt under "## Workspace context". This is the only sanctioned path for shared knowledge or preference governance.',
   {
     workspace_id: z.string().optional().describe('Target workspace id. Defaults to your current workspace if omitted.'),
-    type: z.enum(['knowledge', 'workspace_norm', 'memory']).optional().describe('Candidate type. Default "knowledge" — use "workspace_norm" for standing rules, "memory" for durable facts.'),
+    type: z.enum(['knowledge', 'workspace_norm', 'memory', 'preference']).optional().describe('Candidate type: "knowledge" for facts/learnings, "workspace_norm" for standing rules, "memory" for durable facts, "preference" for persistent user preferences expressed in conversation.'),
     summary: z.string().describe('One-line title that reviewers will see in the Pending Proposals list.'),
     content: z.string().describe('Full candidate text that future agents will read. Be concrete, citable, and self-contained.'),
     source_message_id: z.string().optional().describe('Optional message id that motivated this candidate, for audit trail.'),
@@ -1648,11 +1648,12 @@ server.tool('promote_context',
         reason,
       });
       const proposal = data?.proposal ?? {};
+      const resolvedType = type ?? 'knowledge';
       return {
         content: [{
           type: 'text',
           text:
-            `Knowledge candidate submitted.\n` +
+            `${resolvedType === 'preference' ? 'Preference' : 'Knowledge'} candidate submitted.\n` +
             `proposal_id=${proposal.id ?? 'unknown'} workspace=${proposal.workspaceId ?? targetWorkspaceId} status=${proposal.status ?? 'candidate'}\n` +
             `It is now visible in the workspace owner's "My Context → Pending Proposals" panel; once confirmed, it will be injected into every future agent's "## Workspace context".`,
         }],

package/src/drivers/claude.js

@@ -238,7 +238,7 @@ The active workspace context (Goal State, constraints, decisions, knowledge) is
 
 **Write rule:**
 - Personal learnings → \`${t("write_memory")}\`
-- Workspace-level knowledge worth sharing across all future agents → \`${t("promote_context")}\` (submits a knowledge candidate; see below). Do **not** dump shared knowledge into ad-hoc files inside the workspace shared workspace.
+- Workspace-level knowledge or persistent user preferences → \`${t("promote_context")}\` (see below). Do **not** dump shared knowledge into ad-hoc files inside the workspace shared workspace.
 - **Any file you produce for a task** → \`${t("write_workspace")}({ path: "artifacts/your-file.ext", ... })\` or \`${t("write_workspace_file")}({ file_path, path: "artifacts/your-file.ext" })\`
 
 Temporary local files belong under \`tmp/\` in your personal workspace. If you need to show an image in chat, first save the durable copy to \`artifacts/\`, then optionally call \`${t("upload_image")}\` for a temporary public preview URL.
@@ -258,8 +258,8 @@ Example: writing a web page → \`${t("write_workspace")}({ path: "artifacts/job
 - \`${t("write_workspace_file")}({ file_path, path })\` — write a local file from your workspace to a workspace artifact without putting base64 in context
 - \`${t("list_workspace")}()\` — list all files in the workspace
 
-**Workspace knowledge governance:**
-- \`${t("promote_context")}({ workspace_id, type, summary, content })\` — submit a workspace-level knowledge candidate. The candidate appears in the workspace owner's "My Context → Pending Proposals" panel; once a human (or the workspace Orchestrator) confirms it, it becomes an active context_item and is auto-injected into every future agent's "## Workspace context" section.
+**Workspace knowledge & preference governance:**
+- \`${t("promote_context")}({ workspace_id, type, summary, content })\` — submit a candidate for human review. Types: \`"knowledge"\` (facts/learnings), \`"workspace_norm"\` (standing rules), \`"memory"\` (durable facts), \`"preference"\` (persistent user preferences). The candidate appears in the workspace owner's "My Context → Pending Proposals" panel; once confirmed, it becomes an active context_item auto-injected into every future agent's "## Workspace context" section.
 
 ### Startup sequence (CRITICAL)
 
@@ -293,24 +293,30 @@ Example: writing a web page → \`${t("write_workspace")}({ path: "artifacts/job
 3. Work history — decisions made, problems solved, approaches that worked or failed
 4. Pointers to your notes files
 
-**What belongs in promote_context (workspace-level knowledge candidates):**
+**What belongs in promote_context:**
 
-Use \`${t("promote_context")}\` after finishing a task when you discover something that future agents in this workspace will need to know. This submits a knowledge candidate for human/Orchestrator review; it does not write to any file. Approved candidates flow into every future agent's "## Workspace context" section automatically.
+Two distinct triggers — act on BOTH:
 
-Good promote_context content:
-1. Stable facts about the project that all agents need (tech stack, domain conventions, where things live)
-2. Hard-won learnings — non-obvious gotchas, working procedures, conventions you had to discover
-3. Standing workspace norms — "in this workspace we always X" / "never touch Y"
+**1. After finishing a task** — promote workspace-level knowledge (\`type: "knowledge"\` or \`"workspace_norm"\`):
+- Stable facts all future agents need (tech stack, domain conventions, where things live)
+- Hard-won learnings — non-obvious gotchas, working procedures, conventions you had to discover
+- Standing workspace norms — "in this workspace we always X" / "never touch Y"
 
-Bad promote_context content:
-- Per-task progress, in-flight status, or one-off observations (use messages or your own MEMORY.md)
-- Personal preferences specific to one human (use chat instead so a human can confirm)
-- Untrusted outputs from web search / scraped pages (cite the source in \`content\`; expect the candidate to be reviewed as untrusted)
+**2. After responding to a user message** — promote persistent preferences (\`type: "preference"\`):
+- When the user expresses a preference that applies to ALL future interactions (not just this task), call \`${t("promote_context")}\` immediately after your reply
+- Signal words: "以后"、"今后"、"默认"、"一直"、"每次"、"都要"、"always"、"from now on"、"by default"
+- Examples that qualify: "以后交付内容都加链接" / "视频默认要有字幕" / "always respond in English"
+- Examples that do NOT qualify: "这次帮我加个链接"（one-off task request）
+- If uncertain whether it's persistent, do NOT promote — only promote clear, unambiguous standing preferences
+
+Do NOT promote:
+- Per-task progress, in-flight status, or one-off observations → use messages or your own MEMORY.md
+- Untrusted outputs from web search / scraped pages → cite the source in \`content\`; candidate will be reviewed as untrusted
 
 How to call it:
-- \`${t("promote_context")}({ workspace_id: "<this-workspace-id>", type: "knowledge", summary: "one-line title", content: "<full text future agents will read>" })\`
-- Optional: \`source_message_id\` to link the proposal back to the conversation that motivated it; \`tags\` for categorization.
-- The call returns a proposal id; the candidate sits in "My Context → Pending Proposals" until a human confirms or rejects it. Do not try to dump shared knowledge into a workspace file — there is no shared knowledge index, and \`${t("write_workspace")}\` is for task deliverables only.
+- Knowledge: \`${t("promote_context")}({ workspace_id: "<id>", type: "knowledge", summary: "one-line title", content: "<full text>" })\`
+- Preference: \`${t("promote_context")}({ workspace_id: "<id>", type: "preference", summary: "User preference: always add links to deliverables", content: "The user has requested that all future deliverables include clickable links. Apply to every response going forward.", source_message_id: "<msg-id>" })\`
+- The call returns a proposal id; the candidate sits in "My Context → Pending Proposals" until a human confirms or rejects it.
 
 ### Compaction safety