From a5c3a9fcbcb456101da56e4ca5ece130d99a2dc5 Mon Sep 17 00:00:00 2001 From: MaheshtheDev <38828053+MaheshtheDev@users.noreply.github.com> Date: Tue, 3 Nov 2026 16:33:03 +0000 Subject: [PATCH 1/4] docs(opencode): installer writes the V1 permission rule Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- apps/docs/integrations/opencode.mdx | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/apps/docs/integrations/opencode.mdx b/apps/docs/integrations/opencode.mdx index 8de6db97..3763caf2 100644 --- a/apps/docs/integrations/opencode.mdx +++ b/apps/docs/integrations/opencode.mdx @@ -76,18 +76,16 @@ OpenCode V1 and OpenCode 2 read different keys from `~/.config/opencode/opencode ```jsonc { "plugins": ["opencode-supermemory"], - "permissions": [ - { "action": "supermemory_recall", "resource": "*", "effect": "allow" } - ] + "permission": { "supermemory_recall": "allow" } } ``` - The `permissions` rule lets the read-only `supermemory_recall` tool run without prompting. + The `permission` rule lets the read-only `supermemory_recall` tool run without prompting. OpenCode 2 reads this V1-style rule too. - The installer writes all three keys (`plugin`, `plugins`, and `permissions`) so that one file covers both versions. OpenCode V1 refuses to start when the file has a top-level `permissions` field ("V2 permissions are not supported by OpenCode V1"), so V1 users must remove `permissions` after installing. V1 ignores `plugins` with a warning, so you can remove it too. + The installer writes `plugin`, `plugins`, and `permission` so that one file covers both versions. Installers before 2.1.1 wrote a top-level `permissions` field instead, which OpenCode V1 1.19 and later refuse to start with ("V2 permissions are not supported by OpenCode V1"). Run the installer again to replace it. OpenCode V1 1.17 and 1.18 also reject the `plugins` key, so remove it on those versions. ## How it works From 570a0a593260812102d747127f68a3ff1d1737ea Mon Sep 17 00:00:00 2001 From: MaheshtheDev <38828053+MaheshtheDev@users.noreply.github.com> Date: Fri, 6 Nov 2026 16:32:00 +0000 Subject: [PATCH 2/4] docs(claude-code): MCP tools follow Claude Code permission rules Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- apps/docs/integrations/claude-code.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/integrations/claude-code.mdx b/apps/docs/integrations/claude-code.mdx index 1bce1aac..aaf401a9 100644 --- a/apps/docs/integrations/claude-code.mdx +++ b/apps/docs/integrations/claude-code.mdx @@ -75,7 +75,7 @@ Once installed, the plugin runs automatically: - **Direct recall** — Before Claude sees each substantive prompt, the hook searches Supermemory and injects fresh matches. Set `recallDirective` to switch to advisory mode, where Claude decides when to search. - **Auto-capture** — After each Claude response (the Stop hook), conversation content added since the last save is captured in the background. - **Shared repo memory** — Captures go to one repository container shared with the Codex, OpenCode, and Cursor plugins, tagged with `sm_scope: personal` metadata. -- **MCP tools** — The hosted Supermemory MCP tools (`search_memory`, `add_memory`, and more) use the same credentials. `search_memory` and the legacy camelCase read tools (`listMemories`, `listDocuments`, `getDocument`, `listSpaces`, `whoAmI`) are approved automatically; other tools, including `list_memories`, `list_documents`, `get_document` and `get_profile`, still ask for approval. For deeper history, Claude can also use the `context-gatherer` agent. +- **MCP tools** — The hosted Supermemory MCP tools (`search_memory`, `add_memory`, and more) use the same credentials. The plugin doesn't pre-approve any of them, so each tool follows your Claude Code permission rules and asks for approval until you allow it. For deeper history, Claude can also use the `context-gatherer` agent. ## Commands From 4cae20ea3c9aa21ab741da546e7d8fce37857595 Mon Sep 17 00:00:00 2001 From: MaheshtheDev <38828053+MaheshtheDev@users.noreply.github.com> Date: Fri, 6 Nov 2026 16:54:33 +0000 Subject: [PATCH 3/4] docs(claude-code): restore auto-approval text until the plugin release ships Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- apps/docs/integrations/claude-code.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/integrations/claude-code.mdx b/apps/docs/integrations/claude-code.mdx index aaf401a9..1bce1aac 100644 --- a/apps/docs/integrations/claude-code.mdx +++ b/apps/docs/integrations/claude-code.mdx @@ -75,7 +75,7 @@ Once installed, the plugin runs automatically: - **Direct recall** — Before Claude sees each substantive prompt, the hook searches Supermemory and injects fresh matches. Set `recallDirective` to switch to advisory mode, where Claude decides when to search. - **Auto-capture** — After each Claude response (the Stop hook), conversation content added since the last save is captured in the background. - **Shared repo memory** — Captures go to one repository container shared with the Codex, OpenCode, and Cursor plugins, tagged with `sm_scope: personal` metadata. -- **MCP tools** — The hosted Supermemory MCP tools (`search_memory`, `add_memory`, and more) use the same credentials. The plugin doesn't pre-approve any of them, so each tool follows your Claude Code permission rules and asks for approval until you allow it. For deeper history, Claude can also use the `context-gatherer` agent. +- **MCP tools** — The hosted Supermemory MCP tools (`search_memory`, `add_memory`, and more) use the same credentials. `search_memory` and the legacy camelCase read tools (`listMemories`, `listDocuments`, `getDocument`, `listSpaces`, `whoAmI`) are approved automatically; other tools, including `list_memories`, `list_documents`, `get_document` and `get_profile`, still ask for approval. For deeper history, Claude can also use the `context-gatherer` agent. ## Commands From 8d2cb9a7d93f129848fcc2959397925481d62b93 Mon Sep 17 00:00:00 2001 From: MaheshtheDev <38828053+MaheshtheDev@users.noreply.github.com> Date: Fri, 6 Nov 2026 18:31:42 +0000 Subject: [PATCH 4/4] docs(opencode): one config for OpenCode V1 and OpenCode 2 Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- apps/docs/integrations/opencode.mdx | 32 ++++++++--------------------- 1 file changed, 9 insertions(+), 23 deletions(-) diff --git a/apps/docs/integrations/opencode.mdx b/apps/docs/integrations/opencode.mdx index 3763caf2..956f44ff 100644 --- a/apps/docs/integrations/opencode.mdx +++ b/apps/docs/integrations/opencode.mdx @@ -62,31 +62,17 @@ Or set an API key manually from the [API Keys](https://console.supermemory.ai/ke -OpenCode V1 and OpenCode 2 read different keys from `~/.config/opencode/opencode.jsonc`. Use the config for the version you run: +The installer adds Supermemory to `~/.config/opencode/opencode.jsonc`. This one config works on both OpenCode V1 and OpenCode 2: - - - ```jsonc - { - "plugin": ["opencode-supermemory@latest"] - } - ``` - - - ```jsonc - { - "plugins": ["opencode-supermemory"], - "permission": { "supermemory_recall": "allow" } - } - ``` +```jsonc +{ + "plugin": ["opencode-supermemory@latest"], + "plugins": ["opencode-supermemory"], + "permission": { "supermemory_recall": "allow" } +} +``` - The `permission` rule lets the read-only `supermemory_recall` tool run without prompting. OpenCode 2 reads this V1-style rule too. - - - - - The installer writes `plugin`, `plugins`, and `permission` so that one file covers both versions. Installers before 2.1.1 wrote a top-level `permissions` field instead, which OpenCode V1 1.19 and later refuse to start with ("V2 permissions are not supported by OpenCode V1"). Run the installer again to replace it. OpenCode V1 1.17 and 1.18 also reject the `plugins` key, so remove it on those versions. - +If OpenCode won't start after an older install, run the installer again to update your config. ## How it works