@zilliz/memsearch-opencode 0.3.2 → 0.3.3

package/index.ts

@@ -93,7 +93,7 @@ function getRecentMemories(
     try {
       const content = readFileSync(join(memDir, file), "utf-8");
       const lines = content.split("\n")
-        .filter((l) => /^#{2,4}\s/.test(l) || l.startsWith("- ") || l.startsWith("[Human]") || l.startsWith("[Assistant]"))
+        .filter((l) => /^#{2,4}\s/.test(l) || l.startsWith("- ") || l.startsWith("[User]") || l.startsWith("[Assistant]"))
         .slice(0, maxLinesPerFile);
       if (lines.length > 0) {
         summary.push(`[${file}]`, ...lines);
@@ -301,7 +301,7 @@ const MemsearchPlugin: Plugin = async ({ project, directory, worktree }) => {
           "Retrieve the original conversation from a past OpenCode session. " +
           "Use after memory_get when the expanded result contains a session anchor " +
           "(<!-- session:ID turn:ID db:PATH -->). Returns the formatted " +
-          "dialogue with [Human] and [Assistant] labels. When turn_id is present, " +
+          "dialogue with [User] and [Assistant] labels. When turn_id is present, " +
           "the tool returns the target turn plus surrounding context.",
         args: {
           session_id: tool.schema.string().describe("The session ID from the anchor comment"),

package/package.json

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

package/prompts/summarize.txt

@@ -1,14 +1,15 @@
-You are a third-person note-taker. You will receive a transcript of ONE conversation turn between a human and {{AGENT_NAME}}.
+You are a third-person note-taker. You will receive a transcript of ONE conversation turn between User and {{AGENT_NAME}}.
 
-Your job is to record what happened as factual third-person notes. You are an EXTERNAL OBSERVER — you are NOT {{AGENT_NAME}}, NOT an assistant. Do NOT answer the human's question, do NOT give suggestions, do NOT offer help. ONLY record what occurred.
+Your job is to record what happened as factual third-person notes. You are an EXTERNAL OBSERVER — you are NOT {{AGENT_NAME}}, NOT an assistant. Do NOT answer User's question, do NOT give suggestions, do NOT offer help. ONLY record what occurred.
 
-Output 2-6 bullet points, each starting with '- '. NOTHING else.
+Output 2-10 bullet points, each starting with '- '. NOTHING else.
+Mandatory language rule: write every bullet in the same primary language as the [User] text. If User mixes languages, use the dominant user-facing language.
 
 Rules:
-- Write in third person: 'User asked...', '{{AGENT_NAME}} read file X', '{{AGENT_NAME}} ran command Y'
-- First bullet: what the user asked or wanted (one sentence)
-- Remaining bullets: what was done — tools called, files read/edited, commands run, key findings
-- Be specific: mention file names, function names, tool names, and concrete outcomes
-- Do NOT answer the human's question yourself — just note what was discussed
+- Write in third person and call the user 'User'
+- First bullet: what User asked or wanted (one sentence)
+- Remaining bullets: what was done, found, changed, configured, tested, explained, decided, or could not be completed
+- Be specific when useful: mention important files read or edited, searches or research performed, refactors, commands or tests run, key findings, and concrete outcomes
+- Prefer the final user-visible outcome over low-level transcript mechanics
+- Do NOT answer User's question yourself — just note what was discussed
 - Do NOT add any text before or after the bullet points
-- Write in the same language as the human's message in the transcript

package/scripts/capture-daemon.py

@@ -164,7 +164,10 @@ def _load_summarize_prompt(agent_name: str, memsearch_cmd: str | None = None) ->
     # Inline fallback
     return (
         "You are a third-person note-taker. Summarize the transcript as "
-        "2-6 bullet points. Write in third person. Output ONLY bullet points."
+        "2-10 bullet points. Write in third person. Do NOT answer User's question. "
+        "Mandatory language rule: write every bullet in the same primary language as the [User] text. "
+        "If User mixes languages, use the dominant user-facing language. "
+        "Output ONLY bullet points."
     )
 
 

package/scripts/opencode_turns.py

@@ -17,6 +17,13 @@ from dataclasses import dataclass, field
 from pathlib import Path
 
 
+def _tail_truncate(text: str, max_chars: int) -> str:
+    """Keep the end of long text, where final conclusions usually appear."""
+    if len(text) <= max_chars:
+        return text
+    return "...(truncated to tail)\n" + text[-max_chars:]
+
+
 @dataclass
 class OpenCodeMessage:
     """A single meaningful OpenCode message with rendered text."""
@@ -51,10 +58,9 @@ class OpenCodeTurn:
             f"=== Turn {self.turn_index} ({self.turn_id}) ===",
         ]
         for message in self.messages:
-            label = "[Human]" if message.role == "user" else "[Assistant]"
+            label = "[User]" if message.role == "user" else "[Assistant]"
             text = message.text.strip()
-            if len(text) > max_chars:
-                text = text[:max_chars] + "\n..."
+            text = _tail_truncate(text, max_chars)
             lines.append(f"{label}: {text}")
             lines.append("")
         return "\n".join(lines).strip()
@@ -283,7 +289,6 @@ def extract_message_text(conn: sqlite3.Connection, message_id: str) -> str:
     ).fetchall()
 
     text_parts: list[str] = []
-    tool_parts: list[str] = []
 
     for part in parts:
         try:
@@ -298,36 +303,9 @@ def extract_message_text(conn: sqlite3.Connection, message_id: str) -> str:
             text = str(part_data["text"]).strip()
             if text:
                 text_parts.append(text)
-        elif part_type == "tool" and part_data.get("state"):
-            state = part_data.get("state", {})
-            status = state.get("status", "unknown")
-            tool_name = part_data.get("tool", "unknown")
-
-            if status == "completed":
-                tool_input = state.get("input", {})
-                tool_output = state.get("output", "")
-                if isinstance(tool_output, str) and len(tool_output) > 300:
-                    tool_output = tool_output[:300] + "..."
-
-                input_summary = ""
-                if isinstance(tool_input, dict):
-                    if "command" in tool_input:
-                        input_summary = f" `{tool_input['command']}`"
-                    elif "path" in tool_input:
-                        input_summary = f" {tool_input['path']}"
-                    elif "query" in tool_input:
-                        input_summary = f" '{tool_input['query']}'"
-
-                tool_parts.append(
-                    f"[Tool: {tool_name}{input_summary}] {tool_output}"
-                )
-            elif status == "error":
-                error = state.get("error", "unknown error")
-                tool_parts.append(f"[Tool: {tool_name}] Error: {error}")
+        # Skip tool parts; summaries use the readable User/Assistant text.
 
     combined = "\n".join(text_parts).strip()
-    if tool_parts:
-        combined = "\n".join([combined, "\n".join(tool_parts)]).strip()
     return combined
 
 

package/skills/memory-config/SKILL.md

@@ -5,9 +5,9 @@ description: "Diagnose and configure MemSearch memory behavior for the OpenCode
 
 You are a MemSearch configuration assistant for the OpenCode plugin. This skill manages MemSearch settings only. It is not OpenCode's built-in memory configuration.
 
-Start every user-facing answer with:
-
-> This is MemSearch memory config, not OpenCode's own memory config.
+In diagnostic summaries or final answers, state once that this is MemSearch
+memory configuration, not OpenCode's own memory/config system. Do not prepend
+that sentence to every progress update or every paragraph.
 
 When this skill is triggered, inspect the user's request text. If there is no concrete request, run a diagnostic. If they ask for a specific setting or change, route the request using the flows below.
 
@@ -31,8 +31,54 @@ memsearch config list --global
 memsearch config list --project
 ```
 
+Check CLI and plugin versions before calling the setup healthy:
+
+```bash
+memsearch --version
+uv tool list --show-paths | rg -n 'memsearch|Package|Installed|path'
+curl -fsSL https://pypi.org/pypi/memsearch/json \
+  | python3 -c 'import json,sys; print(json.load(sys.stdin)["info"]["version"])'
+```
+
 If `memsearch` is unavailable, try `uvx --from memsearch[onnx] memsearch --version`.
 
+MemSearch has one shared Python CLI and platform plugins that may be installed
+from different channels:
+
+- CLI latest version comes from PyPI package `memsearch`. Update with
+  `uv tool install -U "memsearch[onnx]"` or `uv tool upgrade memsearch`.
+- Codex plugin has no independent package/version file. Inspect
+  `${CODEX_HOME:-$HOME/.codex}/hooks.json` to find the hook source path, then
+  compare that repository with the latest `zilliztech/memsearch` GitHub release:
+  `git -C <memsearch-repo> describe --tags --always --dirty` and
+  `gh release view --repo zilliztech/memsearch --json tagName,publishedAt,url`.
+  Update source installs with `git pull` plus
+  `bash plugins/codex/scripts/install.sh`.
+- Claude Code plugin latest marketplace/source version is in
+  `plugins/claude-code/.claude-plugin/plugin.json` and
+  `.claude-plugin/marketplace.json` in the `zilliztech/memsearch` repo. Check
+  the latest source manifest with
+  `curl -fsSL https://raw.githubusercontent.com/zilliztech/memsearch/main/plugins/claude-code/.claude-plugin/plugin.json`.
+  For marketplace installs, use `claude plugin marketplace update memsearch-plugins`
+  then `claude plugin update memsearch`, and restart Claude Code.
+- OpenClaw plugin latest published version comes from
+  `clawhub package inspect memsearch`; the source version is
+  `plugins/openclaw/package.json`. Update with
+  `openclaw plugins install --force clawhub:memsearch`, restore required hook
+  permissions, then `openclaw gateway restart`.
+- OpenCode plugin latest published version comes from
+  `npm view @zilliz/memsearch-opencode version dist-tags --json`; the source
+  version is `plugins/opencode/package.json`. If `~/.config/opencode/opencode.json`
+  pins a version, update the pin; otherwise restart OpenCode after package
+  refresh.
+
+For more detail, fetch the update sections from the public documentation:
+
+- Codex: https://zilliztech.github.io/memsearch/platforms/codex/installation/
+- Claude Code: https://zilliztech.github.io/memsearch/platforms/claude-code/installation/
+- OpenClaw: https://zilliztech.github.io/memsearch/platforms/openclaw/installation/
+- OpenCode: https://zilliztech.github.io/memsearch/platforms/opencode/installation/
+
 Check memory files:
 
 ```bash
@@ -152,6 +198,6 @@ Empty prompt paths mean use the built-in MemSearch prompts. Custom prompt files
 
 Use `memsearch config set` for changes. After changing anything, show the command, the resolved value, and whether a new session is needed.
 
-MemSearch TOML changes are read lazily by the CLI, capture daemon, and maintenance runner, so values such as `plugins.opencode.summarize.*`, `plugins.opencode.project_review.*`, `plugins.opencode.user_profile.*`, `[llm.providers.*]`, `[prompts]`, `milvus.*`, and `embedding.*` usually apply on the next capture, recall, index, or maintenance invocation. Restart OpenCode after `opencode.json` or plugin package changes; if capture behavior still looks stale after TOML edits, restart OpenCode or the capture daemon. After any answer, make clear that this is MemSearch memory configuration, not OpenCode's own memory/config system.
+MemSearch TOML changes are read lazily by the CLI, capture daemon, and maintenance runner, so values such as `plugins.opencode.summarize.*`, `plugins.opencode.project_review.*`, `plugins.opencode.user_profile.*`, `[llm.providers.*]`, `[prompts]`, `milvus.*`, and `embedding.*` usually apply on the next capture, recall, index, or maintenance invocation. Restart OpenCode after `opencode.json` or plugin package changes; if capture behavior still looks stale after TOML edits, restart OpenCode or the capture daemon. In final diagnostic/change summaries, make clear that this is MemSearch memory configuration, not OpenCode's own memory/config system.
 
 When useful, remind the user that they can either continue using this `memory-config` skill for guided configuration, or manually run `memsearch config init` for global interactive setup, `memsearch config init --project` for project interactive setup, and `memsearch config set/get/list` for direct CLI changes.