From cda3bca0d063fdb180bf555afdc7fb33963a0a4e Mon Sep 17 00:00:00 2001
From: Prasanna721 <106952318+Prasanna721@users.noreply.github.com>
Date: Wed, 18 Feb 2026 06:02:41 +0000
Subject: [PATCH] docs: add FAQ section to OpenClaw integration page (#746)
docs: add FAQ section to OpenClaw integration page
Added FAQ section below Manual Configuration with 5 questions covering installation, custom container tags for Twitter
bookmarks, work/personal memory separation, non-technical setup via agent, and per-channel session memory separation with
feature request CTA.
---
apps/docs/integrations/openclaw.mdx | 133 ++++++++++++++++++++++++++++
1 file changed, 133 insertions(+)
diff --git a/apps/docs/integrations/openclaw.mdx b/apps/docs/integrations/openclaw.mdx
index 9b9c5543..436022e8 100644
--- a/apps/docs/integrations/openclaw.mdx
+++ b/apps/docs/integrations/openclaw.mdx
@@ -138,6 +138,139 @@ openclaw supermemory wipe # Delete all memories (requires confirma
+## FAQ
+
+
+
+ 1. Install the plugin:
+
+ ```bash
+ openclaw plugins install @supermemory/openclaw-supermemory
+ ```
+
+ 2. Run the setup wizard:
+
+ ```bash
+ openclaw supermemory setup
+ ```
+
+ 3. When prompted, paste your API key from [console.supermemory.ai](https://console.supermemory.ai). The key starts with `sm_`.
+
+ 4. Restart OpenClaw to activate the plugin:
+
+ ```bash
+ openclaw gateway --force
+ ```
+
+ 5. Verify the connection:
+
+ ```bash
+ openclaw supermemory status
+ ```
+
+ That's it — Supermemory is now connected and will automatically recall and capture memories across all your channels.
+
+
+
+ Use the advanced setup to enable custom container tags and add a read-only Twitter bookmarks container.
+
+ ```bash
+ openclaw supermemory setup-advanced
+ ```
+
+ When prompted, enter:
+
+ - **API key**: paste your `sm_` key
+ - **Container tag**: keep the default (or set your preferred root tag)
+ - **Auto recall**: `true` (recommended)
+ - **Auto capture**: `true`
+ - **Enable custom container tags**: `true`
+ - **Custom container tags**: `twitter-bookmarks:Twitter bookmarks saved from Twitter`
+
+
+ Custom container tags use the format `tag:description`, separated by a colon. For example: `twitter-bookmarks:Twitter bookmarks saved from Twitter`.
+
+
+ When asked for **custom container instructions**, enter something like:
+
+ ```
+ Whenever the user asks about Twitter bookmarks, search the twitter-bookmarks container.
+ Never save anything to the twitter-bookmarks container — it is read-only and populated directly from Twitter.
+ ```
+
+ This ensures the AI references your Twitter bookmarks when relevant but never writes to that container.
+
+
+
+ Use custom container tags to route memories by channel. Run the advanced setup:
+
+ ```bash
+ openclaw supermemory setup-advanced
+ ```
+
+ When prompted, enter:
+
+ - **API key**: paste your `sm_` key
+ - **Container tag**: keep the default
+ - **Auto recall**: `true`
+ - **Auto capture**: `true`
+ - **Enable custom container tags**: `true`
+ - **Custom container tags**:
+ - `work:Work-related memories from Slack and Gmail`
+ - `personal:Personal memories from Telegram and WhatsApp`
+
+ When asked for **custom container instructions**, enter:
+
+ ```
+ When the active channel is slack or gmail, always use the work container for storing and recalling memories. Never mix personal memories into work context.
+
+ When the active channel is telegram or whatsapp, always use the personal container. Do not recall or store work memories in personal conversations.
+ ```
+
+ This keeps your work and personal memories completely separated — Slack and Gmail conversations only see `work` memories, while Telegram and WhatsApp only see `personal` memories.
+
+
+
+ Ask the OpenClaw agent directly in any chat. No terminal needed.
+
+ ```
+ What are all the available configurations for the Supermemory plugin advanced mode?
+ ```
+
+ The agent will list every option. Then tell it what you want:
+
+ ```
+ Set up my Supermemory plugin with these settings:
+ - Auto recall: true
+ - Auto capture: true
+ - Enable custom container tags: true
+ - Custom containers:
+ - work: Work-related memories from Slack and Gmail
+ - personal: Personal memories from Telegram and WhatsApp
+ - Custom instructions: When on Slack or Gmail, use the work container.
+ When on Telegram or WhatsApp, use the personal container.
+ ```
+
+ Each custom container needs a **tag** and a **description** — e.g. `work: Work-related memories from Slack and Gmail`. The description helps the AI understand what belongs in that container.
+
+
+ You can change settings anytime by just telling the agent. For example: "Add a new container called `twitter-bookmarks` with description `Twitter bookmarks saved from Twitter` and make it read-only".
+
+
+
+
+ By default, all session memories across every channel are stored under a single root-level container tag.
+
+ To store specific memories separately, use **custom container tags** — see the FAQ above on separating work and personal memories.
+
+ Automatic per-channel separation is not supported yet. If you need this, let us know — with enough requests, we'll implement it right away.
+
+
+ Email us with your use case.
+
+
+
+
## Next Steps