@zilliz/memsearch-opencode 0.3.11 → 0.3.12

package/index.ts

@@ -150,6 +150,23 @@ function shellEscape(s: string): string {
   return s.replace(/'/g, "'\\''");
 }
 
+export function getSkillCandidateHint(memsearchDir: string, memsearchCmd: string): string {
+  try {
+    const result = spawnSync(
+      "bash",
+      [
+        "-c",
+        `MEMSEARCH_DIR='${shellEscape(memsearchDir)}' ${memsearchCmd} skills status --hint`,
+      ],
+      { encoding: "utf-8", timeout: 5000 }
+    );
+    if (result.status !== 0) return "";
+    return (result.stdout || "").trim().split("\n")[0] || "";
+  } catch {
+    return "";
+  }
+}
+
 /** Marks the start of memsearch's injected block within a system message. */
 export const MEMSEARCH_SYSTEM_MARKER = "[memsearch] Memory available.";
 
@@ -277,6 +294,7 @@ const MemsearchPlugin: Plugin = async ({ project, directory, worktree }) => {
   const collectionName = deriveCollectionName(projectDir);
   const memsearchDir = join(projectDir, ".memsearch");
   const memoryDir = join(memsearchDir, "memory");
+  const skillCandidateHint = getSkillCandidateHint(memsearchDir, memsearchCmd);
   const home = process.env.HOME || "~";
 
   // Skip capture/recall in child processes to prevent recursion
@@ -433,10 +451,12 @@ const MemsearchPlugin: Plugin = async ({ project, directory, worktree }) => {
           "experimental.chat.system.transform": async (_input: any, output: any) => {
             try {
               const context = getRecentMemories(memoryDir);
-              if (context) {
+              if (context || skillCandidateHint) {
                 const memoryText =
                   `${MEMSEARCH_SYSTEM_MARKER} You have access to memory_search, ` +
-                  `memory_get, and memory_transcript tools for recalling past sessions.\n\n${context}`;
+                  `memory_get, and memory_transcript tools for recalling past sessions.` +
+                  `${skillCandidateHint ? `\n${skillCandidateHint}` : ""}` +
+                  `${context ? `\n\n${context}` : ""}`;
                 output.system = mergeSystemMemoryContext(output.system, memoryText);
               }
             } catch { /* ignore */ }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zilliz/memsearch-opencode",
-  "version": "0.3.11",
+  "version": "0.3.12",
   "description": "memsearch plugin for OpenCode — semantic memory search across sessions",
   "type": "module",
   "main": "index.ts",

package/skills/memory-config/SKILL.md

@@ -93,6 +93,8 @@ Check index health:
 
 ```bash
 memsearch stats
+STATE_DIR="${MEMSEARCH_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)/.memsearch}"
+test -f "$STATE_DIR/.index-state.json" && cat "$STATE_DIR/.index-state.json"
 ```
 
 OpenCode transcript recall reads from OpenCode's SQLite database, while captured MemSearch memory lives as markdown under `.memsearch/memory/`.
@@ -208,6 +210,11 @@ Model guidance:
 
 Advanced maintenance runs after the plugin wakes it, only when enabled, journal input changed, and `min_interval_hours` elapsed. `PROJECT.md` and `USER.md` are maintenance artifacts by default and are not automatically indexed.
 
+If indexing seems silent or search looks stale, check `.memsearch/.index-state.json`
+for `status`, `last_error`, and `failed_files`. `status: degraded` means the
+scan completed but one or more files failed; `status: error` means the index run
+did not complete.
+
 If advanced maintenance or `memory_to_skill` seems silent, check
 `.memsearch/.maintenance-state.json` for `<plugin>.<task>.last_error` and
 `last_failed_at`; background hook errors may not surface in the chat.

package/skills/memory-to-skill/SKILL.md

@@ -47,10 +47,16 @@ captured automatically going forward) — do not force it.
 ## B. Review & install candidates (1→2)
 
 ```bash
+memsearch skills status          # pending candidate versions needing install
 memsearch skills list            # add -j for sources / installed paths
 git -C .memsearch/skill-candidates log --oneline -5 2>/dev/null || true
 ```
 
+`skills status` compares each candidate's current `SKILL.md` content hash with
+the hash recorded by the last `skills install`. It does not inspect live agent
+skill directories. A pending installed skill means the candidate source evolved
+after the last deliberate install; reinstall only after reviewing the candidate.
+
 Before recommending or installing, skim the candidate's body: if a step looks uncertain or loosely summarized, re-check it against the source (open the transcript if needed) or flag it to the user and let them decide — installing copies the candidate as-is, so this is the last chance to catch a wrong step.
 When showing candidates, mention the store's recent git history when it helps
 explain whether a candidate is new, evolved, removed, or re-created.