Product Vision

A really helpful, but  classic "Power User" friction point is tabs "jumping" across screens to join a Tab Group in another window—is technically impressive but can be UX-hostile, especially for users with multi-monitor setups who are trying to compare documents side-by-side.

We want to introduce "Window Isolation" fucntions to give more control over this function.

Product Roadmap Item: Smart Window Isolation

1. The Problem (The "Why") Currently, Tabomatic uses a "Global Magnet" strategy. If a rule exists, it searches the entire browser instance for a matching group. If "Project X" is open on Monitor 1, and you open a "Project X" reference link on Monitor 2, the tab vanishes from Monitor 2 and snaps to Monitor 1. This breaks context for split-screen workflows.

2. We will introduce a "Grouping Scope" setting that lets the user define how aggressive the grouping logic should be.

Proposed Approach: "Local-First" Logic Instead of a complex per-rule setting, simply change the core search order in your code to prioritize the current window.

• Current Logic: Find Group (Any Window) → Move Tab.

• New Logic: Find Group (Current Window) → Move Tab.

  • Else: Create New Group (Current Window).

Other options include :
a) Allowing Per Rule logic settings, which while ads total control  it does also make this very complex.
b) Perhaps trigger a small pop-up modal to allow real time control over this per window, so you can choose if you want to consolodate back to one window or not.

Get in touch if you have other great ideas, or feed back. 

⚡ Feature: Advanced Regex Support

Unlock infinite flexibility. Go beyond simple keywords and use standard Regular Expressions to target complex URL patterns. Whether you need to group specific ticket numbers (e.g., JIRA-[0-9]+), dynamic subdomains, or specific file types, Regex gives you precise control to capture exactly the tabs you want, and nothing else.

Power User" scenarios where Regex outperforms standard keywords:

1. The "Project Isolation" Workflow

• Problem: You use Jira (or Linear/Asana) for multiple client projects. A simple "jira" keyword lumps everything into one messy group.

• Regex Solution: Create rules that target specific project codes in the URL.

  • browse\/PROJ-A-\d+ → Red Group (Project A Tickets)

  • browse\/PROJ-B-\d+ → Blue Group (Project B Tickets)

• Result: Your tickets separate themselves by client automatically.

2. The Full-Stack Developer (Port Splitting)

• Problem: You have 10 tabs open for localhost, but you can't tell which is your frontend, backend, or documentation server.

• Regex Solution: Group by port number.

  • localhost:3000 → Green (React App)

  • localhost:8080 → Purple (API / Backend)

• Result: Frontend and Backend environments stay strictly separated.

3. The "Reading List" Collector

• Problem: You are researching a topic and have opened PDFs from 15 different domains.

• Regex Solution: Match the file extension at the end of a URL.

  • \.pdf$ → Yellow (Reference Docs)

• Result: Any PDF, from any website, snaps into a single "Reading" group.

4. The "Omni-Search" Group

• Problem: You are searching across Google, Bing, and DuckDuckGo simultaneously.

• Regex Solution: Match the search parameter pattern common to search engines.

  • search\?q= → Grey (Search Results)

• Result: All your active search pages group together, keeping them separate from the actual articles you click on.

New Native Split View (experimental flag #side-by-side), which allows two tabs to merge into a single view within the same window.

The Challenge: Because this feature is still experimental/new, Google has not yet released an Extension API to control it. Currently, extensions can open new windows or side panels, but they cannot programmatically command Chrome to "merge Tab A and Tab B into a Split View".

However, we have this on the roadmap as a "Future/Pending API" feature, to implement it as soon as Google opens the door.