@echomem/mcp 1.4.25 → 1.4.26

package/dist/index.js

@@ -18,9 +18,13 @@ import { checkLatestUpdateStatus, formatUpdateNotice, formatUpdateStatusText, st
 const ECHO_API_BASE_URL = process.env.ECHO_API_BASE_URL || "https://echo-mem-chrome.vercel.app";
 const ECHO_PRICING_URL = process.env.ECHO_PRICING_URL || "https://echoknows.com/account";
 const ECHO_MEMORY_WEB_URL = (process.env.ECHO_MEMORY_WEB_URL || "https://echoknows.com/company/memories").replace(/\/$/, "");
+const ECHO_PERSONAL_MEMORY_WEB_URL = (process.env.ECHO_PERSONAL_MEMORY_WEB_URL || "https://echoknows.com/memories/timeline").replace(/\/$/, "");
 function memoryWebUrl(memoryId) {
     return `${ECHO_MEMORY_WEB_URL}?memoryId=${encodeURIComponent(memoryId)}`;
 }
+function personalMemoryWebUrl(memoryId) {
+    return `${ECHO_PERSONAL_MEMORY_WEB_URL}?memoryId=${encodeURIComponent(memoryId)}`;
+}
 /** Thrown when no API token is present yet — the model gets a "run login" nudge, not a hard error. */
 class NoTokenError extends Error {
 }
@@ -1404,8 +1408,11 @@ class EchoMemMCPServer {
                     : m.details == null
                         ? ""
                         : String(m.details).trim();
+                const memoryId = readString(m, "id");
                 return [
                     `[${idx + 1}] ${key}${typeof score === "number" ? ` (score ${score.toFixed(3)})` : ""}`,
+                    memoryId ? `Memory ID: ${memoryId}` : "",
+                    memoryId ? `Open private memory: ${personalMemoryWebUrl(memoryId)}` : "",
                     meta,
                     `Description: ${description}`,
                     details ? `Details: ${details}` : "",
@@ -1423,6 +1430,7 @@ class EchoMemMCPServer {
         }
         const formattedResults = memories
             .map((m, idx) => `[Result ${idx + 1}] Memory ID: ${m.id || "unknown"} (Similarity: ${m.similarity_score?.toFixed(3) || "N/A"})
+Open private memory: ${personalMemoryWebUrl(String(m.id || "unknown"))}
 Time: ${m.time} | Location: ${m.location}
 Category: ${m.category} | Object: ${m.object} | Emotion: ${m.emotion}
 Description: ${m.description}
@@ -1500,7 +1508,9 @@ Details: ${m.details || "N/A"}`)
             };
         }
         const formattedResults = memories
-            .map((m, idx) => `[${idx + 1}] Time: ${m.time} | Location: ${m.location}
+            .map((m, idx) => `[${idx + 1}] Memory ID: ${m.id || "unknown"}
+Open private memory: ${personalMemoryWebUrl(String(m.id || "unknown"))}
+Time: ${m.time} | Location: ${m.location}
 Category: ${m.category} | Object: ${m.object} | Emotion: ${m.emotion}
 Description: ${m.description}
 Details: ${m.details || "N/A"}`)
@@ -1526,6 +1536,7 @@ Details: ${m.details || "N/A"}`)
         }
         const formattedResults = memories
             .map((m, idx) => `[${idx + 1}] ${m.keys || "Saved memory"}${m.id ? ` · id ${m.id}` : ""}
+${m.id ? `Open private memory: ${personalMemoryWebUrl(String(m.id))}` : ""}
 Time: ${m.time} | Category: ${m.category} | Object: ${m.object} | Emotion: ${m.emotion}
 Description: ${m.description}
 Details: ${m.details || "N/A"}`)
@@ -1604,7 +1615,9 @@ Details: ${m.details || "N/A"}`)
             };
         }
         const formattedResults = memories
-            .map((m, idx) => `[${idx + 1}] Time: ${m.time} | Keys: ${m.keys || "N/A"}
+            .map((m, idx) => `[${idx + 1}] Memory ID: ${m.id || "unknown"}
+Open private memory: ${personalMemoryWebUrl(String(m.id || "unknown"))}
+Time: ${m.time} | Keys: ${m.keys || "N/A"}
 Location: ${m.location} | Category: ${m.category} | Object: ${m.object}
 Description: ${m.description}
 Details: ${m.details || "N/A"}`)
