Claude-in-Chrome leaves a persistent "Claude" saved tab group per session; they accumulate on the bookmarks bar and can't be cleaned up automatically

Summary

Each browser-automation session creates a Chrome tab group named "Claude". Because Chromium auto-saves tab groups, every session leaves a persistent "Claude" saved-tab-group chip on the bookmarks bar. These survive browser restarts (by design of saved groups), so they accumulate one-per-session with no built-in cleanup. After a handful of sessions the bookmarks bar fills with duplicate "Claude" chips.

Environment

• Claude Code 2.1.216
• Claude-in-Chrome extension 1.0.81 (id fcoeoabgfenejglbffodgkkbkcdhcgfn)
• Chromium 150.0.7871.124
• Linux Mint 21.3

Steps to reproduce

1. Use Claude Code's browser automation (tabs_context_mcp / tabs_create_mcp) so the extension creates its "Claude" tab group.
2. End the session / close the browser.
3. Repeat across a few separate conversations (or relaunches).
4. Observe the bookmarks bar.

Expected

At most one "Claude" saved group, or the session's group cleaned up when the session ends — no unbounded accumulation.

Actual

A new "Claude" saved-tab-group chip is left on the bookmarks bar per session. They persist across restarts and pile up (observed 3 after a few sessions). Nothing in the normal flow removes them.

Impact / notes

• Closing the browser does not remove them (they are saved groups, persistent by design) — gracefully or via kill makes no difference.
• There is no MCP tool to delete/ungroup a tab group, so the assistant can't clean up after itself. The MCP tools only see page content, not the bookmarks bar, so they also can't click the chips.
• Manual cleanup (right-click chip → "Delete group") works but is easy to overlook and grows tedious with repeated use.

Possible fixes

• Have the extension delete/ungroup its "Claude" group when the automation session ends (or opt its groups out of Chrome's "save group" behavior).
• Reuse a single persistent "Claude" group across sessions instead of creating a new one each time.
• Expose an MCP "delete/ungroup" capability so the assistant can clean up.

Separate, minor observation

When the browser is closed uncleanly (e.g. pkill), Chromium's crash recovery restores the previous automation window on next launch (profile.exit_type=Crashed) even with session-restore set to a fixed start page. Distinct from the saved-group issue above, but related to leftover state from automation sessions.

<img width="1920" height="1200" alt="Image" src="https://github.com/user-attachments/assets/ab4b9929-f9a6-47f0-9e16-faf78e3b2000" />