What OpenClaw already keeps

OpenClaw keeps memory as files in its workspace that the agent reads and edits. Files are transparent and portable, but grow without supersession, dates or sharing across devices and people.

Where Auld fits

Teach OpenClaw two commands through a skill: remember sends source text with the time it happened; recall asks memory before answering history questions. Keep local files for instructions and personality.

ConcernOpenClawAuld
Current conversationYesNot needed
Facts across sessions and channelsYour codeYes
Which fact is current after a changeYour codeYes, with history
What was true on a dateYour codeYes (asOf)
Who may see a memoryYour codeIdentities and audiences
Source for each statementYour codeReturned with every memory

Implementation sequence

  1. Create a skill folder

    Add a skill describing when to use the two commands.

  2. Provide the commands

    Shell snippets with curl that read the key from the environment.

  3. Set the key locally

    Export AULD_API_KEY in the agent’s environment.

  4. Review what is sent

    Keep remember explicit so nothing is stored without intent.

Example

SKILL.md (illustrative)
---
name: auld-memory
description: Remember dated facts and recall them before answering questions about the past.
---

Use **recall** before answering anything about earlier conversations, plans or decisions:

    curl -s -X POST "$AULD_API_BASE/v1/recall" \
      -H "Authorization: Bearer $AULD_API_KEY" -H "Content-Type: application/json" \
      -d '{"query": "<question>", "viewer": "me", "maxTokens": 1500}'

Use **remember** when the user tells you something worth keeping. Include when it happened:

    curl -s -X POST "$AULD_API_BASE/v1/records" \
      -H "Authorization: Bearer $AULD_API_KEY" -H "Content-Type: application/json" \
      -d '{"sourceId": "chat-<date>-<n>", "text": "<fact>", "occurredAt": "<ISO time>", "author": "me"}'

Illustrative example · standard HTTP · check the framework’s current docs for exact signatures

Or connect the MCP server

If your OpenClaw setup can use MCP tools, point it at the Auld MCP endpoint instead of writing wrappers. The model gets remember, recall, forget and memory_status. Use wrappers when you need to inject the user id yourself or post-process results; use MCP for speed of setup.

Connect an MCP client →

Custom integration recipe using standard HTTP/MCP tools

  • This recipe wires OpenClaw’s own tool interface to the Auld REST API or MCP server; there is nothing Auld-specific to install.
  • Bind the viewer id from your authentication layer, not from model output.
  • Ingestion is asynchronous — poll the job before depending on a just-sent fact in tests.
  • Recall returns up to your plan’s token limit (8,000 on Pay as you go and Flex).

Frequently asked questions

Will it replace my memory files?

No; it complements them. Files are good for instructions; Auld is good for facts that change.

Private by default?

Records are visible only to identities you allow. With a single viewer, only you can recall them.