What changes when the browser is organised around what you're working on, instead of around a row of tabs you're trying not to lose.
The first thing you notice is that closing a page stops feeling risky. When everything you read is captured to a searchable library anyway, a page list can stay short without anxiety — you're not throwing anything away, just clearing your desk.
The second is that idle pages sleeping in the background is invisible until you want it: the memory comes back, and the page you left reloads in a blink when you click it. The trade is a short reload on return, paid only for pages you'd stopped looking at.
▌ highlighted by you · 32m ago
Closing a page stops feeling risky when everything you read is captured to a searchable library anyway.
Select that line and press ⌘⇧H and it lands in Stuff with a backlink to this exact passage — drag it onto the Canvas later and it arrives as an attributed quote.
Project-based browsing makes closing pages low-stakes because everything read is captured to a searchable library. Background pages sleep to reclaim memory, reloading on click — the only cost a brief reload on return.
{mode === "tabs" ? "Two open pages cover fingerprinting: privacytests.org (defenses compared) and the Mozilla research note. Both argue randomisation beats blocking." : "Across the two snippets: your own read is that capture-by-default is what makes a short page list workable — the library, not the tab strip, is the safety net."}