Directory changes from resume, sandbox, deep links and worktrees no longer leave a stale path behind.
What's wrong with this entry?
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.
- 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.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
Differently-spelled paths are no longer mistaken for existing directories
Both mention working directory
-
v2.1.238
Sync state machine gains a moved-root case and a per-turn pull hook
Both mention directory
-
v2.1.238
Untracked-file survey extracted and shared
Both mention directory