opencode-memtomem 0.1.0 → 0.1.2

package/README.md

@@ -6,9 +6,10 @@ and three read-only skills. It does not add event hooks or automatic indexing.
 
 ## Current status
 
-`opencode-memtomem` is present in this source repository but is not currently
-published to npm. Do not use an `opencode plugin add` command; OpenCode loads
-npm plugins from the singular `plugin` array in `opencode.json`.
+The published npm release is `opencode-memtomem@0.1.1`; this source tree is
+version `0.1.2` (bundling core `0.3.12`), which is not on npm yet. Do not use
+an `opencode plugin add` command; OpenCode loads npm plugins from the singular
+`plugin` array in `opencode.json`.
 
 For a released memtomem installation, configure the local MCP server now:
 
@@ -18,7 +19,7 @@ For a released memtomem installation, configure the local MCP server now:
   "mcp": {
     "memtomem": {
       "type": "local",
-      "command": ["uvx", "--isolated", "--from", "memtomem[all]==0.3.10", "memtomem-server"],
+      "command": ["uvx", "--isolated", "--from", "memtomem[all]==0.3.12", "memtomem-server"],
       "enabled": true,
       "timeout": 60000,
       "environment": {"MEMTOMEM_TOOL_MODE": "core"}
@@ -27,15 +28,15 @@ For a released memtomem installation, configure the local MCP server now:
 }
 ```
 
-After the npm package is published, the plugin form will be:
+After `0.1.2` is published, the plugin form will be:
 
 ```json
-{"plugin": ["opencode-memtomem@0.1.0"]}
+{"plugin": ["opencode-memtomem@0.1.2"]}
 ```
 
 Restart OpenCode, then run `/memtomem-status` or `/memtomem-search topic`.
 `uvx` must be available on `PATH`. The manual configuration above starts the
-exact-pinned `memtomem[all]==0.3.10` runtime on demand.
+exact-pinned `memtomem[all]==0.3.12` runtime on demand.
 
 The plugin supports macOS, Linux, and Windows through WSL. Native Windows has
 not been verified.

package/dist/generated.d.ts

@@ -1,4 +1,4 @@
-export declare const CORE_VERSION = "0.3.10";
+export declare const CORE_VERSION = "0.3.12";
 export declare const TOOL_MODE = "core";
 export declare const MCP_TIMEOUT_MS = 60000;
 export declare const OPENCODE_COMMANDS: {
@@ -16,7 +16,7 @@ export declare const OPENCODE_COMMANDS: {
     };
     readonly "memtomem-remember": {
         readonly description: "Save an explicit user-requested memory with memtomem. Use only when the user clearly asks to remember, record, or persist information for later.";
-        readonly template: "Use the memtomem remember workflow.\n\nUser input: $ARGUMENTS\n\nConfirm that the user explicitly requested persistence, then call `memtomem_mem_add` with the requested content. Add a natural title and a small set of useful tags only when they are clear from the content.\n\nUse `scope=\"user\"` by default and leave `force_unsafe=false`. Use `project_shared` only after explicit confirmation and set `confirm_project_shared=true`. Report the written file and indexed chunk count. If the tool reports a similar memory, surface the warning rather than silently creating another variant.";
+        readonly template: "Use the memtomem remember workflow.\n\nUser input: $ARGUMENTS\n\nConfirm that the user explicitly requested persistence. Add a natural title and a small set of useful tags only when they are clear from the content.\n\nChoose the destination from the user's context:\n\n- For a project-specific fact or decision, call `memtomem_mem_status` first. If the current project has a registered `.memtomem/memories.local` source, call `memtomem_mem_add` with `scope=\"project_local\"`.\n- If the request is project-specific but that tier is not registered, do not silently fall back to user memory. Ask the user to run `cd <project-root> && mm mem init --scope project_local`, then retry.\n- Use `scope=\"user\"` only for cross-project preferences or when the user explicitly requests personal/global memory.\n- Use `project_shared` only after explicit confirmation and set `confirm_project_shared=true`.\n\nAlways leave `force_unsafe=false`. Report the effective scope, written file, and indexed chunk count. If the tool reports a similar memory, surface the warning rather than silently creating another variant.";
     };
     readonly "memtomem-index": {
         readonly description: "Index or re-index an explicitly selected file or directory with memtomem. Use for initial ingestion or intentional refresh after file changes.";
@@ -24,7 +24,7 @@ export declare const OPENCODE_COMMANDS: {
     };
     readonly "memtomem-setup": {
         readonly description: "Set up and verify a first memtomem memory source. Use for onboarding, choosing an index path, or confirming that search works.";
-        readonly template: "Use the memtomem setup workflow.\n\nUser input: $ARGUMENTS\n\n1. Call `memtomem_mem_status` and treat the default `provider=none` BM25-only configuration as healthy.\n2. Obtain an explicit notes or memory directory from the request; ask for one when absent.\n3. Call `memtomem_mem_index` on that path with `force=false` and `auto_tag=false`.\n4. Choose a representative phrase from the indexed material and call `memtomem_mem_search` to verify retrieval.\n5. Report the first-success path and mention embeddings only as an optional relevance enhancement.\n\nDo not install Ollama, enable automation hooks, or edit host instruction files unless the user separately requests those actions.";
+        readonly template: "Use the memtomem setup workflow.\n\nUser input: $ARGUMENTS\n\n1. Call `memtomem_mem_status` and treat the default `provider=none` BM25-only configuration as healthy.\n2. If status says memtomem is not configured, stop before indexing and give the exact terminal bootstrap command from the plugin README. Preserve project context by prefixing it with `cd <project-root> &&` when the setup is project-specific. Retry only after the user completes that explicit trust step.\n3. Obtain an explicit notes or memory directory from the request; ask for one when absent.\n4. Call `memtomem_mem_index` on that path with `force=false` and `auto_tag=false`. This is a one-shot index and must not silently register a watcher root.\n5. Choose a representative phrase from the indexed material and call `memtomem_mem_search` to verify retrieval.\n6. Report the effective DB path, indexed path, and first-success result. Mention embeddings only as an optional relevance enhancement.\n\nDo not install Ollama, enable automation hooks, or edit host instruction files unless the user separately requests those actions.";
     };
 };
 export declare const OPENCODE_READ_SKILLS: readonly ["memtomem-search", "memtomem-recall", "memtomem-status"];

package/dist/generated.js

@@ -1,5 +1,5 @@
 // Generated by tools/render_plugin_assets.py. Do not edit.
-export const CORE_VERSION = "0.3.10";
+export const CORE_VERSION = "0.3.12";
 export const TOOL_MODE = "core";
 export const MCP_TIMEOUT_MS = 60000;
 export const OPENCODE_COMMANDS = {
@@ -17,7 +17,7 @@ export const OPENCODE_COMMANDS = {
     },
     "memtomem-remember": {
         "description": "Save an explicit user-requested memory with memtomem. Use only when the user clearly asks to remember, record, or persist information for later.",
-        "template": "Use the memtomem remember workflow.\n\nUser input: $ARGUMENTS\n\nConfirm that the user explicitly requested persistence, then call `memtomem_mem_add` with the requested content. Add a natural title and a small set of useful tags only when they are clear from the content.\n\nUse `scope=\"user\"` by default and leave `force_unsafe=false`. Use `project_shared` only after explicit confirmation and set `confirm_project_shared=true`. Report the written file and indexed chunk count. If the tool reports a similar memory, surface the warning rather than silently creating another variant."
+        "template": "Use the memtomem remember workflow.\n\nUser input: $ARGUMENTS\n\nConfirm that the user explicitly requested persistence. Add a natural title and a small set of useful tags only when they are clear from the content.\n\nChoose the destination from the user's context:\n\n- For a project-specific fact or decision, call `memtomem_mem_status` first. If the current project has a registered `.memtomem/memories.local` source, call `memtomem_mem_add` with `scope=\"project_local\"`.\n- If the request is project-specific but that tier is not registered, do not silently fall back to user memory. Ask the user to run `cd <project-root> && mm mem init --scope project_local`, then retry.\n- Use `scope=\"user\"` only for cross-project preferences or when the user explicitly requests personal/global memory.\n- Use `project_shared` only after explicit confirmation and set `confirm_project_shared=true`.\n\nAlways leave `force_unsafe=false`. Report the effective scope, written file, and indexed chunk count. If the tool reports a similar memory, surface the warning rather than silently creating another variant."
     },
     "memtomem-index": {
         "description": "Index or re-index an explicitly selected file or directory with memtomem. Use for initial ingestion or intentional refresh after file changes.",
@@ -25,7 +25,7 @@ export const OPENCODE_COMMANDS = {
     },
     "memtomem-setup": {
         "description": "Set up and verify a first memtomem memory source. Use for onboarding, choosing an index path, or confirming that search works.",
-        "template": "Use the memtomem setup workflow.\n\nUser input: $ARGUMENTS\n\n1. Call `memtomem_mem_status` and treat the default `provider=none` BM25-only configuration as healthy.\n2. Obtain an explicit notes or memory directory from the request; ask for one when absent.\n3. Call `memtomem_mem_index` on that path with `force=false` and `auto_tag=false`.\n4. Choose a representative phrase from the indexed material and call `memtomem_mem_search` to verify retrieval.\n5. Report the first-success path and mention embeddings only as an optional relevance enhancement.\n\nDo not install Ollama, enable automation hooks, or edit host instruction files unless the user separately requests those actions."
+        "template": "Use the memtomem setup workflow.\n\nUser input: $ARGUMENTS\n\n1. Call `memtomem_mem_status` and treat the default `provider=none` BM25-only configuration as healthy.\n2. If status says memtomem is not configured, stop before indexing and give the exact terminal bootstrap command from the plugin README. Preserve project context by prefixing it with `cd <project-root> &&` when the setup is project-specific. Retry only after the user completes that explicit trust step.\n3. Obtain an explicit notes or memory directory from the request; ask for one when absent.\n4. Call `memtomem_mem_index` on that path with `force=false` and `auto_tag=false`. This is a one-shot index and must not silently register a watcher root.\n5. Choose a representative phrase from the indexed material and call `memtomem_mem_search` to verify retrieval.\n6. Report the effective DB path, indexed path, and first-success result. Mention embeddings only as an optional relevance enhancement.\n\nDo not install Ollama, enable automation hooks, or edit host instruction files unless the user separately requests those actions."
     }
 };
 export const OPENCODE_READ_SKILLS = [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-memtomem",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Safe memtomem MCP, commands, and read skills for OpenCode",
   "type": "module",
   "sideEffects": false,
@@ -35,7 +35,7 @@
     "pack:check": "npm pack --dry-run"
   },
   "devDependencies": {
-    "@opencode-ai/plugin": "1.17.18",
+    "@opencode-ai/plugin": "1.18.3",
     "@types/node": "26.1.1",
     "typescript": "5.9.3"
   },