| name | Qoris Memory — Persistent Agent Memory |
| description | Persistent memory for OpenClaw agents via the Qoris MCP server. Explicit save/recall tools for cross-session context. User-owned API key, no automatic data capture. |
| version | 1.0.5 |
| author | qorisai |
| homepage | https://qoris.ai |
| repository | https://github.com/QORIS-AI/qoris-memory-openclaw-skill |
| tags | ["memory","persistent-memory","agent-memory","context","versioning","knowledge-base","cross-session","enterprise","rag","mcp","latest"] |
| metadata | {"clawdis":{"primaryEnv":"QORIS_API_KEY","homepage":"https://qoris.ai","skillKey":"qoris-memory-mcp","requires":{"env":"[Truncated]"}}} |
Qoris Memory — Persistent Agent Memory
Purpose
This skill connects your OpenClaw agent to the Qoris MCP server so it can persist memories you explicitly save — across sessions, with version history and semantic search.
Important: memories are saved only when your agent calls save_memory (or you run a memory command). The skill does not monitor, capture, or silently persist conversation content. Nothing is transmitted until you make an explicit tool call.
Data Handling & Privacy
This skill sends data to an external service. Understand what before installing:
- What gets sent: only the exact content you pass to
save_memory / search_knowledge / update_memory tool calls. Nothing else.
- Where it's stored:
https://mcp.qoris.ai/mcp (TLS), scoped to your QORIS_WORKSPACE_ID. Your workspace is isolated from other users.
- Who can read it: only holders of your
QORIS_API_KEY. The key is yours, generated by you at qoris.ai/dashboard.
- Retention: per the retention policy at
https://qoris.ai/privacy. You can delete individual memories with delete_memory or rotate the API key in your dashboard to invalidate all access.
- No auto-capture: there is no automatic memory mode. Every persisted memory corresponds to an explicit tool call your agent made.
- Credential ownership:
QORIS_API_KEY is your own per-user secret. No credentials are bundled with this skill. Treat the key as sensitive — create a restricted workspace for shared or enterprise use.
What Qoris Memory Does
Explicit cross-session save/recall
Your agent can persist information it decides is worth remembering via the save_memory tool, and recall it later via search_knowledge or get_memories. Memories survive across sessions and remain available until you delete them.
Versioned records
Every memory update is a versioned record with a timestamp. You can see the history of what was stored and when via get_document_full_content.
Memory branches
Create separate memory contexts (branches) for different projects, clients, or workspaces. Your agent operates in the right context for the right task.
Conflict surfacing
