I open sourced memduck today.
It is a self-hosted AI memory workspace for the things that usually disappear across browser tabs, copied notes, screenshots, and chat channels.
The idea is simple: save useful material once, then ask against your own memory later with citations back to the original source.
Why I built it
Most note tools make it easy to save more, but retrieval still gets messy.
I wanted something closer to a personal memory engine:
- keep the raw source so I can always go back
- turn long links or pasted text into reusable memory cards
- capture from browser and chat channels
- ask questions only against material I actually saved
- keep model providers and channel setup visible in the UI
What it does now
memduck currently includes:
- a Next.js web workspace
- local SQLite storage
- browser extension capture
- Telegram runtime
- DingTalk / Slack / Discord / Feishu / WhatsApp-style channel adapters
- configurable model providers such as OpenAI, Anthropic, Gemini, Ollama, and OpenAI-compatible profiles
- grounded Q&A with citations over saved memory
It is still early, but the core loop is already there: capture, compile, retrieve, ask.
Who it is for
This is mainly for developers, builders, and researchers who want a self-hosted place to keep source-backed memory instead of sending every note into another hosted AI app.
If you care about local control, explicit provider setup, and source traceability, it may be worth trying.
Top comments (0)