BusyTab

Why it exists

Running several client projects at once means a window per project, and inside each one a tab for everything that project made you go and read. Then another window. Then the research for that. The count stops being a number anybody looks at.

The browser has one answer of its own, which is to close things one at a time, and that is not an answer at this scale. But the reason nobody does it is not laziness. Closing a tab feels like losing whatever was on it, and there is no undo worth trusting.

So the problem was never really the tabs. It was that closing had no safety net, and without one you keep everything.

What we decided

• Archived before closed, always

  Every close is written down before it happens, and any batch can be brought back whole. That is the decision the rest of the tool rests on: once closing is genuinely reversible, closing in bulk stops being frightening.

• Select the pile, not the tab

  One checkbox takes all one hundred and sixteen tabs from a single site while the other five hundred stay exactly where they are. Duplicates and parked homepages get counted and cleared the same way.

• Triage you can put down

  Keep and Snooze decisions survive a restart, so the pile can be worked in ten minute bursts across a week without ever re-deciding the same tab twice.