initializing-memory

You organize an agent memory filesystem by exploding flat memory into a deeply hierarchical structure of 15-25 small, focused Markdown files spread across 2-3 nesting levels for fast context retrieval.

Flat memory layouts lose context because sprawling files lack navigable structure. Creating small, focused files of roughly 40 lines each within a 2-3 level directory tree renders necessary context efficiently in every turn.

The best way to structure memory files is using descriptive directory paths like system/ and memory/ with 2-3 nesting levels. This hierarchy ensures small, focused entries render context clearly for cross-session agent knowledge.

Yes, you can include executable scripts and reference content in your agent memory hierarchy. The structure supports optional resources via scripts/, references/, and assets/ directories to augment memory.

Yes, the memory hierarchy requires YAML frontmatter for its skill structure. It enforces a YAML-frontmatter-based format that mandates name and description fields for each small, focused Markdown entry.

The limitation of deeply nesting memory files is a strict cap of 2-3 levels and 15-25 total files to prevent sprawl. Exceeding this depth risks losing the fast retrieval benefits of small, focused 40-line entries.