DevRecall is on-device memory for engineers. Chat your work history, generate standups, and write brag docs from Git, Slack, Calendar, Jira, Linear, and Confluence — without your activity ever leaving this laptop. Ships an MCP server, so your AI coding tool finally remembers what you've shipped.
brew install --cask pavelpilyak/devrecall/devrecall 
DevRecall keeps an on-device, embedding-searchable index of your work. Ask it questions, or let it write the routine docs for you.
An agent with read-only tools over your local index — FTS5 keyword search, vector search, date and source filters. Ask "what was that auth bug I fixed in February?" and it filters by date, then semantic-matches. Every answer cites the rows it read; nothing is invented.
Ships an MCP server out of the box — any MCP-compatible
coding tool (Claude Code, Cursor, Codex, Continue, Zed) can
spawn it as a stdio subprocess and gain search, citations,
and decision history over your local index.
/devrecall:recall what was that auth bug returns
cited PRs and commits inline — no leaving the editor.
devrecall standup writes "yesterday / today /
blockers" from real signal. Weekly roll-ups for Monday and
quarterly brag docs for perf review — sourced from data, not
memory.
Collapses your git email, GitHub handle, Slack ID, and Jira account into one "you". Works across orgs.
Defaults to local Ollama. BYOK for Claude or GPT. Embeddings run on-device via bundled ONNX — no GPU required.
Single Go binary on macOS and Linux. Native macOS app wraps the CLI for menu-bar use.
OAuth once, indexed locally. Tokens stay in your home directory; raw activity never leaves your laptop.
The whole point of DevRecall is that raw events stay on your machine. Activity data is never transmitted to a backend we control.
The only network calls DevRecall makes are to integrations you authorise (GitHub, Slack, Calendar) and — if you opt in — to the LLM provider you chose. A small Cloudflare Worker handles OAuth redirects so the CLI doesn't need to bind to a public port; it never sees your activity, only the OAuth handshake.
DevRecall is MIT-licensed end to end — CLI, desktop app, OAuth relay. There's no proprietary core, no telemetry hidden behind a flag, no "open core" plus paid cloud. If you don't trust the binaries, build your own.
Manual reads in about ten minutes. Pick where to drop in.
Yes. Once sources are synced and a local model is pulled, DevRecall runs entirely offline. It re-syncs when you come back online.
In a single SQLite database at
~/.devrecall/devrecall.db, alongside OAuth tokens
in ~/.devrecall/tokens/. Nothing else writes to
your machine.
No. There is no admin panel, no shared cloud, no exfiltration
path. Your index lives in ~/.devrecall/devrecall.db
— same place as your shell history.
macOS desktop app and CLI (Apple Silicon & Intel), Linux CLI
(x86_64 & aarch64) as .tar.gz and
.deb. Windows is not supported.
For summarisation, yes — a Gemma-class local model writes standups that read like yours. For chat over your work history, BYOK gives noticeably sharper answers.
One install command. Your work, remembered.
brew install --cask pavelpilyak/devrecall/devrecall