@lightcone-ai/daemon 0.9.76 → 0.9.77

package/package.json

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

package/src/chat-bridge.js

@@ -113,46 +113,8 @@ server.tool('send_message', 'Send a message to a team, DM, or thread', {
   return { content: [{ type: 'text', text: `Sent. messageId=${data.messageId} threadTarget=${data.threadTarget}` }] };
 });
 
-// ── read_history ──────────────────────────────────────────────────────────────
-server.tool('read_history', 'Read message history from a team, DM, or thread. Supports pagination via before/after and context jumps via around.', {
-  team: z.string().describe('Target: #team-name | dm:@agentName | #team-name:shortMsgId'),
-  limit:   z.number().optional().describe('Max messages to return (default 50, max 100)'),
-  around:  z.union([z.string(), z.number()]).optional().describe('Center the result window around a messageId or seq number'),
-  before:  z.number().optional().describe('Return messages before this seq'),
-  after:   z.number().optional().describe('Return messages after this seq'),
-}, async ({ team, limit, around, before, after }) => {
-  const params = new URLSearchParams({ team, limit: String(Math.min(limit ?? 50, 100)) });
-  if (around != null) params.set('around', String(around));
-  if (before != null) params.set('before', String(before));
-  if (after  != null) params.set('after',  String(after));
-  const data = await api('GET', `/history?${params}`);
-  const msgs = data.messages ?? [];
-  if (msgs.length === 0) return { content: [{ type: 'text', text: 'No messages found.' }] };
-
-  const text = msgs.map(m => {
-    const senderType = m.senderType === 'agent' ? ' type=agent' : '';
-    const taskSuffix = m.taskStatus ? ` [task #${m.taskNumber} status=${m.taskStatus}${m.taskAssigneeId ? ` assignee=${m.taskAssigneeType}:${m.taskAssigneeId}` : ''}]` : '';
-    return `[seq=${m.seq} msg=${m.id} time=${m.createdAt}${senderType}] @${m.senderName}: ${m.content}${taskSuffix}`;
-  }).join('\n');
-
-  let footer = '';
-  if (data.has_more && msgs.length > 0) {
-    const minSeq = msgs[0].seq;
-    const maxSeq = msgs[msgs.length - 1].seq;
-    if (around) {
-      footer = `\n\n--- Use before=${minSeq} to load older or after=${maxSeq} to load newer. ---`;
-    } else if (after) {
-      footer = `\n\n--- ${msgs.length} messages shown. Use after=${maxSeq} for more. ---`;
-    } else {
-      footer = `\n\n--- ${msgs.length} messages shown. Use before=${minSeq} for older. ---`;
-    }
-  }
-
-  return { content: [{ type: 'text', text: `## History for ${team} (${msgs.length} messages)\n\n${text}${footer}` }] };
-});
-
 // ── search_messages ──────────────────────────────────────────────────────────
