Developer work journal for VS Code
Start with a private journal in VS Code. Connect cloud features only when you want hosted reports, history, or sharing.
Local-first by default. Sync only when you choose.
feat(auth): add token refresh handlingtodayfix(api): handle failed webhook retriestodayrefactor(ui): split dashboard widgetstodaytest(sync): add queue retry coveragetodayDaily engineering update
This fictional example groups authentication, webhook, dashboard, and sync work into a daily update.
Fewer interruptions when sessions expire or callbacks fail.
How to read the demo
The preview uses fictional, sanitized data. It shows the shape of CommitDiary’s report experience without presenting demo output as real work or verified test results.
Source activity
Commit messages, changed file names, change counts, and short code samples provide the source material.
Generated narrative
CommitDiary groups the evidence into a summary, changes, rationale, expected impact, and next steps.
Review boundary
A generated report does not prove that the code works or that tests passed. Review it against the repository.
Start locally
The local journal works without a CommitDiary account or API key. Open a Git repository in VS Code and let the extension capture eligible activity.
Install CommitDiary from the VS Code Marketplace. You do not need a cloud workspace to begin.
Open a trusted VS Code workspace that already uses Git, then confirm the extension is enabled.
CommitDiary detects eligible Git activity and adds it to your local journal, including while you are offline.
Optional cloud connection
A hosted workspace adds history, generated reports, and sharing. Turn it on when those features are useful to you.
Sign in to the dashboard only when you want hosted history, reports, or sharing.
Generate a key from dashboard Settings. The key is shown for secure setup and remains protected by the existing credential flow.
Run “CommitDiary: Setup Cloud Sync” in VS Code. The key is stored in VS Code SecretStorage.
See authorized synced work across repositories from the dashboard.
Create structured reports from synced commit context and review them before use.
Share supported activity and reports through the permissions provided by your hosted plan.
Where it helps
Walk in with a clear account of what changed and what comes next.
Show outcomes and maintenance work without asking everyone to read every diff.
Turn real engineering history into proof of how you build.
Give contributors and maintainers a readable record of repository progress.
Developer trust
Your local journal stays in VS Code. If you turn on cloud sync, CommitDiary sends only the commit details needed for your hosted journal and reports. Your full repository stays where it is.
Read the CommitDiary privacy noticeCommit discovery begins in the editor.
Unsynced work can wait until you reconnect.
Cloud sync adds selected commit details to your CommitDiary workspace.
Reports support review; they do not replace it.
Plans that stay understandable
The VS Code extension and local journal are the starting point. Paid plans add hosted history, AI reports, sharing, and Discord delivery.
You can install and use the local journal while current hosted plans load.
Keep a private work journal in VS Code while you decide if cloud reporting is useful.
Paid plans are billed through Paddle. Prices are localized where supported; final currency, tax, renewal, and total details are shown during checkout. Terms · Refund policy.
Questions, answered plainly
CommitDiary is a developer work journal for VS Code. It turns Git activity into clear reports about what changed, why it mattered, and what may need attention next.
The extension discovers commits in an open Git repository and keeps a local journal. If you turn on cloud sync, it sends the commit details needed for reports and sharing to your CommitDiary workspace.
No. Cloud reporting uses commit details, changed file names, change counts, and short code samples. Your full repository stays where it is.
Yes. Commit discovery and local storage work in the editor. Unsynced work can wait in a local queue until you reconnect.
Yes. Turn cloud sync off in the extension settings or run “CommitDiary: Remove API Key” whenever you want.
Stepper is the reliability layer behind AI reports. It handles provider routing, retries, rate limits, failover, validation, callbacks, and structured output.
No. CommitDiary summarizes engineering activity. It does not replace code review, tests, product context, or engineering judgment.
It is useful for solo developers, students, teams, maintainers, and anyone who needs to explain software work clearly—from daily updates to portfolio evidence.
Your work is already in Git
Install the VS Code extension and start your local journal with your next commit.