Roundup — Automatically Group Your Tabs

Every tab in its place. Group tabs by your own rules or built-in categories — no server, no account, no analytics.

Roundup sorts the tabs in a window into Chrome tab groups — in one click, or with a keyboard shortcut. WHAT MAKES IT DIFFERENT Most tab organisers handle well-known sites and fall apart on everything else: a shop on a vanity domain, someone's tutorial blog, a streaming service that launched last month. Roundup works those out from the shape of the address, remembers what it decided, and lets you correct it in one dropdown when it guesses wrong. YOUR RULES COME FIRST Write rules as a regular expression, a wildcard pattern, or a plain domain. They are matched against the whole address, not just the hostname — so two products sharing one host end up in different groups. Jira and Confluence both live on your-team.atlassian.net, and Roundup can still split them: Jira ^https://[^/]+\.atlassian\.net/(jira|browse|secure)/ Confluence ^https://[^/]+\.atlassian\.net/wiki/ A live tester shows you exactly which rule claims a URL and where it would land, before anything touches your tabs. THE NAME YOU GIVE A GROUP IS THE NAME IT KEEPS Rename a group and Roundup follows that group by identity, not by title. Re-run it as often as you like — your names survive, and new matching tabs join the group you renamed instead of spawning a duplicate. IT TELLS YOU WHY IT DID NOTHING If a run moves no tabs, Roundup says which rule held them back — tabs already in groups you named, a group you locked, too few tabs to bother — and offers the one control that unblocks it. No silent no-ops. ALSO - Undo the last grouping (Alt+Shift+Z) - Lock a group so Roundup never touches it - Collapse new groups to keep the tab strip short - Choose what happens to unmatched tabs: category, domain, or leave them alone - Works entirely offline PRIVACY No server. No account. No analytics. No remote code. No host permissions and no content scripts — Roundup never runs code on the pages you visit, and it makes no network requests at all. Your rules sync through your own Google account via Chrome's built-in storage sync, and nothing else leaves the device. The source is public and the build refuses to ship if fetch, XMLHttpRequest, WebSocket or sendBeacon ever appear in the bundle: https://github.com/rishavsharma9802/roundup