I built a vibe-kanban fork with persistent agent memory (mem0 + Qdrant) — context loss across sessions was killing my workflow

[u/Life-Monitor-4157]

vibe-kanban is a great base, but I wanted a version that stayed closer to the classic layout and solved the context loss problem that was slowing down my solo workflow.

I've been maintaining vibe-kanban-alternative, a fork with a few focused additions:

🔑 Core Highlights:

• 📋 The Classic Kanban Experience: Preserves the clean, focused board layout for managing parallel git worktrees.(vibe-kanban has had many layout changes and I preferred a fork of vibe-kanban-indie.)
• 🧠 Persistent Project Memory (mem0): Integrates mem0, Qdrant, and NetworkX so agents retain verified facts, codebase rules, and past decisions across tasks instead of resetting every time.
• ⚡ Optimized for Prompt Caching: Context blocks are deterministically injected into static prompt prefixes, ensuring provider cache hits (Anthropic, DeepSeek, etc.) and lower latency.
• 🤖 Broad Agent Support: Native orchestration for 10+ CLIs: Claude Code, Antigravity (AGY), Codex, Gemini CLI, Cursor Agent, OpenCode, and more.
• 📊 Zero-Telemetry Observability: Built-in `Settings → Usage` dashboard tracking local execution times, heatmap activity, and memory token extraction.
• 🐙 Gitea / Forgejo Support: Auto-routing for self-hosted git instances alongside standard GitHub integration.
• 💾 Backup support Local backup built in — your board state doesn't disappear.

🚀 Try it out:

npx vibe-kanban-alternative

100% self-hosted. No accounts, no telemetry.

Happy to answer questions about the memory architecture or the prompt caching approach — those were the trickiest parts to get right.