TabLedger — Iteration 3 (Now It Actually Feels Usable)

A few weeks ago I wrote about building a tiny Chrome extension because I was drowning in tabs and did what devs do best — built a tool instead of fixing the habit.

Since then, I’ve been using it daily.

And as expected, the real improvements didn’t come while building it — they came while using it.

v0.0.3 is now out, and this version is less about “saving tabs” and more about actually managing them properly.

What changed in v0.0.3?

1. Proper Snapshot Management Saved sessions now have a structured dashboard instead of just being dumped in a list. It feels like something you can actually work with.

1. Search Across Snapshots You can search by snapshot name or even URL keywords. This was a big one. If you save often, scrolling doesn’t scale.

1. Domain Filtering (with quick chips) Filtering by domain makes it much easier to find context-specific work. If I was researching one tool across multiple sessions, I can now isolate that quickly.

1. Safer Save & Close Pinned tab protection + confirmation flows. No accidental nuking of important tabs.

There are smaller UX refinements too — rename snapshots, copy individual links, safer deletes — but the main goal was reducing friction.

Still:

No accounts

No cloud sync

No tracking
Everything stays local in your browser.

It’s still intentionally simple.
But now it feels stable enough to actually rely on.

Repo:
https://github.com/mohitgauniyal/tabledger

Would love to hear how others manage tab overload — I’m already thinking about what v0.0.4 should look like.