claude-code - 💡(How to fix) Fix [BUG] Subject: Claude Desktop groups sessions from different services under the wrong project [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55034Fetched 2026-05-01 05:47:58
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Hi Anthropic team,

I'm experiencing an issue with Claude Desktop where sessions created for one service are incorrectly grouped under a different project in the left sidebar.

Environment:

Claude Desktop (latest version) Windows 11 Working directory: C:\Personale\Develop\Pmc\pmc2-dev-env\services\pmc2-blue-stay-service Steps to reproduce:

Open Claude Desktop Click "New session" Select the folder pmc2-blue-stay-service as the working directory Start working in the session Expected behavior: The new session should appear in the sidebar under a project named pmc2-blue-stay-service.

Actual behavior: The session is incorrectly grouped under pmc2-customer-care-service in the sidebar, even though the working directory is a completely different service (pmc2-blue-stay-service).

Both services are located under the same parent directory (pmc2-dev-env/services/), which might be causing Claude Desktop to incorrectly associate sessions based on the parent folder rather than the actual selected working directory.

Additional notes:

The .claude/settings.local.json file in pmc2-blue-stay-service contains no project association settings — only permissions. This makes it impossible to organize sessions by service in the sidebar. Thank you for looking into this.

What Should Happen?

Hi Anthropic team,

I'm experiencing an issue with Claude Desktop where sessions created for one service are incorrectly grouped under a different project in the left sidebar.

Environment:

Claude Desktop (latest version) Windows 11 Working directory: C:\Personale\Develop\Pmc\pmc2-dev-env\services\pmc2-blue-stay-service Steps to reproduce:

Open Claude Desktop Click "New session" Select the folder pmc2-blue-stay-service as the working directory Start working in the session Expected behavior: The new session should appear in the sidebar under a project named pmc2-blue-stay-service.

Actual behavior: The session is incorrectly grouped under pmc2-customer-care-service in the sidebar, even though the working directory is a completely different service (pmc2-blue-stay-service).

Both services are located under the same parent directory (pmc2-dev-env/services/), which might be causing Claude Desktop to incorrectly associate sessions based on the parent folder rather than the actual selected working directory.

Additional notes:

The .claude/settings.local.json file in pmc2-blue-stay-service contains no project association settings — only permissions. This makes it impossible to organize sessions by service in the sidebar. Thank you for looking into this.

Error Messages/Logs

Steps to Reproduce

Hi Anthropic team,

I'm experiencing an issue with Claude Desktop where sessions created for one service are incorrectly grouped under a different project in the left sidebar.

Environment:

Claude Desktop (latest version) Windows 11 Working directory: C:\Personale\Develop\Pmc\pmc2-dev-env\services\pmc2-blue-stay-service Steps to reproduce:

Open Claude Desktop Click "New session" Select the folder pmc2-blue-stay-service as the working directory Start working in the session Expected behavior: The new session should appear in the sidebar under a project named pmc2-blue-stay-service.

Actual behavior: The session is incorrectly grouped under pmc2-customer-care-service in the sidebar, even though the working directory is a completely different service (pmc2-blue-stay-service).

Both services are located under the same parent directory (pmc2-dev-env/services/), which might be causing Claude Desktop to incorrectly associate sessions based on the parent folder rather than the actual selected working directory.

Additional notes:

The .claude/settings.local.json file in pmc2-blue-stay-service contains no project association settings — only permissions. This makes it impossible to organize sessions by service in the sidebar. Thank you for looking into this.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

1.5354

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

extent analysis

TL;DR

The issue can be resolved by configuring project association settings in the .claude/settings.local.json file for each service.

Guidance

  • Verify that the .claude/settings.local.json file in each service directory (e.g., pmc2-blue-stay-service) contains the correct project association settings.
  • Check if the pmc2-dev-env/services/ parent directory has any default or inherited project association settings that might be causing the incorrect grouping.
  • Consider adding project association settings to the .claude/settings.local.json file in the pmc2-blue-stay-service directory to override any default settings.
  • Test the changes by creating a new session in Claude Desktop and verifying that it appears under the correct project in the sidebar.

Example

No code example is provided as the issue is related to configuration settings.

Notes

The issue is likely caused by the lack of project association settings in the .claude/settings.local.json file for each service. Configuring these settings should resolve the issue.

Recommendation

Apply a workaround by configuring project association settings in the .claude/settings.local.json file for each service, as this is the most likely cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING