V · MemoryEmerging★

Procedural Memory

also known as Skill Memory, How-To Memory, Learned-Procedure Store

Maintain a third agent memory type alongside episodic (past events) and semantic (facts): procedural memory captures *learned how-to* — reusable skills, workflows, and self-rewritten system instructions that map situations directly to actions.

Context

An agent operates across many sessions and accumulates experience. Some of that experience is best stored as facts (semantic), some as event records (episodic). A third category — how to do something — does not fit either: it's the agent's accumulated playbook, recipes, and shortcuts. Without a dedicated store, this knowledge either lives in a static system prompt (no learning) or gets re-derived from episodic memory each time (slow, wasteful).

Problem

Episodic memory stores 'on 2026-03-12 I did X'; semantic memory stores 'X is true'. Neither stores 'when situation S arises, the right action sequence is A1, A2, A3'. Without a procedural store, the agent re-derives skills from raw episodes on every invocation, or relies on a frozen system prompt that cannot improve. LangChain's LangMem SDK explicitly names this gap and provides three memory types; the arXiv ProcMEM paper shows learned procedural memory outperforms episodic-only retrieval on reusable-skill tasks.

Forces

  • Episodic memory recalls past events but does not generalise to reusable shortcuts.
  • Static system prompts cannot improve from experience.
  • Procedural memory must be safely updatable — the agent rewriting its own instructions is itself a risk surface (see rogue-agent-drift).
  • Skills must be retrievable by situation, not by keyword — requires structured indexing.

Example

A software-engineering agent works across hundreds of pull-request reviews. Initially, it re-derives the right review approach (run tests, check coverage, look for security smells) from its general training each time. After adopting procedural memory, the agent stores 'on PRs touching auth code, the right procedure is: 1) load OWASP cheatsheet, 2) check auth-test coverage, 3) flag any new secrets to security review'. On future auth PRs, the procedural retrieval surfaces this playbook, saving derivation cost and producing more consistent reviews. Updates to the procedure require a successful application before they overwrite the prior version.

Diagram

Solution

Therefore:

Implement a procedural-memory store as a first-class memory type alongside episodic and semantic. Entries are (situation pattern, action sequence, success record). The agent reads at planning time and appends after successful workflows. Updates are gated — naïvely letting the agent overwrite its own playbook risks rogue-drift, so add provenance and review. Common implementations: LangChain's LangMem 'procedural' channel, Claude Agent Skills (manually authored), ProcMEM-style learned skill libraries.

What this pattern forbids. Imposes a third memory type with structured situation→action indexing and update governance; constrains the agent to retrieve procedures by situation match rather than by free-text query.

And the patterns that stand alongside it, or against it —

  • complementsEpisodic Summaries★★— Compress past episodes into summaries that preserve gist while shedding token cost.
  • complementsKnowledge Graph Memory★— Persist agent memory as entities and relations in a structured graph so symbolic queries (path, neighbour, type) become possible.
  • complementsSelf-Archaeology·— Synthesize the agent's past thought history into time-layered trajectory notes so it can articulate how its understanding evolved without recomputing the narrative each time.
  • complementsDream Consolidation Cycle★— Run a deeper, slower reflection pass distinct from per-tick reflection — reading hours of recent thoughts, promoting themes, releasing affective residue, and clearing working memory — so the agent does not accumulate residue indefinitely.
  • conflicts-withRogue Agent Drift✕— Anti-pattern: deploy a long-running agent with persistent memory and self-modification ability, then leave it without periodic re-alignment to its stated purpose.
  • complementsSemantic Memory★— Maintain a dedicated store of what the agent holds to be true about the user and the world, separate from event records (episodic) and learned how-to (procedural).
  • complementsEpisodic Memory★★— Record past events as time-stamped first-person experiences the agent can recall later, separately from extracted facts (semantic) and learned how-to (procedural).
  • complementsMemory-Type Storage Specialization★★— Use different storage technologies optimized per memory type — fast in-memory stores (Redis-class) for episodic, vector databases (Pinecone/Weaviate) for semantic, relational or workflow engines for procedural — instead of one general store for everything.
  • complementsThree Layers of Agentic AI Memory★— Architect agent memory as three integrated concentric layers — Short-Term Memory (outer), Long-Term Memory (middle), Feedback Loops (core) — operating together as a unit rather than as separable optional components.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

Used in frameworks

References

Provenance