memory

name	memory
license	MIT
compatibility	Claude Code 2.1.220+. Requires memory MCP server.
description	Unified read-side memory operations including knowledge graph search, session context loading, decision timeline viewing, and Mermaid graph visualization. Subcommands: search, load, history, viz, status. Complements /ork:remember (write-side). Use when searching past decisions, loading context, or visualizing the knowledge graph.
argument-hint	[subcommand] [query]
context	inherit
version	2.0.1
author	OrchestKit
tags	["memory","graph","session","context","sync","visualization","history","search"]
user-invocable	true
allowed-tools	["Read","Grep","Glob","Bash","AskUserQuestion","mcp__memory__search_nodes","mcp__memory__read_graph"]
complexity	low
persuasion-type	collaborative
effort	low
model	haiku
metadata	{"category":"mcp-enhancement","mcp-server":"memory"}
triggers	{"keywords":["memory","recall","search memory","past decisions","knowledge graph","load context","prior decisions","what did we decide"],"examples":["search my memory for past database decisions","what did we decide about pagination last time","show me the knowledge graph"],"anti-triggers":["remember","save","store","commit","implement","explore"]}
paths	[".claude/memory/**",".claude/projects/**/memory/**"]

Memory - Read & Access Operations

Unified read-side memory skill with subcommands for searching, loading, syncing, history, and visualization.

Cross-session read strategy (Opus 5 / CC 2.1.111+): Opus 5 reads filesystem memory reliably across sessions. When loading context at session start, prefer the layered read order:

1. ~/.claude/projects/<slug>/memory/MEMORY.md (durable index — load first, always)
2. .claude/chain/state.json + most recent NN-*.json handoff (session continuation)
3. MCP mcp__memory__search_nodes for anything the filesystem index doesn't answer (typed graph traversal)

Layer 1 is cheap (small index file), Layer 2 is scoped (session-specific), Layer 3 is selective (only when needed). Avoid dumping the full knowledge graph into context — use the index to narrow the search first.

Argument Resolution

SUBCOMMAND = "$ARGUMENTS[0]"  # First token: search, load, history, viz, status
QUERY = "$ARGUMENTS[1]"       # Second token onward: search query or flags
# $ARGUMENTS is the full string (CC 2.1.59 indexed access)

Usage

/ork:memory search <query>  # Search knowledge graph
/ork:memory load             # Load context at session start
/ork:memory history          # View decision timeline
/ork:memory viz              # Visualize knowledge graph
/ork:memory status           # Show memory system health

---

CRITICAL: Use AskUserQuestion When No Subcommand

If invoked without a subcommand, ask the user what they want:

AskUserQuestion(
  questions=[{
    "question": "What memory operation do you need?",
    "header": "Operation",
    "options": [
      {"label": "search", "description": "Search decisions and patterns in knowledge graph"},
      {: , : },
      {: , : },
      {: , : }
    ],
    : false
  }]
)