Claw Memory
UnverifiedShared memory service for AI agents (OpenClaw, KimiClaw, NanoClaw, etc). Use when user asks to store, retrieve, search, or share memories across agent instances. Also use for importing existing memory files (MEMORY.md, daily notes) into the shared service.
Install on your platform
Showing OpenClaw.
- 1
Run this in your terminal
terminal$ openclaw skills install claw-memory
What we know about this skill
Publisher
siddontang
Taken from the source listing. We haven't verified who controls this account.
Install target
Pinned to 75777c1f
Installs fetch a stored snapshot of that commit, so the code can't change after the fact.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 3 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: claw-memory.siddontang.workers.dev, opencollective.com, zero.tidbapi.com.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
raw.githubusercontent.comsource hostclaw-memory.siddontang.workers.devundeclaredopencollective.comundeclaredgithub.comsource hostzero.tidbapi.comundeclaredWhat it found (3 of 31)
- SKILL.md:21contacts claw-memory.siddontang.workers.dev
curl -s -X POST https://claw-memory.siddontang.workers.dev/api/tokens | jq . - SKILL.md:27contacts claw-memory.siddontang.workers.dev
curl -s -X POST https://claw-memory.siddontang.workers.dev/api/tokens \ - SKILL.md:34contacts claw-memory.siddontang.workers.dev
curl -s -X POST https://claw-memory.siddontang.workers.dev/api/memories \
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned siddontang/claw-memory at 75777c1f87.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 75777c1f87
- Manifest
- SKILL.md
- Scanned
- 16 files, 4,174 lines
About this skill
What it does
Claw Memory is a service that allows different AI agent instances (like OpenClaw, KimiClaw, or NanoClaw) to share memory securely across those instances. It utilizes a Cloudflare Worker and TiDB Cloud backend, providing full data isolation by provisioning each token with its own dedicated TiDB Cloud Zero instance. Connection strings are encrypted at rest for enhanced security, and optional client-side encryption is supported for double protection.
When to use it
- Persistent State Across Agent Restarts: Share complex agent state (e.g., a long conversation history or ongoing task data) even if an agent instance crashes or restarts.
- Multi-Agent Collaboration: Enable multiple agents working on the same project to access and update shared information without needing to constantly retransmit data.
- Distributed Processing: Distribute parts of a larger task across different agent instances, allowing them to share intermediate results in a secure manner.
- Maintaining Context Across Scaling Events: Ensure that an agent’s context is preserved even when scaling up or down the number of agent instances.
Key capabilities
- Cross-instance memory sharing for Claw agents
- Full data isolation per token with dedicated TiDB Cloud Zero instances
- AES-256-GCM encrypted registry connection strings
- Optional client-side encryption using
X-Encryption-Keyheader - Zero-friction provisioning of TiDB Cloud Zero instances (~2 seconds)
- 30-day lifecycle for provisioned Zero instances
Example prompts
These are not prompts for the skill, but examples of what an agent might do with it:
- "Agent A, store this complex data structure in shared memory so Agent B can access it."
- "Agent C, retrieve the latest status update from shared memory and report it to me."
- "When I restart, load my previous session state from shared memory."
Tips & gotchas
Each token automatically provisions a TiDB Cloud Zero instance. Be mindful of the 30-day lifecycle; data will be lost after this period unless proactively migrated.