Tab Triage & Stash

Too many tabs open? Tab Triage & Stash tells you which ones to close first — then closes them for you, without losing anything. Instead of squinting at a wall of identical favicons, Tab Triage scans every open tab and sorts it into Close First, Review, or Keep, using both what the site is (streaming, social feeds, AI chat, dashboards, docs) and what it's actually doing right now (playing audio, sitting idle, already asleep, pinned). One click on a row jumps you straight to that tab; check a batch of rows and close or stash them together. Don't want to lose a tab, just get it out of your way? Stash it. Selected tabs are saved into a "🗂 Stashed Tabs" bookmark folder — name the stash yourself, or let it timestamp automatically — and the tabs close, freeing up memory immediately. Reopen the whole stash with one click, any time, from the report or the toolbar popup. Made a mistake? Undo brings back your last close or stash instantly. Features 🔍 Smart triage report — every open tab ranked into Close First / Review / Keep, with the reasoning visible 🗂 Stash, don't lose — bulk-save tabs to a named bookmark folder and restore later with one click ↩️ Undo — reverse your last close or stash action ⌨️ Keyboard shortcut — Cmd/Ctrl+Shift+E opens the full report ⚙️ Custom rules — add host-to-category rules from the options page, applied live 📊 Optional measured memory — real per-process RAM on Chrome Dev channel 🔒 Fully local — no server, no network requests, no analytics Why it's useful: Tab hoarding quietly eats RAM and productivity. Most tabs you'll never revisit, but you're not ready to just lose them either. Tab Triage gives you a fast, opinionated starting point on what's actually costing you something right now, and Stash makes "close it" reversible so you never have to keep a tab open "just in case." Privacy: No backend, no network requests, no analytics — everything stays in your Chrome profile. Permissions: Tabs (score/close/reopen), Bookmarks (stash folder), Storage (custom rules + undo buffer), Processes (optional, Dev-channel measured memory only). No host permissions, no content scripts. One thing worth fixing before you actually publish: PRIVACY.md:41 still has a placeholder [add a contact email or issue tracker URL here] — the Chrome Web Store requires a real contact method in the privacy policy, so that'll need to be filled in.