@@ -1911,7 +1924,7 @@ Details: ${m.details || "N/A"}`;
                 : null;
             return [
                 `[${index + 1}] Memory ID: ${readString(candidate, "memoryId") ?? "unknown"}`,
-                `Open memory: ${memoryWebUrl(readString(candidate, "memoryId") ?? "unknown")}`,
+                `Open private memory: ${personalMemoryWebUrl(readString(candidate, "memoryId") ?? "unknown")}`,
                 `Created: ${readString(candidate, "createdAt") ?? "unknown"}`,
                 `Category: ${readString(candidate, "category") ?? "unknown"}`,
                 `Description: ${readString(candidate, "description") ?? ""}`,
@@ -1938,9 +1951,9 @@ Details: ${m.details || "N/A"}`;
                         formatted,
                         "",
                         flaggedIds.length
-                            ? `Extra attention required: ${flaggedIds.length} candidate(s) are flagged (${flaggedIds.join(", ")}). Show them in a separate warning and require a separate explicit acknowledgement before including their exact IDs in acknowledgedFlaggedMemoryIds.`
+                            ? `Extra attention required: ${flaggedIds.length} candidate(s) are flagged (${flaggedIds.join(", ")}). Nothing has been published. Show them in a separate warning and offer to exclude them, review them separately, or first search for and mark similar sensitive owned memories for publication attention. Never auto-flag based on inference. Require separate explicit acknowledgement before including their exact IDs in acknowledgedFlaggedMemoryIds.`
                             : "",
-                        "Select exact memory IDs matching the user's instruction. From memory evidence, draft a concise title and responsibility summary. Show the profile proposal and memory preview together, then ask for explicit confirmation. After confirmation, call update_group_profile and complete_group_publication.",
+                        "Select exact memory IDs matching the user's instruction. From memory evidence, draft a concise title and responsibility summary. If an unflagged candidate appears sensitive, proactively ask whether the user wants to mark its exact ID for publication attention first. Explain that marking does not publish or change encryption; it means you will call it out and ask for detailed confirmation whenever a later publication includes it. Never auto-flag. Show the profile proposal and memory preview together, then ask for explicit confirmation. After confirmation, call update_group_profile and complete_group_publication.",
                     ].join("\n"),
                 }],
         };
