Standups, automatically
devrecall standup writes yesterday’s standup from your commits, PR
reviews, Slack threads, meetings, and ticket transitions.
DevRecall pulls activity from your dev tools, stores it in a local SQLite database, and turns it into something you can actually use: a standup, a weekly summary, a brag doc, a chat over your work history.
Standups, automatically
devrecall standup writes yesterday’s standup from your commits, PR
reviews, Slack threads, meetings, and ticket transitions.
Chat with your work
Ask “what was that auth bug I fixed in February?” and get an answer grounded in your actual activity.
Brag docs & perf reviews
Quarterly summaries with metrics, collaborators, and concrete deliverables — sourced from data, not memory.
Local-first by design
SQLite on your laptop. OAuth tokens in ~/.devrecall/tokens/ (0600).
BYOK or local Ollama for LLM. No proxy, no telemetry.
| Source | What gets collected |
|---|---|
| Git (local) | Commits, branch activity, files changed |
| GitHub | PRs, reviews, issues, comments |
| GitLab | MRs, reviews, issues |
| Bitbucket | PRs, comments |
| Slack | Your messages, threads you participated in |
| Google Calendar | Meetings attended, organized, declined |
| Jira | Issue transitions, comments, sprint membership |
| Confluence | Pages, blogposts, and comments you authored |
| Linear | Issue transitions, comments, cycle membership |
DevRecall ships an MCP server — any MCP-compatible
coding tool (Claude Code, Cursor, Codex, Continue, Zed) can search your
past work without leaving the editor. /devrecall:recall what auth bug did I fix in February returns cited commits, PRs, and tickets inline.
DevRecall is MIT-licensed. Audit it, fork it, build it from source. github.com/pavelpilyak/devrecall