“Added monetization” 18 days ago.

I built TabVault, an open-source (AGPLv3) browser extension for Chrome, Firefox, and Chromium-based browsers designed around a simple rule: zero data loss when managing high-volume tabs.

Like many developers, I often end up with 40+ tabs open across multiple projects (docs, PRs, issue trackers). Most tab managers treat open tabs casually. If the browser crashes mid-save, the OS runs out of memory, or an update forces a restart, sessions often corrupt or disappear silently.

A few architectural details:

1. Two-Phase Atomic Staging: Before any open tabs are closed, the snapshot payload is written to an isolated staging buffer (tabvault_sessions_staging) and verified. Only after a successful write is the session committed to local storage. If the browser or machine dies mid-save, the previous database remains uncorrupted, and uncommitted tabs are recovered on the next startup.

2. 100% Offline & Zero Telemetry: No analytics, no tracking pixels, and no external CDNs or remote dependencies. The extension operates completely locally in Manifest V3.

3. Direct Cloud Backup: Optional automated backups go directly to your personal Google Drive via OAuth2. There are no middleman servers or third-party databases touching your browsing data.

4. Developer Portability: 1-click export to Markdown (organized by session & domain), Notion-ready hierarchical text, Netscape HTML Bookmarks, CSV, and OneTab format.

5. Native Browser Semantics: Tab items use native <a> anchors, preserving middle-click to open in background, native context menus ("Open link in new tab", "Copy link address"), and link dragging.

Links: - GitHub: https://github.com/jarvissing/tabvault - Chrome Web Store: https://chromewebstore.google.com/detail/fhmbeamnofaciafhdbi... - Firefox Add-ons: https://addons.mozilla.org/en-US/firefox/addon/tabvault-zero...

The project is licensed under GNU AGPLv3. I’d love to hear your feedback on the crash recovery mechanism, performance, or any edge cases you run into.