Skip to content
TabBoyTabBoy Help Center

Search is only available in production builds. Try building and previewing the site to test it out locally.

Collections in context

When a browser becomes a place to hold every unfinished thought, the problem is rarely the number of tabs alone. Work gets split between windows, useful links become hard to find again, and a reading list turns into another place to postpone decisions.

TabBoy’s direction is simple: make that context easier to see, keep the browser under your control, and be clear about what exists today.

A calmer view of browser work

Section titled “ A calmer view of browser work”

The repository’s market analysis describes a familiar pattern: people keep tabs open because closing them can feel like losing the information behind them. TabBoy starts with local scans, reviewable suggestions, and explicit approval for browser-changing actions.

The broader collections experience is being built in small, verifiable steps:

  • Related collections will connect windows that appear to belong to the same piece of work, as a focused list rather than an opaque graph. See #72.
  • The reading queue will give saved pages a visible status and, later, a local extractive summary. See #74.
  • Bookmark organization will help group Chrome bookmarks by theme. See #73.
  • Optional AI summaries are a separate, opt-in TabBoy Pro direction using your provider choice. See #75.

These are planned surfaces, not current product claims.

What is available now

Section titled “ What is available now”

The current V1 boundary remains local and deliberate. TabBoy can scan Chrome windows, tabs, and groups; evaluate validated rules; show suggestions; and apply only the actions you approve. It also supports local saved groups and collections for recovery workflows.

The four capabilities described above are not presented as available here while #72, #73, #74, and #75 remain open.

Boundaries that stay visible

Section titled “ Boundaries that stay visible”
  • No account, hosted backend, telemetry, or AI is required for V1.
  • Tab data is processed locally in the extension’s current product path.
  • TabBoy does not close, delete, or save browser state without a clear user approval step.
  • Future content reading and remote summaries require separate, explicit permission and disclosure. A planned feature will not silently expand the current permission boundary.

When these issues ship, this page will be updated alongside the implementation and its privacy and manual-test documentation.