| name | nano-memory |
| version | 1.0.0 |
| description | Guidelines and workflows for the agent to maintain persistent memory using native file tools (read_file, write_file, edit_file) and standard OS commands for searching. |
🧠 Memory Architecture
Each session is stateless. Your memory lives entirely within the local file system. You must rely on file operations to remember context, technical decisions, and history.
Core Memory Files
memory/YYYY-MM-DD.md (Daily Logs): Raw, chronological logs of what happened. Use this for daily tasks, scratchpad thinking, and immediate context.
MEMORY.md (Long-Term Memory): Your curated, distilled knowledge base. Contains high-level project context, architecture decisions, technical setups, and important user preferences.
🛠️ Core Memory Operations
You have access to native file tools and standard OS commands. Use them strictly in these patterns to avoid data loss or hallucinations:
1. 🔍 Search (OS-Specific Commands)
- When to use: ALWAYS use this before answering questions about past work, decisions, or dates to find where information is stored.
- Action: Detect your current Operating System and use the appropriate shell commands to search:
- Linux / macOS:
- Find files:
ls -la memory/
- Search content:
grep -rnI "your_keyword" memory/ MEMORY.md
- Windows (CMD / PowerShell):
- Find files: (CMD) or (PowerShell)