What happened
Write what you worked on, investigated, decided and left unfinished. One timeline per day, with notes you can edit any time.
Open source · MIT licensed
Remember what you did, not just what you changed.
DevMemo is a personal developer journal. It puts your daily notes and your Git activity on one calendar, and lets your AI assistant search and update it through MCP.
Free to use. Or self-host it with one Docker command.
devmemo / journal / 2026-11-02
Today
Monday, November 2
Notes
- 10:05Webhooks returned 401 in staging. Investigating signature check.
- 12:40via AIRoot cause: body was parsed before HMAC verification. Decided to verify on the raw body.
Git activity acme/api
a3f91c2Verify webhook HMAC with raw body10:427be0d14Make commit ingestion idempotent11:18e52c8aaConvert commit time to user timezone15:06
The missing context
Git remembers the diff. Nobody remembers the day.
Why was this approach chosen? What did you spend Tuesday debugging? What is still unresolved? That context lives in your head for a week, then it’s gone. DevMemo keeps it, next to the commits it explains.
Three sources, one timeline
Each kind of information keeps its origin. Nothing overwrites anything else.
What changed
Commits arrive automatically from GitHub and land on the right day in your timezone. They stay separate from your notes.
What it means
Connect Claude or any MCP client to ask about your history, summarize a week, or add a note without leaving your editor.
How it works
- 01
Sign in with GitHub
No passwords, no setup wizard. Your journal is ready the moment you sign in.
- 02
Write and push
Jot down notes as you work. Push code as usual, and your commits show up on the calendar.
- 03
Ask your history
Point your AI assistant at DevMemo and ask what you did, when, and why.
Model Context Protocol
Your AI assistant answers from your actual history.
DevMemo exposes your journal as MCP tools. Claude Desktop, Claude Code and other MCP clients can read days, search notes and commits, and add notes, so answers come from your records, not from guesses.
- “What did I work on yesterday?”
- “Summarize my development activity this week.”
- “Which repositories did I touch last month?”
- “What problems did I investigate this week?”
- “Mark today as a workday.”
claude · devmemo connected
you › When did I last investigate webhook authentication?
⚙ search_journal { query: "webhook authentication" }
⚙ get_day { date: "2026-11-02" }
On Monday, Nov 2. Staging webhooks returned 401 because the payload was parsed before the HMAC check. You decided to verify against the raw body and shipped it in a3f91c2 on acme/api.
you › Add a note: follow up on retry handling tomorrow.
⚙ add_note → saved to 2026-11-02
Small on purpose
A small tool that works reliably beats a large one with infrastructure you don’t need.
- AI is optional
- The journal works fully without any AI provider configured.
- Your notes stay yours
- Git sync and AI never overwrite what you wrote. Every note records where it came from.
- One database is the truth
- Web, API and MCP all go through the same service, with the same rules.
DevMemo is not
- ×A Jira replacement
- ×A task board
- ×A team analytics dashboard
- ×A RAG infrastructure project
It’s a personal memory for software developers. Nothing more, on purpose.
Start remembering your work.
Sign in with GitHub and write your first note in under a minute.