@@ -1958,6 +1971,7 @@ Details: ${m.details || "N/A"}`;
                         `Flagged ${payload?.flaggedCount ?? parsed.memoryIds.length} memories for publication attention.`,
                         `Label: ${parsed.label}`,
                         `Memory IDs: ${parsed.memoryIds.join(", ")}`,
+                        `Private review links:\n${parsed.memoryIds.map((memoryId) => `- ${memoryId}: ${personalMemoryWebUrl(memoryId)}`).join("\n")}`,
                         "No memory was published, decrypted, or made globally public.",
                         alreadyPublished > 0
                             ? `Attention: ${alreadyPublished} flagged memories already have group snapshots. This flag does not retract those existing snapshots.`

package/dist/package-metadata.js

@@ -30,8 +30,9 @@ export const MCP_SERVER_INSTRUCTIONS = [
     "Do not auto-update on every MCP startup; this bridge is intentionally stable between explicit updates.",
     "For company-group sharing, use get_group_context for orientation; create_memory_group/create_group_invite/join_memory_group for membership; and prepare_group_publication as a no-publication preview.",
     "After joining or when profile fields are missing, use candidate memory evidence to propose a title and responsibility summary. Ask the user to confirm that proposal together with the publication preview, then call update_group_profile and complete_group_publication.",
+    "Use owner-only /memories/timeline?memoryId=... links for the user's private search, flag, and publication-preview evidence. Use /company/memories?memoryId=... only for already-published group evidence.",
     "Each group-search result is one memory: preserve its Memory ID and direct echoknows.com link when citing it.",
-    "For sensitive-topic flags, search and preview exact owned memories before confirmed flag_memories_for_publication_attention. During publication, separate flagged candidates and require exact-ID acknowledgement.",
+    "During a publication preview, if an unflagged candidate appears sensitive, proactively ask whether the user wants to mark its exact ID for publication attention first. Explain that marking does not publish or change encryption; it means the agent will call it out and ask for detailed confirmation whenever a later publication includes it. Never auto-flag inferred sensitivity. For sensitive-topic flags, search and preview exact owned memories before confirmed flag_memories_for_publication_attention. Separate already-flagged candidates, state that nothing has been published yet, and offer to exclude them, review them separately, or first search for and mark similar sensitive owned memories.",
     "Never save an inferred group profile or complete a group publication without explicit confirmation, and never store or log an echo_grp_ invite code.",
 ].join(" ");
 export function withMcpVersion(description) {

package/dist/setup.js

@@ -399,9 +399,9 @@ function echomemGuidanceBlock() {
         "- If a user supplies an `echo_grp_...` code and explicitly asks to join, call `join_memory_group`. Joining never authorizes publishing by itself and must not move a user out of another group. After joining, continue into the profile-and-publication preview instead of leaving title or responsibility blank.",
         "- For requests such as “prepare my recent work memories,” “upload work from this ticket,” or “publish work since my last sync,” call `prepare_group_publication` first. This is a no-publication preview. For encrypted accounts, tell the user to run `echomem-mcp unlock` locally if the tool reports that the key is required.",
         "- After preparing, select only exact candidate memory IDs that match the user's stated scope and exclude already-published or exact-content duplicates. Use the candidate evidence to draft a concise title and responsibility summary for the current member, but label both as proposals rather than facts.",
-        "- Each returned group-search result is one memory. When citing it in a bullet, preserve its Memory ID and include its `https://echoknows.com/company/memories?memoryId=...` link so the user can open the evidence directly.",
-        "- If the user asks to flag memories about a sensitive topic, search their own memories first, show the exact matches, and ask them to confirm. Only then call `flag_memories_for_publication_attention`; flagging does not publish, decrypt, change visibility, or retract an existing group snapshot.",
-        "- Present the proposed title/responsibility and the memory publication preview together and ask for explicit confirmation. Never save an inferred profile or publish memories before confirmation. Show flagged candidates in a separate warning.",
+        "- Use two distinct evidence links. For the user's own source memories during search, flag review, or publication preview, preserve the Memory ID and use `https://echoknows.com/memories/timeline?memoryId=...`; this is an owner-only personal link and may require Vault unlock. For already-published results from `search_others_memories`, use `https://echoknows.com/company/memories?memoryId=...`, which requires current group access.",
+        "- If the user asks to flag memories about a sensitive topic, search their own memories first, show the exact matches with owner-only personal links, and ask them to confirm. Only then call `flag_memories_for_publication_attention`; flagging does not publish, decrypt, change visibility, or retract an existing group snapshot.",
+        "- Present the proposed title/responsibility and the memory publication preview together and ask for explicit confirmation. Never save an inferred profile or publish memories before confirmation. If an unflagged candidate appears sensitive, proactively ask whether the user wants to mark its exact ID for publication attention first. Explain naturally: marking does not publish or change encryption; it means you will call it out and ask for detailed confirmation whenever a later publication includes it. Never auto-flag based on agent inference. Show already-flagged candidates in a separate warning, state that nothing has been published yet, and offer three choices: exclude them, review them separately, or first search for and mark similar sensitive owned memories for publication attention.",
         "- On confirmation, call `update_group_profile` with the confirmed title, responsibility summary, and `confirmed: true`, then call `complete_group_publication` with the exact `scanId`, selected memory IDs, and `confirmed: true`. If a flagged memory is selected, require separate explicit acknowledgement and pass its exact ID in `acknowledgedFlaggedMemoryIds`. If the user edits either proposal, use their wording. An explicit request to join and upload still requires this preview and confirmation.",
         "- If the user asks to show, reopen, restart, or bring back the EchoMem HUD (the context-health overlay), run the shell command `echomem-hud app --client auto`.",
         "- If the user wants the HUD to come back after a computer restart, run the shell command `echomem-hud autostart on --client auto`.",

package/dist/v1-contract.js

