Desktop app: folder assigned when creating a new session becomes an additional working directory — session's primary project silently stays the previous one

Status Open
Reported on v2.1.181
Maintainer reply None cached
Activity 2 comments · opened Aug 10, 2026

Environment

  • Claude Code desktop app on macOS (Darwin 25.5.0), CLI core 2.1.181

What I did

  1. In the desktop app, with project A open, I created a new thread for a brand-new

project and immediately assigned it a newly created folder B during setup.

  1. I sent my first message — the kickoff description for the new project in B.

What I expected

The new session's project (primary working directory) is B: it is listed under B,
B's CLAUDE.md is auto-loaded, B's per-project memory attaches, and the first
message executes in B's context.

What actually happened

The session was created with its primary working directory set to A — the project
that happened to be open — and B was attached only as an *additional working
directory*. A's CLAUDE.md and A's per-project auto-memory loaded silently, and my
kickoff message for project B executed inside project A's context. (In my case A's
instructions contain a wrong-channel guard, so the assistant caught and flagged it —
otherwise I would not have noticed until much later.)

Timestamps from my machine confirm the sequence: folder B created 19:11, session
created 19:17 with primary cwd = A.

There is no way I can find to fix it afterwards: the primary working directory
cannot be changed after creation, and I found no UI to remove the additional
working directory either. The misfiled session is permanent.

Why this hurts

  • The wrong project's CLAUDE.md and memory silently shape every response.
  • Project histories cross-contaminate; per-project session lists become unreliable.
  • It is a recurring trap, not a one-off — it has misfiled several of my new-project

threads over time, and I now run a dedicated housekeeping routine partly to catch
these strays.

Suggestions

  1. A folder assigned during new-session creation should become the session's

primary working directory — or the app should ask explicitly: "use as the
session's project folder" vs. "add as an additional working directory".

  1. Show the session's primary project prominently in the composer before the first

message is sent.

  1. Allow changing the primary working directory at least until the first message.
  2. Provide UI to remove an additional working directory from a session.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