Viktor.comAn AI coworker that actually does the work
Launching today
DevRecall
On-device memory for everything you ship
1 follower
On-device memory for everything you ship
1 follower
Most tools that remember your work ship it to someone's cloud. DevRecall keeps a searchable index of your whole work history on your laptop — local SQLite, offline embeddings, nothing leaves the machine. It pulls from Git, GitHub, Slack, Jira, Linear and Confluence, then links each ticket to the commits, PRs and threads that resolved it. Ask "what was that auth bug in February?" and answers cite real rows. Also an MCP server, so Claude Code and Cursor recall your history inline. MIT.
Hey Product Hunt 👋
I kept hitting the same wall: someone asks what I worked on last quarter, and I'm scrolling git log, Jira, and Slack trying to reconstruct it. The tools that solve this are mostly built for managers — dashboards that ingest your org's data into their cloud to measure teams. I wanted the opposite: something for me, that indexes the systems of record I actually work in, and never leaves my laptop.
So DevRecall does it entirely on-device. It pulls from Git, GitHub/GitLab, Slack, Calendar, Jira, Linear and Confluence into a local SQLite database, and everything — search, embeddings, grouping — runs on your machine. The only cloud piece is a Cloudflare Worker that forwards OAuth callbacks; it never sees your data.
Two things I'm most happy with:
Tickets linked to code. It extracts issue keys from commit messages and branch names, then groups a ticket with the commits, PRs and discussions that resolved it. "What happened with PROJ-123?" returns one timeline across all your sources — and that join is deterministic, no LLM guessing.
Memory for your coding agent. It ships an MCP server, so Claude Code, Cursor, Codex, Continue or Zed can search your work history inline, with citations.
Search fuses keyword and semantic matching, so a vague "stale sessions after a password change" finds the right work even with no exact keyword overlap. Answers always cite the rows they read — nothing invented.
Happy to answer anything — especially curious what sources people want next.