@@ -492,7 +492,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.prepareGroupPublication,
-            description: "Prepare a no-publication preview of up to 50 owned memories for group publication. For encrypted accounts the local bridge must be unlocked. The host agent selects exact work-related memory ids, drafts a concise title and responsibility summary from memory evidence, and asks the user to confirm both the profile and publication selection together. Flagged memories are identified separately and require extra attention before publication. This tool never publishes.",
+            description: "Prepare a no-publication preview of up to 50 owned memories for group publication. For encrypted accounts the local bridge must be unlocked. The host agent selects exact work-related memory ids, gives each candidate an owner-only https://echoknows.com/memories/timeline?memoryId=... review link, drafts a concise title and responsibility summary from memory evidence, and asks the user to confirm both the profile and publication selection together. If an unflagged candidate appears sensitive, proactively ask whether the user wants to mark its exact ID for publication attention first. Explain that marking does not publish or change encryption; it means the agent will call it out and ask for detailed confirmation whenever a later publication includes it. Never auto-flag inferred sensitivity. Already-flagged memories are identified separately and require extra attention before publication. This tool never publishes.",
             inputSchema: {
                 type: "object",
                 properties: {
@@ -508,7 +508,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.flagPublicationAttention,
-            description: "Mark exact owned memories for extra attention during future group publication. First search the user's own memories, show the matching memory IDs and summaries, and obtain explicit confirmation. This only records a safety flag; it does not publish, decrypt, change visibility, or retract an existing group snapshot.",
+            description: "Mark exact owned memories for extra attention during future group publication. First search the user's own memories, show the matching memory IDs, summaries, and owner-only https://echoknows.com/memories/timeline?memoryId=... review links, and obtain explicit confirmation. This only records a safety flag; it does not publish, decrypt, change visibility, or retract an existing group snapshot.",
             inputSchema: {
                 type: "object",
                 properties: {
@@ -548,7 +548,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.completeGroupPublication,
-            description: "Publish only the exact memory ids from a prepared scan after the user explicitly confirms the preview. confirmed must be true. Any flagged memories must be called out separately and their exact IDs supplied in acknowledgedFlaggedMemoryIds after extra user acknowledgement. Completing an empty selection safely advances the scan cursor without publishing.",
+            description: "Publish only the exact memory ids from a prepared scan after the user explicitly confirms the preview. confirmed must be true. Any flagged memories must be called out separately; state that nothing has been published yet and offer to exclude them, review them separately, or first search for and mark similar sensitive owned memories. Never auto-flag inferred sensitivity. Publish flagged memories only after extra user acknowledgement with their exact IDs in acknowledgedFlaggedMemoryIds. Completing an empty selection safely advances the scan cursor without publishing.",
             inputSchema: {
                 type: "object",
                 properties: {
@@ -568,7 +568,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.publishToGroup,
-            description: "Publish one exact memory snapshot to your current company group without changing the memory's global is_public or encryption state. Call only after the user explicitly asks to publish or push that memory. If it is flagged, call it out and pass its ID in acknowledgedFlaggedMemoryIds only after extra user acknowledgement. The operation is idempotent.",
+            description: "Publish one exact memory snapshot to your current company group without changing the memory's global is_public or encryption state. Call only after the user explicitly asks to publish or push that memory. If it is flagged, state that nothing has been published yet and offer to exclude it, review it separately, or first search for and mark similar sensitive owned memories. Never auto-flag inferred sensitivity. Pass its ID in acknowledgedFlaggedMemoryIds only after extra user acknowledgement. The operation is idempotent.",
             inputSchema: {
                 type: "object",
                 properties: {
@@ -593,7 +593,7 @@ export function listToolSpecs(opts = {}) {
         },
         {
             name: canonicalToolNames.publishBatchToGroup,
-            description: "Publish up to 50 exact memory snapshots to your current company group without changing global is_public or the encrypted originals. For a session request, first call get_memories_by_context, select the exact ids that match the user's instruction, then pass those ids with the same contextId. Call only after explicit group-publication intent; report what was selected when the user delegates work-related filtering. Flagged memories must be called out separately and acknowledged by exact ID.",
+            description: "Publish up to 50 exact memory snapshots to your current company group without changing global is_public or the encrypted originals. For a session request, first call get_memories_by_context, select the exact ids that match the user's instruction, then pass those ids with the same contextId. Call only after explicit group-publication intent; report what was selected when the user delegates work-related filtering. Flagged memories must be called out separately; state that nothing has been published yet and offer exclusion, separate review, or a confirmed search-and-flag pass for similar sensitive owned memories. Never auto-flag inferred sensitivity. Publish flagged memories only after exact-ID acknowledgement.",
             inputSchema: {
                 type: "object",
                 properties: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@echomem/mcp",
-  "version": "1.4.25",
+  "version": "1.4.26",
   "description": "EchoMem MCP bridge: cloud-first memory tools, local context HUD, and the Agent Doctor workspace forensics report (cost ledger + 3D repo city)",
   "main": "dist/index.js",
   "type": "module",