I built DevChronicles because I was tired of losing hours of work to forgotten commits. How many times have you coded for hours, only to realize you haven’t committed anything? Or worse—your machine crashes and you lose everything since your last manual commit?
Chronicles solves this by automatically tracking your coding journey with intelligent commit reminders and auto-commits.
<h2>What DevChronicles Does</h2>
DevChronicles is a VSCode extension that automatically commits your code based on your workflow:
<ul>
<li>Auto-commit on file save — Every time you save, your progress is safely stored</li>
<li>Auto-commit on idle — Configurable 2-5 minute intervals catch those “thinking breaks”</li>
<li>Smart file detection — Only tracks relevant files (.js, .ts, .jsx, .tsx, .css, .scss, .html)</li>
<li>Auto-generated commit messages — No more “fix stuff” commits</li>
<li>Session tracking — See exactly how many files and commits you’ve made</li>
</ul>
<h2>Why This Matters</h2>
As developers, we’re often in flow state where stopping to commit feels disruptive. But losing work is devastating. DevChronicles runs silently in the background, creating a safety net without breaking your concentration.
The extension respects your workflow:
<ul>
<li>Only works in git repositories</li>
<li>Pause/resume when needed</li>
<li>Configurable file types and timing</li>
<li>Manual commit commands when you need them</li>
</ul>
<h2>Getting Started</h2>
<ol>
<li>Install from VSCode Marketplace: Search “DevChronicles”</li>
<li>Configure in settings.json or command palette</li>
<li>Start coding — DevChronicles handles the rest</li>
</ol>
<pre><code class="language-json">&quot;chronicle&quot;: {
 &quot;autoCommit&quot;: true,
 &quot;autoPush&quot;: true,
 &quot;idleMinutes&quot;: 2,
 &quot;fileExtensions&quot;: [&quot;.js&quot;, &quot;.ts&quot;, &quot;.jsx&quot;, &quot;.tsx&quot;, &quot;.css&quot;, &quot;.scss&quot;, &quot;.html&quot;],
 &quot;showNotifications&quot;: true
}
</code></pre>
DevChronicles has already saved countless hours of work for developers who’ve adopted it. It’s particularly valuable for:
<ul>
<li>Long coding sessions</li>
<li>Experimental features</li>
<li>Learning new technologies</li>
<li>Pair programming sessions</li>
</ul>
The peace of mind knowing your progress is always saved lets you focus on what matters: building great software.
🔗 VSCode Marketplace: Search “DevChronicles” 
📄 License: ISC 
🐙 Github: <a href="https://github.com/MatthewTheCoder1218/chronicle" target="_blank" rel="noopener nofollow">https://github.com/MatthewTheCoder1218/chronicle</a>
Built for developers who value their time and sanity. Feedback and contributions welcome!
— Made with ❤️ by Little Prince

Crafting the future of the web, one line of code at a time 💻✨. A place to share tips, tools, and tech for developers who love building the web 🌐🚀. Let’s make the web better, together! 👩‍💻

WebCraft

DevChronicles is a VSCode extension that automatically commits code changes to prevent work loss. It features auto-commits on file save and during idle periods, smart file detection for relevant code files, auto-generated commit messages, and configurable settings. The tool runs silently in the background to maintain developer flow while creating a safety net for code progress.

Chronicles: Never Lose Code Progress Again with Smart Auto-Commits

<blockquote>
your machine crashes and you lose everything since your last manual commit
</blockquote>
Absolutely ridicules scenario. Nobody works on unsaved files for hours.
You write some code, save and test it. it’s a very tight cycle.
<hr>
<blockquote>
How many times have you coded for hours, only to realize you haven’t committed anything?
</blockquote>
It is sometimes intentional to work for a long time without committing because things aren’t “stable” yet for various reasons.
When you know a specific file or group of files are done and no changes will be needed in regards to the current task, then you can commit those, or choose to commit them later (but you have to know you will remember the reason for the changes to write a good commit message).
Anyway, I believe there is no need at all for this thing

Odd. I do not see this extension anywhere. Am I alone?