---
title: "Temporal memory for OpenClaw"
description: "OpenClaw stores selected context in MEMORY.md and daily notes. Add queryable temporal memory through the past.dev API."
canonical: https://past.dev/integrations/openclaw
last-updated: 2026-08-31
---
# Memory for OpenClaw

Source: https://past.dev/integrations/openclaw

OpenClaw uses MEMORY.md for durable notes, daily memory files for recent context and a pre-compaction flush for selected state. File-based memory does not provide entity resolution, fact validity periods or structured supersession. Keep identity and standing instructions in files. Store changing facts in a queryable memory service when those functions are required.

## How OpenClaw's native memory works

[OpenClaw](https://github.com/openclaw/openclaw) stores identity and standing instructions in Markdown bootstrap files, durable notes in MEMORY.md and recent context in dated memory files. A flush step writes selected state before context compaction. Users can inspect these files directly.

## Where files stop scaling

- **Retrieval is grep.** Finding the right note depends on the note using the words you searched.
- **No time model.** A note from February and its March correction sit in the same file; the agent quotes whichever it reads first.
- **Compaction.** Only content written before compaction persists. The saved content remains unstructured prose.
- **Single-agent scope.** Two OpenClaw instances, or one agent plus your product, cannot share files cleanly.

These are the same limits every file-based memory hits; the [LLM-wiki pattern](/what-is-agent-memory) has them too. Files hold slow knowledge well. Changing facts need structure.

## The integration: teach OpenClaw two commands

OpenClaw agents run shell commands, so the integration is two curl calls the agent learns from its instructions: remember and recall.

```bash
# remember: store a fact at the time it happened
curl -s -X POST https://api.past.dev/api/v1/ingest \
  -H "Authorization: Bearer $PAST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"content": "Sam approved the Q4 budget of 40k", "timestamp": "2026-08-28T14:00:00Z"}'

# recall: ask the memory before answering history questions
curl -s -X POST https://api.past.dev/api/v1/recall \
  -H "Authorization: Bearer $PAST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "What is the approved Q4 budget?"}'
```

Add two rules to the agent instructions: write durable facts with their original timestamps, and recall before answering questions about people, decisions or history. Keep identity and standing preferences in MEMORY.md.

Applications can route on `status`. `Supported` means the evidence establishes the answer. `Conflicted` returns evidence from credible sources that disagree. `NoKnownSupport` means the stored evidence does not establish an answer. `UnknownBecauseDegraded` means retrieval could not complete and should be treated as an unknown result.

## What changes in daily use

- Facts written before compaction remain available in the API with dates.
- The March correction supersedes the February note instead of coexisting with it; both remain for as-of questions.
- Retrieve changes for a specified period from stored validity windows.
- Your OpenClaw agent and your product agents share one memory with one key model.

The [quickstart](/docs/memory-api/quickstart) documents setup. [Benchmarks](/benchmarks) reports recall evaluation. [Fact supersession](/glossary/fact-supersession) explains update handling.

## Frequently asked questions

### Should I delete MEMORY.md?

No. Files are the right place for identity, tone and standing preferences: slow knowledge the agent reads at startup. Move the changing facts, events, decisions and people-state into the API.

### How is this different from the memory plugins?

Most OpenClaw memory plugins index local files or transcripts for search. past.dev adds entity resolution, validity dates, supersession, and an insufficient-evidence status. Multiple agents and machines can query the same project memory.

## Related

- [Memory for the Claude Agent SDK](https://past.dev/integrations/claude-agent-sdk)
- [past.dev and claude-mem](https://past.dev/compare/claude-mem)
- [Fact supersession](https://past.dev/glossary/fact-supersession)
- [What is agent memory?](https://past.dev/what-is-agent-memory)
- [Quickstart](https://past.dev/docs/memory-api/quickstart)