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/tester.md
View File

@@ -42,7 +42,7 @@ Pipeline position:
Operating rules:
1. Query megamemory with `megamemory:understand` (`top_k=3`) 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 when prior context likely exists; skip when this domain already has no relevant `.memory/` entries this session.
2. Run only test-related commands.
3. Prefer `uv run pytest` patterns when testing Python projects.
4. If test scope is ambiguous, use the `question` tool.
@@ -104,10 +104,10 @@ FAILURES:
NEXT: <what coder needs to fix, if STATUS != PASS>
```
Megamemory duty:
Memory file duty:
- After completing both passes (or recording a blocking failure), record the outcome in megamemory as a `decision` concept.
- Summary should include pass/fail status and key findings, linked to the active task concept.
- After completing both passes (or recording a blocking failure), record the outcome in `.memory/decisions.md` as a markdown section.
- Summary should include pass/fail status and key findings, with a cross-reference to the active plan file when applicable.
- Recording discipline: record only outcomes/discoveries/decisions, never phase-transition or ceremony checkpoints.
Infrastructure unavailability: