clauding.de
DE
• 2 min read AI-generated

Claude Code 2.1.205: Protection Against Transcript Tampering and Windows Fixes

Copy article as Markdown

The new Claude Code version closes a tricky gap: in auto mode, tampering with session transcripts is now blocked. Plus fixes for Windows worktrees and background agents.

Claude Code Release Developer Security Background Agents
Featured image for "Claude Code 2.1.205: Protection Against Transcript Tampering and Windows Fixes"

Claude Code keeps shipping on a weekly cadence — and version 2.1.205 brings a fix that goes beyond your average bug patch. Auto mode now actively prevents session transcripts from being tampered with. Sounds technical, but it’s really a security matter.

What’s inside

The key changes in this version:

  • Transcript protection: A new auto mode rule blocks tampering with session transcript files. If you need auditable logs — say, in an enterprise or government context — this is a hard safety net.
  • JSON schema fix: --json-schema was silently producing unstructured output when the schema was invalid. And schemas using the format keyword were wrongly rejected. Both fixed.
  • Lost messages: A message sent while Claude was working got silently dropped if the turn ended at the --max-turns limit. Not anymore.
  • Windows worktree fix: Removing a worktree on Windows deleted files outside the worktree when an NTFS junction or directory symlink lived inside it. A nasty bug — now resolved.
  • Background agents: Agents resumed via SendMessage stayed wrongly listed as ‘failed’ or ‘completed’. The status is accurate again.

My take

Two of these fixes are more than cosmetic. The transcript protection shows where things are heading: Claude Code is increasingly used in regulated environments where a tamper-evident log isn’t a nice-to-have, it’s mandatory. Fits nicely with the FedRAMP High government launch from the same week.

And the Windows worktree bug is a good reminder of why file-deleting operations always make me a little uneasy. One symlink in the wrong place, and suddenly files are gone that nobody meant to touch. Good that it gets fixed fast — but it’s a reminder of how much trust we put in these agents when they handle our file system.

Sources: