You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/web
Steps to reproduce
Open T3.code with multiple machines configured.
Send chats with no project on multiple devices (might be optional).
Go to settings and see that the "No project" project is listed multiple times, not grouped as one project on multiple machines.
Example: (Machine names redacted.)
Expected behavior
These "No project" scratch projects should share one logical group key, not a key from their path which varies by machine. This lets them group together.
Reproduced on the macOS desktop app 0.1.3-nightly.20261027.3754 with four connected environments (three macOS, one Linux/WSL). Each environment has its own scratch project (<T3 home>/scratch), so their workspace roots differ per machine.
What I found in the bundled client (logicalProject-*.js):
The grouping function only collapses scratch projects into the shared "\0no-project" key when the caller passes groupScratchProjects: true:
Otherwise the key falls back to environmentId:workspaceRoot, because scratch projects have no repositoryIdentity. That makes every machine's "No project" a separate group.
Only the sidebar calls the grouping with groupScratchProjects: true. The settings project list (settingsLayout-*.js) and the other grouping calls in _chat-*.js and main-*.js omit it. So those views show one "No project" per environment.
Possible fix: pass groupScratchProjects: true in the settings list too, or make it the default for views that list projects.
Note: #26000 asks for the opposite in the new-thread picker and the command palette: one "No project" row per environment, labeled with its machine, so the user can choose where to run. If that is the intended design for the picker, the fix for this issue should cover settings (and other listing views) only, not the picker.
🤖 Claude Opus 5.5 responding on behalf of bradenbiz
Still happens on desktop 0.1.11-nightly.20261118.4890 (macOS arm64), with three environments connected: this Mac and two Linux servers. Settings → Projects lists three "No project" rows, one per machine, while the sidebar shows a single grouped "No project".
Same cause as described above, at tag v0.1.11-nightly.20261118.4890: useSidebarProjectGroups.ts passes groupScratchProjects: true, but apps/web/src/components/settings/useSettingsProjectGroups.ts calls buildSidebarProjectSnapshots without it, so each machine's scratch project keeps its own environmentId:workspaceRoot key. main still omits the flag.
#25777 fixes this, but it currently has merge conflicts with main and no review yet.
Found during a T3 Code triage session (Claude Code, Claude Opus 5.5).
Activity
Birzool commentedon Oct 27, 2026
Reproduced on the macOS desktop app
0.1.3-nightly.20261027.3754with four connected environments (three macOS, one Linux/WSL). Each environment has its own scratch project (<T3 home>/scratch), so their workspace roots differ per machine.What I found in the bundled client (
logicalProject-*.js):"\0no-project"key when the caller passesgroupScratchProjects: true:environmentId:workspaceRoot, because scratch projects have norepositoryIdentity. That makes every machine's "No project" a separate group.groupScratchProjects: true. The settings project list (settingsLayout-*.js) and the other grouping calls in_chat-*.jsandmain-*.jsomit it. So those views show one "No project" per environment.Possible fix: pass
groupScratchProjects: truein the settings list too, or make it the default for views that list projects.Note: #26000 asks for the opposite in the new-thread picker and the command palette: one "No project" row per environment, labeled with its machine, so the user can choose where to run. If that is the intended design for the picker, the fix for this issue should cover settings (and other listing views) only, not the picker.
bradenbiz commentedon Nov 19, 2026
Note
🤖 Claude Opus 5.5 responding on behalf of bradenbiz
Still happens on desktop
0.1.11-nightly.20261118.4890(macOS arm64), with three environments connected: this Mac and two Linux servers. Settings → Projects lists three "No project" rows, one per machine, while the sidebar shows a single grouped "No project".Same cause as described above, at tag
v0.1.11-nightly.20261118.4890:useSidebarProjectGroups.tspassesgroupScratchProjects: true, butapps/web/src/components/settings/useSettingsProjectGroups.tscallsbuildSidebarProjectSnapshotswithout it, so each machine's scratch project keeps its ownenvironmentId:workspaceRootkey.mainstill omits the flag.#25777 fixes this, but it currently has merge conflicts with
mainand no review yet.Found during a T3 Code triage session (Claude Code, Claude Opus 5.5).