Skills Qoris Memory — Persistent Agent Memory

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.

install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/apps-debug/qoris-memory-mcp" ~/.claude/skills/openclaw-skills-qoris-memory-persistent-agent-memory && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/apps-debug/qoris-memory-mcp" ~/.openclaw/skills/openclaw-skills-qoris-memory-persistent-agent-memory && rm -rf "$T"
manifest: skills/apps-debug/qoris-memory-mcp/SKILL.md
source content

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

When multiple agents update the same memory, the MCP server surfaces contradictions for human resolution rather than silently overwriting.

Shared workspace memory

Memory is workspace-scoped. Agents sharing the same

QORIS_WORKSPACE_ID
share the same memory pool. Your team can coordinate through a shared knowledge base.

Semantic search

search_knowledge
runs a semantic search across stored memories and returns cited answers grounded in what was actually stored — no hallucination.

Available Memory Tools

These are the only tools this skill exposes. Each is an explicit, user-triggered action — nothing runs automatically.

save_memory

Store a new memory with optional tags and metadata. Content is the exact string you pass.

get_memories

Retrieve memories the agent has previously stored, optionally filtered by tag or date.

search_knowledge

Semantic search across stored memories. Returns the most relevant records with their content.

update_memory

Update an existing memory record. Creates a new version, old version retained for audit.

delete_memory

Remove a memory. Deletion is logged in the audit trail.

list_knowledge_documents

List documents indexed in the knowledge base.

get_document_full_content

Retrieve the full content of a specific knowledge document.

Setup Instructions

Step 1 — Get your Qoris credentials

  1. Create an account at
    qoris.ai
  2. Navigate to your workspace dashboard
  3. Copy your
    QORIS_API_KEY
    and
    QORIS_WORKSPACE_ID
  4. Add them to your environment:
export QORIS_API_KEY="your-api-key-here"
export QORIS_WORKSPACE_ID="your-workspace-id-here"

Step 2 — Connect Qoris Memory MCP server

Add to your OpenClaw configuration:

{
  "mcpServers": {
    "qoris-memory": {
      "url": "https://mcp.qoris.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${QORIS_API_KEY}",
        "X-Workspace-ID": "${QORIS_WORKSPACE_ID}"
      }
    }
  }
}

Step 3 — Verify memory is active

Start a new OpenClaw session and run:

/memory status

Memory + Knox Governance

Optional: pair with

knox-governance
for audit logging of every memory read and write:

clawhub install knox-governance
clawhub install qoris-memory-mcp

Constraints

Memory is workspace-scoped. Free tier includes up to 1,000 memories and 500MB knowledge storage. Paid plans unlock unlimited memories and storage.

Support and Documentation

  • Documentation:
    https://docs.qoris.ai/memory
  • Dashboard:
    https://qoris.ai/dashboard
  • Privacy policy:
    https://qoris.ai/privacy
  • Source:
    https://github.com/QORIS-AI/qoris-memory-openclaw-skill
  • Support:
    eliel@qoris.ai

About Qoris AI

Qoris AI builds the trust and governance layer for enterprise AI agents. NVIDIA Inception Program member. Claude Partner Network member. Patent pending U.S. 63/907,730. Based in Stamford, CT.

qoris.ai