Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.236 ·

Changing directory no longer leaves a stale working directory behind

Directory changes from resume, sandbox, deep links and worktrees no longer leave a stale path behind.

You'll notice Bug Fixes
JSON All of v2.1.236
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Working DirectoryArea: what it touches
Bug FixesKind: in v2.1.236,
Bug FixesSection of the release
What

Worktree cleanup and switching, session resume, sandbox startup, deep links and CLI boot all changed directory directly before. They now go through one helper that changes directory and then immediately re-reads it, which refreshes Node's cached working directory and surfaces a deleted target right away instead of leaving a stale path to fail later.

Details
  • The re-read is wrapped so a vanished directory is swallowed rather than crashing the path that moved.
  • Worktree cleanup failure still reports as "Could not chdir to original directory while cleaning up worktree".
  • Logging switched from reading the cwd directly to a getter with a fallback.
Evidence

Could not chdir to original directory while cleaning up worktree, process.chdir, function MI(e) {\n process.chdir(e);, process.chdir(e);

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.236 →

Feedback