OpenTabs.

Your open tabs, grouped, on every new tab.

Most new tab pages show you a grid of links you already have bookmarked. OpenTabs shows you the twenty-six tabs you actually have open — grouped by site, sorted by what you touched last, closable from the page — above a briefing you assemble yourself.

Get the extension Browse packs Free. No account. MIT-licensed.

It paints before you perceive it

A new tab opens thirty to a hundred times a day. Anything that makes it hesitate is felt every one of those times, so nothing interesting is allowed on the critical path. 

chrome.alarms ─► service worker ─► fetch → rank (Rust/wasm)
                                        │
                               render-ready JSON
                                        │
                                        ▼
                                chrome.storage.local
                                        │
          new tab opens ─────────────►  read once, paint. done.

All the work happens where nobody is waiting. The page itself ships about 4 KB gzipped, loads no WebAssembly, and makes no network request when it opens — a budget the test suite enforces, so it stays true as the product grows.

What goes above the tabs is yours

Every group is optional, reorderable, and off until you turn it on.

Topics

Any subject you can name, from RSS, Hacker News, arXiv, Reddit or an X search — deduplicated across sources and ranked, not concatenated.

Markets

Crypto and equities, at the interval you choose.

Weather

From coordinates you set. No location permission, no IP lookup.

Focus

A to-do list with sub-tasks, reordering, and items that clear themselves six hours after you tick them.

Calendar

A read-only ICS address. Real recurrence handling, not a naive expansion.

Tabs management

Grouped by site, duplicates closable in one press, stale New Tab pages closed on a schedule you set.

Nothing about you is stored anywhere but your browser

Not a policy — an architecture, and one that can be checked.

No account to use it

Your configuration lives in your own browser profile. There is no server holding it, so there is no server to breach, subpoena or shut down.

Permissions asked when needed

A group you never enable never asks for a site, and never makes a request. The install prompt is not where you agree to everything up front.

Anonymous by construction

Signing in — optional, and only to publish or like a pack — stores a one-way digest. The marketplace database has no column that could answer "what has this account liked".

Install

Chrome 121 or later, Edge, or Firefox. Not in the stores yet — this is the build itself, and it is the same bytes that will go to them.

  1. Download the latest build from the releases page and unzip it — opentabs-chromium for Chrome and Edge, opentabs-firefox for Firefox.
  2. Load it. On Chrome or Edge open chrome://extensions (or edge://extensions), turn on Developer mode, press Load unpacked and pick the unzipped folder. On Firefox open about:debugging#/runtime/this-firefox, press Load Temporary Add-on and pick any file inside the folder.
  3. Open a new tab. Your open tabs are already grouped. That part needs no configuration at all.
  4. Add what you want above them in Settings — or install a ready-made pack from the marketplace and start from someone else's hour of work.

Prefer to build it yourself? cargo test --workspace then npm ci && npm run build in apps/extension. The source is MIT.

Questions

Does it need an account?
No. OpenTabs works completely without one and your settings never leave your browser profile. Signing in is optional and buys exactly two things: publishing a pack to the marketplace, and liking one.
What does it send anywhere?
Only the requests needed to fill the groups you turned on. There is no analytics and no telemetry. A group you did not enable makes no request at all.
Why does it want Chrome 121?
That is the version that reports when each tab was last used. Without it, "sort by what you touched last" and "close the New Tab pages you abandoned" both become guesses.
What is a pack?
One group's configuration — its sources, its query, its layout — as a document you can hand to someone. Your API keys, calendar addresses and coordinates are stripped out before it leaves your browser. You can publish one to the marketplace or just send the file to a colleague; the second needs no account.
Is it open source?
Yes, MIT. The grouping, ranking, parsing and date handling are a Rust library compiled to WebAssembly; the extension itself is vanilla TypeScript with no framework.