Memory
How AGH stores durable Markdown memory, scopes it across global and workspace contexts, consolidates it during dream sessions, and keeps it useful.
- Audience
- Operators running durable agent work
- Focus
- Memory guidance shaped for scanability, day-two clarity, and operator context.
Memory is the durable layer that survives a session. AGH stores memories as Markdown files behind typed indexes so agents can rediscover knowledge without replaying past transcripts. The runtime keeps two scopes — global and workspace — and a consolidation loop that prunes and merges what is no longer load-bearing.
Use this section when an agent should carry durable project knowledge across sessions, when a workspace needs facts that should not live in a prompt, or when consolidation changed a memory file and you need to understand why. Memory is not a transcript archive. It is a curated working set: small enough for agents to read, typed enough to inspect, and scoped enough that one project does not leak into another.
In this section
System
Memory system
Use this page for storage layout, prompt injection, and the CLI/API surfaces that read or mutate memory.
Scopes
Global vs workspace memory
Use this page when you need scope resolution rules and where each kind of memory lives on disk.
Dream
Dream consolidation
Use this page when you need to understand the consolidation loop and what a dream session changes.
Hygiene
Memory best practices
Use this page when authoring memories: keep them small, durable, and verifiable.