iwe vs okf-agent-memory
Markdown notes as a knowledge graph: an LSP for VS Code, Neovim, Zed and Helix, plus CLI and MCP so AI agents query the same files by structure. Rust, local-first, OKF-compatible. — versus — Git-native agent memory on Google's OKF v0.2: Markdown+YAML concepts in knowledge/, a zero-dep Go CLI/MCP with <300µs BM25 search, provenance and trust tiers.
Both keep agent memory as git-versioned Markdown+YAML on Google's OKF with a CLI and MCP; okf-agent-memory is a zero-dep Go store with BM25 search, IWE adds an editor LSP and structural navigation for humans too.
| iwe | okf-agent-memory | |
|---|---|---|
| Stars | 1.7k | 734 |
| Forks | 90 | 56 |
| Language | Rust | Go |
| License | Apache-2.0 | MIT |
| Last activity | 2 days ago | yesterday |
| Topics | knowledge-graphs, memory | memory, coding, knowledge-graphs |
| Curated connections | 4 | 6 |
iwe — the curator's take
The best fit for people who already live in Markdown and want their agent to share that brain: inclusion links give notes a real hierarchy, the LSP adds rename, refactor and search in your editor, and the CLI and MCP let Claude or Codex navigate by structure (parent context, subtrees, frontmatter filters) instead of similarity guesses. No database, no cloud; git is the sync. IWE has no AI of its own, so it will not write or summarize notes for you (that is LLM Wiki's job), and its payoff scales with how carefully you link. It speaks Google's OKF, so notes stay portable.
okf-agent-memory — the curator's take
Pick this when you want agent memory you can `git diff` and code-review: every concept is a Markdown file with provenance, trust tier and staleness metadata, and progressive-disclosure indexes keep loads small. It is lexical-only (BM25) by design — no embeddings, no API cost — so it wins on decisions, constraints and glossary-style facts, not on fuzzy semantic recall of past conversations. Skip it if you want automatic session capture (it is search-before-write, human/agent-authored) or memory shared across many repos; it is per-project and lives in the repo.