Claude Code Stops Losing Work: Worktrees, Settings, Rewind and Approval Notes

Claude CodeView original changelog

Claude Code 2.1.330 fixes several data-loss bugs. ExitWorktree and the worktree exit dialog no longer delete a worktree another running session is using, and concurrent saves no longer lose user settings. /rewind no longer restores an older file version, and approval notes are kept when a command fails.

Key Takeaways

  • Worktree deletes no longer hit a worktree in use by another session.
  • Concurrent settings saves no longer drop changes.
  • /rewind no longer restores an older file version after queued prompts.
  • Approval notes survive a failed command.
  • Task and plugin lists no longer lose entries to races.
  • ~/.claude.json backups stay good on a full disk.

Worktree Isolation

ExitWorktree and the worktree exit dialog could delete a worktree that another running Claude Code session was working in. Version 2.1.330 fixes that, so one session cannot pull the floor from under another.

Settings and Tasks Saved Together

Changes to user settings could be lost when several Claude Code processes saved them at the same time. Task dependencies and metadata were lost when several task updates ran together, and plugins went missing from the installed list when several claude plugin commands ran at once. All three races are fixed. Incomplete backups of ~/.claude.json also no longer displace good ones when the disk is full.

Rewind and Approvals

/rewind sometimes restored an older version of a file when two queued prompts or stacked skills ran right after a turn that changed it. Text and images added when approving a permission prompt were also dropped when the approved command then failed. Both are fixed.