agent-memory

Manage task-scoped memory sessions and structured memory layers via a Neo4j-backed CLI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/led8/.codex --skill agent-memory-led8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-memory
Source: https://github.com/led8/.codex/tree/main/skills/agent-memory
Command: npx skills add https://github.com/led8/.codex --skill agent-memory-led8

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured, shell-driven memory system to manage task-scoped sessions, concise reasoning traces, and review-first durable memory for coding-agent workflows.

Core Features & Use Cases

  • Task-scoped sessions with a single session_id per active coding task.
  • Three memory layers (short-term, reasoning, long-term) with dedicated commands to capture, reason about, and persist knowledge.
  • Durable memory operations (add-fact, add-preference, add-entity) with safe modification paths (replace-*, alias-entity, merge-entity) to maintain a clean knowledge graph.
  • CLI surface via neo4j-agent-memory memory that supports recall, add, inspect, search, and delete workflows for reproducible coding sessions.

Quick Start

Start a local Neo4j instance and create a task-scoped memory session using the memory CLI to begin recording the active task workflow.

Frequently Asked Questions about agent-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add persistent memory to a coding agent for reasoning traces?

You can add persistent agent memory using a shell-based workflow that records reasoning traces and durable facts in a Neo4j-backed environment. It coordinates task-scoped sessions with structured short-term, reasoning, and long-term memory layers.

Do I need Neo4j to manage task-scoped sessions for CLI agents?

Yes, Neo4j is required to manage task-scoped sessions for CLI agents. The memory system uses a Neo4j-backed environment to store, recall, and manipulate structured knowledge graphs across coding tasks.

How do I structure agent memory layers for development tasks?

Agent memory is structured into three layers: short-term, reasoning, and long-term. You use dedicated CLI commands to capture data, reason about the task, and persist durable knowledge like facts, preferences, and entities.

Can I update and merge entities in a coding agent's knowledge graph?

Yes, you can update and merge entities in the knowledge graph using safe modification paths. The CLI supports replace-fact, replace-preference, alias-entity, and merge-entity workflows to maintain a clean and accurate memory state.

What is the best way to recall task-specific context for coding agents?

The best way to recall task-specific context is by using the CLI recall and search workflows. These commands retrieve traceable reasoning and durable knowledge from the active task-scoped session stored in the Neo4j memory system.

Why use a shell-based memory system instead of stateless coding agents?

A shell-based memory system provides traceable reasoning and durable knowledge persistence that stateless agents lack. It ensures reproducible coding sessions by maintaining structured facts and preferences across multiple task workflows.