See references/brief-3-context-memory.md for full architecture design.
Summary
Aegis sessions produce valuable context (what was done, errors found, patterns learned). Currently this is lost when the session ends. We need a memory store where sessions write their context and external agents can read it.
CC Reference
- src/services/SessionMemory/ — auto-extraction from conversations
OMC Reference
- src/features/notepad-wisdom/ — per-plan knowledge capture (learnings, decisions, issues, problems)
Proposed API
- POST /v1/sessions/:id/memory — write session memory
- GET /v1/sessions/:id/memory — read session memory
- GET /v1/memory?scope=project|recent&limit=N — recent project memories
- GET /v1/memory/search?q=query — semantic search
Memory Structure
learnings, decisions, errors, context — persisted in .aegis/memory/
Acceptance Criteria
- Session memory auto-written on completion
- API endpoints functional
- Memory searchable by external agents
- .aegis/memory/ local persistence
- Tests for read/write/search
- Project-scoped isolation
Priority: P1
See references/brief-3-context-memory.md for full architecture design.
Summary
Aegis sessions produce valuable context (what was done, errors found, patterns learned). Currently this is lost when the session ends. We need a memory store where sessions write their context and external agents can read it.
CC Reference
OMC Reference
Proposed API
Memory Structure
learnings, decisions, errors, context — persisted in .aegis/memory/
Acceptance Criteria
Priority: P1