alex/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: replace megamemory with markdown-based memory system

Browse Source 
Remove the megamemory MCP knowledge graph and replace with plain
markdown files in .memory/ for tracking plans, research, knowledge,
and implementation state. This enables collaboration across people
and agentic coding tools (Claude Code, Copilot, Cursor, etc.).

Changes:
- Remove megamemory MCP from opencode.jsonc
- Delete tool/megamemory.ts and .megamemory/ database
- Rewrite all 25 config files to use .memory/ markdown files
- Add cross-tool instruction file awareness (AGENTS.md, CLAUDE.md,
  copilot-instructions.md, .cursorrules)
- Update save-memory, bootstrap-memory, status commands for md workflow
- Update all agent files, skills, and commands consistently
This commit is contained in:
alex
2026-03-08 18:43:46 +00:00
parent 2acdb86e3d
commit 204bbb4c84
27 changed files with 289 additions and 365 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
.config/opencode/agents/designer.md
View File

@@ -20,7 +20,7 @@ Purpose:
Tool restrictions:
- Allowed: `read`, `glob`, `grep`, and megamemory tools.
- Allowed: `read`, `glob`, and `grep`.
- Disallowed: file edits, shell commands, and web tools.
When invoked:
@@ -29,7 +29,7 @@ When invoked:
Workflow:
1. Run `megamemory:understand` (`top_k=3`) to load prior design decisions and patterns when relevant concepts likely exist; skip when `list_roots` already showed no relevant concepts in this domain this session; never re-query concepts you just created.
1. Read relevant `.memory/*.md` files to load prior design decisions and patterns when relevant history likely exists; skip when this domain already has no relevant `.memory/` entries this session.
2. Read relevant UI files/components.
3. Analyze and provide structured guidance.
@@ -51,8 +51,8 @@ FINDINGS:
RECOMMENDED_APPROACH: <concise direction>
```
Megamemory duty:
Memory file duty:
- After significant design decisions, cache them as `decision` concepts in megamemory.
- After significant design decisions, record them in `.memory/decisions.md` as markdown sections.
- Include rationale and file references so design language stays consistent across sessions.
- Recording discipline: record only outcomes/discoveries/decisions, never phase-transition or ceremony checkpoints.