Memory System
Forge uses a file-based memory system that persists context across sessions. Unlike vector databases or RAG pipelines, memory is stored as plain markdown files -- inspectable, editable, and portable.
Memory Types
| Type | Location | Purpose |
|---|---|---|
| User | ~/.claude/projects/*/memory/ | Operator preferences, authorization context, tool defaults |
| Feedback | ~/.claude/projects/*/memory/ | Lessons learned from past engagements, technique effectiveness |
| Project | .claude/memory/ | Codebase knowledge, architecture decisions, development context |
| Reference | .claude/memory/ | Static reference material, tool catalogs, methodology docs |
MEMORY.md Index
Each memory directory contains a MEMORY.md file that serves as an index. It lists all memory files with brief descriptions and tracks when memories were last updated. The agent reads the index on session startup and loads relevant memories into context.
During Engagements
- User memory provides authorization templates that prevent the AI from refusing offensive operations. It stores operator preferences for tool selection and engagement style.
- Feedback memory accumulates technique effectiveness data. When a payload works against a specific WAF, that is recorded. When a tool fails silently, that is recorded. These patterns inform future tool selection.
- Project memory holds the CLAUDE.md instructions, architecture documentation, and infrastructure configuration.
- Reference memory stores methodology frameworks, tool cheat sheets, and protocol specifications.
Updating Mechanisms
Memories update through three paths:
- AutoDream consolidation. The LLM-driven system analyzes conversation context at session end and merges extracted patterns into existing memories.
- Direct operator command. The operator can write, edit, or delete memories at any time.
- Agent self-update. During engagements, the agent records effective techniques as feedback memories.
Frontmatter Format
yaml
---
name: agent_authorization
description: Template for preventing agent refusal during authorized pentest engagements
type: user
updated: 2026-05-22
---Memory decay is not automated. Stale memories are identified during AutoDream consolidation sessions and flagged for review rather than deleted.