A decade of bookmarks, finally useful

The folder you never open

Everybody has one: hundreds of saved links, filed under names that made sense at the time, a good third of them pointing at pages that no longer exist. The bookmark bar is a graveyard of intentions, and the reason is not laziness — it is that saving is cheap and retrieving is expensive.

So the pile grows, and the part of it you could actually use stays invisible.

Import once, and let them be read

Bring your bookmarks into a project and three things happen. They are grouped by subject rather than by whichever folder you happened to be standing in when you saved them. The ones that no longer resolve are flagged, so dead weight becomes visible instead of quietly padding the count. And the survivors are attached to the project that needs them.

That last step is the one that changes what they are. Inside a project a link stops being a shortcut and becomes a source — something the assistant can open, read, quote and cite when you ask a question the saved page happens to answer.

Your bookmarks stay your bookmarks

Each project also gets a real folder in Chrome’s own bookmark manager. The links remain ordinary Chrome bookmarks: they keep working with the extension uninstalled, and deleting a project unlinks the folder without deleting anything inside it.

Nothing is read in the background. The import runs when you start it from the panel, never on install, and never on a schedule.

What it is actually good for

Saving is cheap. Finding is not.

The point of importing is not tidiness. It is that a link nobody can find is worth exactly as much as a link nobody saved — and the moment those pages become readable sources inside a project, ten years of collecting finally pays something back.

Where to start

Pick one subject you have been quietly collecting for years. Make a project for it, import, and ask what is actually in there. The first answer almost always contains at least one page you had forgotten and needed this week.