-server.tool('search_messages', 'Search messages within a specific team. You must specify the team. Use this to find relevant conversations, then inspect a hit with read_history(team=..., around=messageId).', {
+server.tool('search_messages', 'Search messages within a specific team. You must specify the team. Use this to find relevant conversations by keyword.', {
   query:   z.string().describe('Search query'),
   team: z.string().describe('Target team to search within, e.g. "#general", "dm:@richard". Required — you may only search teams you are a member of.'),
   limit:   z.number().optional().describe('Max results (default 10, max 20)'),
@@ -171,7 +133,6 @@ server.tool('search_messages', 'Search messages within a specific team. You must
       `team: #${r.teamName}`,
       `sender: @${r.senderName}${r.senderType === 'agent' ? ' (agent)' : ''}`,
       `content: ${r.snippet}`,
-      `next: read_history(team="#${r.teamName}", around="${r.id}", limit=20)`,
     ].join('\n')).join('\n\n');
     return { content: [{ type: 'text', text: `## Search Results for "${trimmed}" (${data.results.length} results)\n\n${formatted}` }] };
   } catch (err) {

package/src/drivers/claude.js

@@ -15,15 +15,14 @@ You have MCP tools from the "chat" server. Use ONLY these for communication:
 1. **${t("check_messages")}** — Non-blocking check for new messages. Use freely during work — at natural breakpoints or after notifications.
 2. **${t("send_message")}** — Send a message to a team or DM.
 3. **${t("list_server")}** — List all teams in this server, which ones you have joined, plus all agents and humans.
-4. **${t("read_history")}** — Read past messages from a team, DM, or thread. Supports \`before\` / \`after\` pagination and \`around\` for centered context.
-5. **${t("search_messages")}** — Search messages visible to you, then inspect a hit with \`${t("read_history")}\`.
-6. **${t("list_tasks")}** — View a team's task board.
-7. **${t("create_tasks")}** — Create new task-messages in a team (supports batch; equivalent to sending a new message and publishing it as a task-message, not claiming it for yourself).
-8. **${t("claim_tasks")}** — Claim tasks by number (supports batch, handles conflicts).
-9. **${t("unclaim_task")}** — Release your claim on a task.
-10. **${t("update_task_status")}** — Change a task's status (e.g. to in_review or done).
-11. **${t("upload_image")}** — Upload an image file for a temporary public preview URL in a chat message. This is not durable artifact storage.
-12. **${t("view_file")}** — Download an attached image by its attachment ID so you can view it. Use when messages contain image attachments.
+4. **${t("search_messages")}** — Search messages visible to you by keyword.
+5. **${t("list_tasks")}** — View a team's task board.
+6. **${t("create_tasks")}** — Create new task-messages in a team (supports batch; equivalent to sending a new message and publishing it as a task-message, not claiming it for yourself).
+7. **${t("claim_tasks")}** — Claim tasks by number (supports batch, handles conflicts).
+8. **${t("unclaim_task")}** — Release your claim on a task.
+9. **${t("update_task_status")}** — Change a task's status (e.g. to in_review or done).
+10. **${t("upload_image")}** — Upload an image file for a temporary public preview URL in a chat message. This is not durable artifact storage.
+11. **${t("view_file")}** — Download an attached image by its attachment ID so you can view it. Use when messages contain image attachments.
 
 CRITICAL RULES:
 - Always communicate through ${t("send_message")}. This is your only output method.
@@ -73,7 +72,6 @@ Threads are sub-conversations attached to a specific message. They let you discu
 - When you receive a message from a thread (the target has a \`:shortid\` suffix), **always reply using that same target** to keep the conversation in the thread.
 - **Start a new thread**: Use the \`msg=\` field from the header as the thread suffix. For example, if you see \`[target=#general msg=a1b2c3d4 ...]\`, reply with \`send_message(target="#general:a1b2c3d4", content="...")\`. The thread will be auto-created if it doesn't exist yet.
 - When you send a message, the response includes the message ID. You can use it to start a thread on your own message.
-- You can read thread history: \`read_history(team="#general:a1b2c3d4")\`
 - Threads cannot be nested — you cannot start a thread inside a thread.
 
 ### Discovering people and teams
@@ -87,12 +85,6 @@ Each team has a **name** and optionally a **description** that define its purpos
 - **Stay on topic** — when proactively sharing results or updates, post in the team most relevant to the work. Don't scatter messages across unrelated teams.
 - If unsure where something belongs, call \`list_server\` to review team descriptions.
 
-### Reading history
-
-\`read_history(team="#team-name")\` or \`read_history(team="dm:@peer-name")\` or \`read_history(team="#team:shortid")\`
-
-To jump directly to a specific hit with nearby context, use \`read_history(team="...", around="messageId")\` or \`read_history(team="...", around=12345)\`.
-
 ### Tasks
 
 When someone sends a message that asks you to do something — fix a bug, write code, review a PR, deploy, investigate an issue — that is work. Claim it before you start.
@@ -106,8 +98,6 @@ When someone sends a message that asks you to do something — fix a bug, write
 
 Only top-level team / DM messages can become tasks. Messages inside threads are discussion context — reply there, but keep claims and conversions to top-level messages.
 
-\`read_history\` shows messages in their current state. If a message was later converted to a task, it will show the \`[task #N ...]\` suffix.
-
 **Status flow:** \`todo\` → \`in_progress\` → \`in_review\` → \`done\`
 
 **Assignee** is independent from status — a task can be claimed or unclaimed at any status except \`done\`.