Why I Built a Browser History Manager Instead of Another Tab Saver

ren boxue — Wed, 14 Oct 2026 00:55:39 +0000

I have a habit of keeping too many browser tabs open.

Not because I'm actively using all of them. I just worry that if I close a useful website, I might never find it again.

Bookmarks help when I know exactly what I want to save. But they don't solve the problem of websites I didn't realize would be useful until much later.

That made me rethink what a browser history manager should do.

The problem isn't always too many tabs

A tab manager can save a browsing session, remove duplicates, or restore closed tabs.

Those are useful features, but they don't completely solve my problem.

Sometimes I remember a website's purpose without remembering its name. Other times, I remember roughly when I visited it, or the project I was working on.

I wanted a way to find those websites again without having to remember their exact URLs.

A different way to organize history

I started building a browser extension called BestHistory around one idea:

Organize browsing history by website first, rather than showing an endless list of individual visits.

If I've opened 50 pages from the same website, I'd rather see the website as one recognizable place, with its individual pages available when I need them.

That became the foundation of the project.

I also added tags and personal notes. Sometimes my own description of a website is more useful than its official name.

For example, I might remember "that tool I used to convert a PDF" rather than the tool's actual name.

Keeping the timeline

I didn't want to lose the chronological view entirely.

Sometimes the most useful clue is time:

"I think I visited it last Tuesday afternoon."

So I kept a timeline view, with filtering and grouped browsing records.

The challenge was to make both views useful without simply rebuilding Chrome's default history page.

Experimenting with AI Recall

I later added an optional feature called AI Recall.

Instead of requiring an exact keyword, it lets users describe what they remember in natural language.

The AI helps turn that description into possible search clues, which are then used to search the local browsing history.

One design decision was important to me: I didn't want to upload a user's entire history database just to make the feature work.

The AI feature processes a limited set of relevant information when the user actively requests it, rather than continuously sending browsing history to the cloud.

A separate place for private history

Another challenge was dealing with browsing history that users might want to remember without keeping it in their ordinary history list.

I added an optional encrypted private mode to keep those records separate and locked when not in use.

This isn't intended to provide anonymity. It's a way to manage locally stored browsing history with an additional layer of privacy.

What I'm still trying to figure out

Building the extension was one challenge. Understanding how people actually manage their browsing history is another.

Some people rely entirely on bookmarks. Others keep hundreds of tabs open. Some use session managers, while others barely look at their history at all.

I'm still trying to understand where a website-based history manager is genuinely useful and where existing tools already do a better job.

I'd love to hear how other people handle this.

When you close a tab containing something useful, how confident are you that you'll be able to find it again a month later?