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/6] 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 8de6db972..3763caf2f 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/6] 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 1bce1aac2..aaf401a9e 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/6] 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 aaf401a9e..1bce1aac2 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/6] 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 3763caf2f..956f44ff1 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" }
- }
- ```
-
- The `permission` rule lets the read-only `supermemory_recall` tool run without prompting. OpenCode 2 reads this V1-style rule too.
-
-
+```jsonc
+{
+ "plugin": ["opencode-supermemory@latest"],
+ "plugins": ["opencode-supermemory"],
+ "permission": { "supermemory_recall": "allow" }
+}
+```
-
- 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
From ec44dfa8bdc07eabb74659363eefc7112168e031 Mon Sep 17 00:00:00 2001
From: MaheshtheDev <38828053+MaheshtheDev@users.noreply.github.com>
Date: Mon, 9 Nov 2026 16:32:28 +0000
Subject: [PATCH 5/6] docs(migration): untagged v3 connectors live in
sm_project_default on v5 (mono#3744)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---
apps/docs/snippets/api-v5-overview.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/apps/docs/snippets/api-v5-overview.mdx b/apps/docs/snippets/api-v5-overview.mdx
index a63c37092..6853d82e3 100644
--- a/apps/docs/snippets/api-v5-overview.mdx
+++ b/apps/docs/snippets/api-v5-overview.mdx
@@ -77,7 +77,7 @@ URL values are positional (`namespace` first, then `id` where there is one); eve
### Connectors
-Connector routes also move under the namespace. Legacy `containerTags` arrays become one namespace per connector.
+Connector routes also move under the namespace. Legacy `containerTags` arrays become one namespace per connector. Connectors created without container tags belong to `sm_project_default`, where their syncs already write documents.
| Legacy | v5 | SDK method |
| --- | --- | --- |
From b60ededd5b700e63859692754738313de95defd6 Mon Sep 17 00:00:00 2001
From: MaheshtheDev <38828053+MaheshtheDev@users.noreply.github.com>
Date: Tue, 10 Nov 2026 07:23:06 +0000
Subject: [PATCH 6/6] docs(opencode): write OpenCode versions as v1 and v2
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
---
apps/docs/integrations/opencode.mdx | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/apps/docs/integrations/opencode.mdx b/apps/docs/integrations/opencode.mdx
index 956f44ff1..e99a56765 100644
--- a/apps/docs/integrations/opencode.mdx
+++ b/apps/docs/integrations/opencode.mdx
@@ -62,7 +62,7 @@ Or set an API key manually from the [API Keys](https://console.supermemory.ai/ke
-The installer adds Supermemory to `~/.config/opencode/opencode.jsonc`. This one config works on both OpenCode V1 and OpenCode 2:
+The installer adds Supermemory to `~/.config/opencode/opencode.jsonc`. This one config works on both OpenCode v1 and v2:
```jsonc
{
@@ -82,7 +82,7 @@ Once installed, the plugin runs automatically:
- **Direct Recall** — On every substantive prompt, the plugin searches the current project and injects up to five fresh matches. Set `recallMode` to `"advisory"` to let the agent decide when to search, or `"off"` to disable it.
- **Automatic Capture** — Completed turns are saved every `captureEveryNTurns` turns (fresh installs use `0`, which saves only at the end), and any remainder is flushed when the session ends or OpenCode shuts down.
- **Keyword Detection** — Phrases like "remember" or "save this" nudge the agent to save to memory.
-- **Smart Compaction** — On OpenCode V1, sessions are summarized at 80% context capacity; on OpenCode 2, the plugin enriches native compaction. Both save the summary as a memory.
+- **Smart Compaction** — On OpenCode v1, sessions are summarized at 80% context capacity; on OpenCode v2, the plugin enriches native compaction. Both save the summary as a memory.
- **Privacy Protection** — Content within `` tags never persists.
### Memory scopes
@@ -146,8 +146,8 @@ Create `~/.config/opencode/supermemory.jsonc`:
"keywordPatterns": ["log\\s+this"], // Extra auto-save triggers
"recallMode": "direct", // "direct", "advisory", or "off"
"captureEveryNTurns": 3, // Save completed turns every N turns (0 = session end only)
- "compactionThreshold": 0.80, // OpenCode V1: context usage ratio for summarization
- "compactionEnabled": true // OpenCode 2: enrich native compaction and save summaries
+ "compactionThreshold": 0.80, // OpenCode v1: context usage ratio for summarization
+ "compactionEnabled": true // OpenCode v2: enrich native compaction and save summaries
}
```