Shell Snapshot File Not Found During Restoration

Status Fixed / completed
Maintainer reply ✓ Yes — wolffiex
Activity 6 comments · opened Jul 15, 2025 · closed Jul 17, 2025
💡 Likely answer: A maintainer (wolffiex, collaborator) responded on this thread — see the highlighted reply below.

Bug Description
I get this issue about once a day, and I have to start a new Claude Code session to get shall commands to work:

Error: zsh:source:1: no such file or directory: /Users/parker/.claude/shell-snapshots/snapshot-zsh-c92eee72.sh

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 1.0.52
  • Feedback ID: 7e7d93c3-c96e-411e-96dc-79d17d6b1059

Errors

[{"error":"Error: Command failed: security find-generic-password -a $USER -w -s \"Claude Code\"\nsecurity: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n\n    at genericNodeError (node:internal/errors:983:15)\n    at wrappedFn (node:internal/errors:537:14)\n    at checkExecSyncError (node:child_process:882:11)\n    at execSync (node:child_process:954:15)\n    at eD (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:706:6320)\n    at file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:618:14473\n    at Q (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:520:14406)\n    at AF (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:618:13613)\n    at gC (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:618:12479)\n    at $B (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:618:17093)","timestamp":"2025-07-15T21:41:53.196Z"}]

View original on GitHub ↗

6 Comments

aleksey-perplexity · 1 year ago
wolffiex collaborator · 1 year ago

Hi everyone, I'm really sorry for this trouble. It seems we found the limit of our lockfile implementation 😅

We switched to an in-memory implementation of the snapshot in 1.0.54. If you need to see it for debugging purposes, claude will write to a file when you run with --debug

Please let us know if you have any more trouble!

wolffiex collaborator · 1 year ago

sorry, we had to revert 1.0.54 due to an issue with the in-memory implementation. we are working on this and will try again tomorrow

wolffiex collaborator · 1 year ago

Ok 1.0.55 is out with the fix. Please let us know how it goes for you.

wolffiex collaborator · 1 year ago

correction 1.0.56 is the version with the comprehensive fix

github-actions[bot] · 1 year ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.