Co-founder of Marvellous Codeworks. Rescued The Great Suspender, built The Marvellous Suspender
When Chrome 149 introduced a regression that silently discarded suspended tabs inside tab groups on every browser restart, TMS shipped a workaround in version 8.1.4. When the same regression reached Microsoft Edge, we addressed that too. We knew from the start that these were stopgap measures — the right fix had to come from the browser itself.
It is now here. Chrome 150.0.7871.47 ships the browser-side patch for crbug.com/522338670. Tab groups restore correctly without any intervention from TMS. We have verified this with a clean restart session and multiple group configurations, and everything behaves as expected.
Here is what that means for TMS, and what we decided to do with the workaround code.
Co-founder of Marvellous Codeworks. Rescued The Great Suspender, built The Marvellous Suspender
TMS has been quietly getting better for years — new bugfixes, compatibility patches, a full Manifest V3 migration — but the extension's visual identity never kept up. The settings pages still looked like a relic of 2018. The popup was fine, but only barely. Nothing matched the Marvellous Codeworks website.
That changes with TMS 9.
This is the first in a series of posts we're calling Road to TMS 9 — a chance to show you what's being built on the feature branches before it ships, explain the decisions behind the changes, and hear from you before things are set in stone. Think of it as development in the open.
Co-founder of Marvellous Codeworks. Rescued The Great Suspender, built The Marvellous Suspender
If you are using Microsoft Edge and noticed that your suspended tabs inside tab groups disappear or turn into blank New Tab pages after a browser restart, you are running into the same Chromium-level regression that first appeared in Chrome 149 — and it is now reaching Edge users too.
Microsoft Edge is built on the Chromium engine, which means it inherits browser-level changes from the upstream Chromium project — including regressions. The change introduced around Chromium 149 that broke the tab group restore behavior for suspended tabs is now making its way into Edge builds.
As a result, Edge users are experiencing the same symptoms Chrome users saw earlier:
Suspended tabs inside tab groups are silently discarded when the browser restarts.
Tabs outside tab groups are not affected and restore correctly.
The suspended tab URL (chrome-extension://… / extension://…) is apparently filtered out during session restore when inside a group.
This is tracked in the dedicated GitHub issue #374, opened specifically for Edge. Issue #369 — the original Chrome report — has also been reopened because of these lingering effects across the Chromium ecosystem.
The browser-side Chromium fix is under review but has not yet landed in Chrome's stable channel — Chrome 149.0.7827.156 is still affected. The fix is expected sometime this weekend or early next week.
Edge will take even longer, as it follows its own release schedule on top of Chromium's.
TMS 8.1.4 addressed the issue for Chrome users at the extension level, but some edge cases are still being investigated (see #369).
TMS 8.1.5 is in active development and specifically targets the Edge regression. A fix has already been tested and looks solid — we expect a release candidate to be ready very soon.
We are not waiting for the browser vendors to ship their fix. We are shipping our own.
This is not TMS's fault
We want to be very clear: this regression was introduced by a change in the Chromium engine, not by anything TMS did. We are nonetheless doing everything we can to protect your tabs while the browser-side fix works its way through the release pipeline. We are sorry you are caught in the middle of this.
Co-founder of Marvellous Codeworks. Rescued The Great Suspender, built The Marvellous Suspender
info
2026-06-12
A companion extension — back-grouped-tabs — is now available as a temporary workaround while a proper fix for the Chrome bug is being developed. See the new section below for details.
2026-06-15
TMS 8.1.4 has been submitted to the Chrome Web Store and is currently pending review. This version includes a fix for the tab group restore issue.
The Chrome team is also working on an official browser-side fix: the patch is under review at chromium-review.googlesource.com. It's a race to see who gets there first!
2026-06-16
TMS 8.1.4 is now live on the Chrome Web Store. The tab group restore issue is fixed — update TMS and you are good to go.
The back-grouped-tabs companion workaround is no longer needed. The repository remains available for anyone who still wants it, but you can safely remove the extension.
If you are using Chrome 149 and noticed that your suspended tabs inside tab groups turn into blank New Tab pages after a browser restart, you are not alone — and it is not your fault.
Starting from Chrome 149, a change in the browser's tab group restore engine broke compatibility with suspended tabs managed by TMS. When Chrome restores a session after a restart, it now skips tabs whose URL does not start with https:// inside tab groups. Since TMS suspended tabs use an internal chrome-extension://… URL, they are silently discarded instead of being restored.
Tabs outside tab groups are not affected and restore correctly as before.
The issue was reported by users shortly after Chrome 149 rolled out and confirmed by the TMS team. A member of the Chrome development team has acknowledged the problem and filed an internal bug to investigate whether the behavior change was intentional or an unintended side effect.
TMS 8.1.4 is now available on the Chrome Web Store. It addresses the tab group restore issue directly — suspended tabs inside tab groups will no longer be discarded after a browser restart. Update TMS and the problem goes away.
The Chrome team also had an official fix under review on the browser side; TMS shipped the fix first.
We know how frustrating data loss is, and we are sorry you hit this. Thank you for your patience while we sort it out.
TMS 8.1.4 is out and fixes the issue natively. If you have updated TMS, you can safely remove the back-grouped-tabs companion extension. The repository remains available for anyone who still wants to use it.
While the proper fix was in the works, a small companion extension was made available: back-grouped-tabs.
It does one thing: when Chrome restores a session and discards suspended tabs inside tab groups, this extension detects the affected tabs and navigates them back so the suspended page reappears — automatically, without you having to click the Back button on each one.
To install it, clone or download the repository and load it as an unpacked extension in Chrome (chrome://extensions/ → enable Developer Mode → Load unpacked). The README covers everything you need to know.
Co-founder of Marvellous Codeworks. Rescued The Great Suspender, built The Marvellous Suspender
The Marvellous Suspender has been a fork since day one — born in 2021 out of The Great Suspender, at a time when that project had been pulled from the Chrome Web Store and flagged as malware. TMS cleaned up what needed cleaning and gave orphaned users somewhere to go. Fair enough, that's exactly what a fork is for.
But five years later, TMS isn't a patched-up copy of someone else's abandoned code anymore. It's had a full Manifest V3 rewrite, a proper visual redesign, its own contributors, and — as of a few months ago — a home under the Marvellous Codeworks name. The GitHub fork relationship, though, hadn't changed: technically, gioxx/MarvellousSuspender was still listed as a fork of the original repository, tied to its network, its issues, its history.
