Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)

· ai devtools web · Source ↗

TLDR

  • WUPHF is a self-hosted multi-agent office (Go + npx wuphf) where Claude Code, Codex, and OpenClaw agents share a git-backed markdown wiki with typed facts and per-entity append-only logs.

Key Takeaways

  • The shared wiki is a local git repo at ~/.wuphf/wiki/ with typed triplets, LLM-synthesized briefs committed under an archivist identity, /lookup cited-answer retrieval, and a /lint suite that flags contradictions, orphans, and stale claims.
  • Agents never auto-promote: raw context stays in a per-agent private notebook until the agent decides a fact is durable enough for the workspace-wide wiki.
  • Token efficiency comes from fresh-per-turn sessions with no accumulated history; the README claims 97% Claude API cache hit rate and a flat ~87k input tokens per turn versus 124k-to-484k growth in accumulated-session orchestrators.
  • Wiki backends are swappable: markdown (default since v0.0.6), nex (requires Nex API key), gbrain (OpenAI for embeddings + vector search, or reduced Anthropic-only mode), or none.
  • Pre-1.0 and moving daily; the README explicitly says to pin forks to release tags, not main.

Hacker News Comment Review

  • Discussion is thin at 7 comments; the thread has not yet surfaced implementation critiques or benchmarks challenges, leaving the README’s token-efficiency claims unverified by the community.
  • The Obsidian-vault question points at real positioning tension: the project’s value over a plugin is agent-native write access, push-driven wakes, and MCP tool scoping, but that trade-off is not foregrounded in the repo.
  • One commenter building a similar git-versioned markdown system (voiden.md) treats markdown’s LLM durability as the architectural reason, not just a format preference, which aligns with the project’s file-over-app design choice.

Notable Comments

  • @davedigerati: “why not an Obsidian vault with a plugin?” – the sharpest gap-test in the thread against the project’s design rationale.
  • @dhruv3006: building a similar git-versioned markdown tool (voiden.md) and frames markdown’s edge as durability for LLM reads, not just human readability.

Original | Discuss on HN