---
name: tab-management
description: Use when someone has dozens of browser tabs open, loses things in them, or wants a routine for keeping tabs under control with sessions, a save-for-later place, a tab limit, and an end-of-day close. Distinct from [[focus-blocker]] (blocks sites rather than organizing tabs), [[reading-capture]] (processes what was read), and [[inbox-cleanup]] (the same clutter problem for email).
---

# Tab Management

Open tabs act as a to-do list, a reading list, and a memory aid at the
same time, and none of them well. Tab management gives each purpose a
proper home so the browser can be closed without anxiety. This skill
designs a small system: sessions for work in progress, a place for
things to read later, a soft limit, and a daily close.

## Input required

- **Browsers and devices** in use, and whether tabs sync between them.
- **Why tabs pile up**: research, things to read, tasks, fear of losing
  a page, or no habit of closing.
- **Current count**, roughly, and what the oldest ones are.
- **Typical work contexts**, such as projects, clients, courses, or
  hobbies.
- **Available features**: tab groups, workspaces, vertical tabs, session
  saving, bookmarks, a reading list, or extensions.

## Questions to ask first

Ask in **one batch of at most five questions**, skipping any already
answered:

1. Which browser or browsers do you use, on which devices?
2. Roughly how many tabs are open now, and what are most of them for?
3. What makes you keep a tab open instead of closing it?
4. What are the two or three separate contexts you switch between?
5. Do you already use bookmarks, a reading list, or a notes app?

## Method

1. **Triage the current pile once.** For each tab, pick one: close it,
   do it now if under two minutes, save it for later, or keep it in a
   session. Be quick; tabs unopened for weeks are usually candidates to
   close, since a search can find the page again.
2. **Create sessions by context.** Use tab groups, workspaces, or
   separate windows named for each project or role. Each group holds only
   what that context needs right now. Save a session, then close it when
   the context is paused, and reopen it later.
3. **Build one save-for-later place.** Choose a single destination for
   things to read, such as a reading-list feature, a bookmarks folder, or
   a notes page. One place beats several. Add a date and a short note on
   why the page matters.
4. **Set a tab limit.** Pick a soft ceiling that fits the screen and the
   user, such as the number visible without scrolling the tab bar. This
   is a default to adjust, not a rule of nature. When the limit is hit,
   sort before opening the next tab.
5. **Add a close ritual.** At end of day, spend a few minutes: close what
   is finished, move leftovers to the save-for-later place, and save the
   session for tomorrow. Start the next day from a short, deliberate list.
6. **Review the save-for-later list weekly.** Read, act, or delete.
   Anything skipped through several reviews gets deleted; a list that
   only grows becomes a second pile of tabs.
7. **Reduce the tab-opening urge.** Where possible, open links in the
   current tab, search again rather than keep a page "just in case", and
   write the question you are researching somewhere visible.

## Output format

- **Triage rules** the user can apply in one pass.
- **Session map:** context, group name, what belongs in it.
- **Save-for-later setup:** where, what to record, review day.
- **Tab limit** with the rule for hitting it.
- **End-of-day checklist** in five lines or fewer.
- **Weekly review step.**

## Ground rules

- **Do not close tabs without the user's say.** Guide the triage; the
  user decides. Warn that tabs may hold unsaved forms or logged-in work.
- **Keep it browser-neutral.** Features and names differ; describe the
  capability and have the user find it in their own browser.
- **Treat tab content as private.** Never ask the user to paste URLs
  containing tokens, passwords, or account identifiers.
- **Start small.** One session and one list is better than a complete
  system that is never used.
- **Tools are examples only**, not endorsements.

## Self-check before answering

- Does every kind of tab have a defined home?
- Is there exactly one save-for-later place?
- Is the limit stated as an adjustable default?
- Is the end-of-day close short enough to survive a busy day?
- Is there a weekly review that deletes things?

## Common pitfalls

- **Bookmarking as hoarding** — saving a hundred pages and opening none.
- **Several save-for-later places** — nothing is findable.
- **No limit** — the pile returns within days.
- **Sessions never reopened** — saved work is forgotten; add a note on
  where to restart.
- **Too many groups** — more categories than the user will keep up.
- **Tabs as reminders** — a task belongs on a task list, not in a tab.

## Example prompt

> I always have around eighty tabs open across two windows and I'm afraid
> to close any. Help me triage them, set up sessions for my three
> projects, pick one place for read-later links, and build a five-minute
> end-of-day close.

## Learn more

- [[focus-blocker]] for blocking the sites that keep spawning new tabs.
- [[reading-capture]] for turning saved reading into notes.
- [[inbox-cleanup]] for the same approach applied to email.
- [[ai-note-system]] for keeping the notes where saved items end up.