Bug: Close Other Tabs+ ignores port and closes all localhost tabs

[Henno Täht]

Hello,

I use Claude Code and Opencode to orchestrate many agents. They work on the same project, but each runs in a separate instance on a different localhost port.

My app also has an “open in new tab” feature, so after working for a while I often end up with a large number of tabs that all have the same icon. It starts to look like sites such as AliExpress or Booking.com, where many tabs become hard to distinguish.

Because of that, I wanted to use Close Other Tabs+ to close only the extra tabs belonging to the same instance. However, the extension currently closes all localhost tabs regardless of port.

For example:

* main instance: `localhost:8010`
* secondary instance: `localhost:8110`

What I need is for the extension to treat these as separate instances and close only tabs from the same port as the current tab.

I tested both the “same domain” and “same hostname” options, but in both cases the extension still treats all localhost ports as the same group.

Would it be possible to make port part of the matching logic, or add an option that distinguishes tabs by hostname + port?

Thank you.

Stronger version, if you want it to sound more like a bug report:

Hello,

I would like to report an issue with Close Other Tabs+ when working with multiple localhost instances.

I use Claude Code and Opencode to orchestrate many agents on the same project, with different app instances running on different ports. My app also has an “open in new tab” feature, so over time I accumulate many tabs with the same favicon.

In this setup, I need “Close Other Tabs” behavior to affect only tabs belonging to the same localhost instance. Instead, the extension closes all localhost tabs regardless of port.

Example:

* `localhost:8010` = main instance
* `localhost:8110` = secondary instance

Expected behavior:
When I trigger “Close Other Tabs” on a tab from `localhost:8010`, it should close only other tabs from `localhost:8010`, not tabs from `localhost:8110`.

Actual behavior:
The extension treats all localhost tabs as the same site and closes tabs from both ports.

I tested both “same domain” and “same hostname,” but neither option distinguishes between localhost ports.

Please consider adding matching by hostname + port, or an option to include port in the comparison.

Thank you.

[Browservery Support]

I'll do it.

[Browservery Support]

Done! You can now filter by port. Please update to v1.5.1.  1.5.1 1.5.1