Follow Discord
Sweep 30 Oct 2026 · 21:36Z Build v2.1.315 533 read Stable v2.1.308 Latest v2.1.314 Next v2.1.315 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.315 ·

Project imports can use a safer way of writing files

Importing memory files, skills, commands and settings into a project can now use safer file writing, and reports links and permissions not copied

Under the hood Internal Changes
JSON All of v2.1.315
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.315,
Internal ChangesSection of the release

Unclear It is not stated what condition switches the safer writing on, so whether it applies to a given import is unknown.

What

When Claude Code imports memory files, skills, commands or settings into a project, meaning the files that belong to the current project rather than your whole account, it can now use a safer way of writing them instead of plain writes. This only happens when a particular condition inside Claude Code is met.

When copying skills, Claude Code now reports:

  • symbolic links (shortcut files that point somewhere else) that it did not copy
  • files whose setuid, setgid or sticky bits, which are special file permissions, were not kept

If a copy stops partway, it says that a partial copy may remain and where.

Why

This is aimed at stopping an import from writing outside the project through a symbolic link. You are also told what was left out of a copy.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not stated what condition switches the safer writing on, so whether it applies to a given import is unknown.

See this entry in the whole of v2.1.315 →

Feedback