diff --git a/apps/docs/integrations/opencode.mdx b/apps/docs/integrations/opencode.mdx
index 8de6db97..956f44ff 100644
--- a/apps/docs/integrations/opencode.mdx
+++ b/apps/docs/integrations/opencode.mdx
@@ -62,33 +62,17 @@ Or set an API key manually from the [API Keys](https://console.supermemory.ai/ke
   </Tab>
 </Tabs>
 
-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:
 
-<Tabs>
-  <Tab title="OpenCode V1">
-    ```jsonc
-    {
-      "plugin": ["opencode-supermemory@latest"]
-    }
-    ```
-  </Tab>
-  <Tab title="OpenCode 2">
-    ```jsonc
-    {
-      "plugins": ["opencode-supermemory"],
-      "permissions": [
-        { "action": "supermemory_recall", "resource": "*", "effect": "allow" }
-      ]
-    }
-    ```
+```jsonc
+{
+  "plugin": ["opencode-supermemory@latest"],
+  "plugins": ["opencode-supermemory"],
+  "permission": { "supermemory_recall": "allow" }
+}
+```
 
-    The `permissions` rule lets the read-only `supermemory_recall` tool run without prompting.
-  </Tab>
-</Tabs>
-
-<Warning>
-  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.
-</Warning>
+If OpenCode won't start after an older install, run the installer again to update your config.
 
 ## How it works