Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.267 ·

Symlinked-settings-write fallback is dead code

A new fallback meant to retry settings writes through symlinked paths never actually runs

TierNothing to try yethow much it should matter to you
Useful2my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaSettingswhat it touches
KindIn Developmentin v2.1.267,
Group of 2 Nothing to try yet

A new fallback meant to retry settings writes through symlinked paths never actually runs

What

A new helper (lr) wraps settings-file writes so that, on a permission-type write failure, it checks a new Lo() function and, if Lo() returns true, retries the write with allowSymlink: true (and checkParentDir: false), logging "Writing settings through symlinked path". However, Lo() is a stub that unconditionally returns false, so the retry branch and its log message can never run.

Why

Anyone whose settings file lives behind a symlink and hits this permission error still sees the original failure; the intended fallback to write through the symlinked path does not actually work yet.

See this entry in the whole of v2.1.267 →