docs: update OpenClaw integration docs v2

[Prasanna721]

docs: OpenClaw integration v2 documentation

Restructure OpenClaw docs for Openclaw v2

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	supermemory-app	e401760	Feb 17 2026, 06:24 AM

[Prasanna721]

• docs: update OpenClaw integration docs v2 #743 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label Main to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[linear]

ENG-579 Update Openclaw v2 documentation

[graphite-app]

Merge activity

• Feb 17, 6:20 AM UTC: Dhravya added this pull request to the Graphite merge queue.
• Feb 17, 6:22 AM UTC: Merged by the Graphite merge queue.

[sentry]

Bug: The documentation introduces new CLI setup commands (e.g., openclaw supermemory setup) that may not exist in the external OpenClaw plugin, blocking user setup.
_{Severity: HIGH}

Suggested Fix

Verify that the openclaw supermemory setup, setup-advanced, and status commands are implemented and functional in the OpenClaw v2 plugin. If they are not, either remove them from the documentation or revert to the previous setup instructions that used environment variables until the CLI is ready.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: apps/docs/integrations/openclaw.mdx#L83-L89

Potential issue: The documentation for the OpenClaw integration was updated to use new
CLI commands like `openclaw supermemory setup` as the primary setup method. These
commands are not part of the main Supermemory codebase and are presumed to exist in the
separate OpenClaw v2 plugin repository. If these commands are not implemented in the
plugin as documented, users will encounter 'command not found' errors and will be unable
to configure the integration, as this is presented as the main setup path.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[sentry]

Bug: The documentation suggests using ${VAR} syntax for an API key inside a JSON configuration. Standard JSON does not support this, which will likely cause authentication failures.
_{Severity: HIGH}

Suggested Fix

Remove the ${VAR} syntax from the JSON example. Instead, instruct users to set the environment variable in their shell profile and then use a placeholder in the JSON, like "apiKey": "YOUR_API_KEY_HERE", with a comment explaining that the plugin will read the SUPERMEMORY_OPENCLAW_API_KEY environment variable if the key is not hardcoded.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: apps/docs/integrations/openclaw.mdx#L118

Potential issue: The manual configuration section in the OpenClaw integration
documentation provides a JSON snippet where the API key is set using
`${SUPERMEMORY_OPENCLAW_API_KEY}`. Standard JSON does not support environment variable
interpolation with this syntax. When the configuration is parsed, the `apiKey` field
will contain the literal string `"${SUPERMEMORY_OPENCLAW_API_KEY}"` instead of the key's
value. This will cause API authentication to fail, rendering the integration
non-functional for users who follow the manual setup.

_{Did we get this right? 👍 / 👎 to inform future reviews.}