Groups not synced across new windows — new windows always default to Ungrouped

Resolved 💬 1 comment Opened May 22, 2026 by JimboKY Closed Jun 21, 2026

Summary

When you have custom groups set up in one Claude Code window (e.g. Content, Planning, Clients), opening a new window does not show those groups. The new window always defaults to showing all conversations under Ungrouped with no named groups visible.

Expected behaviour

Groups created in any window should be part of the account state and visible in all windows opened by the same logged-in user — the same way conversation history syncs across windows.

Actual behaviour

New windows show only a flat "Ungrouped" section. The named groups (and any conversation assignments to those groups) do not appear. The only way to restore them is to manually recreate every group and reassign every conversation in the new window — which is lost again the next time a new window is opened.

Steps to reproduce

  1. In an existing Claude Code window, create two or more named groups (e.g. via right-click → Move to group → New group…)
  2. Assign several conversations to those groups
  3. Open a new Claude Code window (File → New Window, or ⌘N)
  4. Observe: the new window shows only "Ungrouped" — no named groups visible

Environment

  • Claude Code version: v1.8555.0
  • Platform: macOS (Claude Desktop app)
  • Account: logged in (same account across both windows)

Impact

High — groups are a core organisational feature. If they don't persist across windows, they're effectively unusable for anyone who works with multiple windows (a common workflow). Users are forced to choose between maintaining one window forever or losing all organisation.

Request

Groups and conversation group assignments should sync as part of account state, so any new window immediately reflects the user's existing organisation structure.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