[BUG] shell-snapshot is gone
Status Fixed / completed
Maintainer reply ✓ Yes — wolffiex
Workaround ✓ Mentioned in thread ↓
Activity 15 comments · opened Jul 16, 2025 · closed Jul 17, 2025
💡 Likely answer: A maintainer (wolffiex, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform (select one):
- [X] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other: <!-- specify -->
- Claude CLI version: 1.0.53
- Operating System: ArchLinux
- Terminal: Gnome Terminal
Bug Description
For the first time I started getting this error for every single Bash tool claude is trying to run:
● Now let me start the server and test the improved design:
● Bash(source venv/bin/activate && python run.py &)
⎿ Error: zsh:source:1: no such file or directory:
/home/pmatos/.claude/shell-snapshots/snapshot-zsh-415f5359.sh
● Bash(source venv/bin/activate && python run.py &)
⎿ Error: zsh:source:1: no such file or directory:
/home/pmatos/.claude/shell-snapshots/snapshot-zsh-415f5359.sh
● Bash(source venv/bin/activate && python run.py &)
⎿ Error: zsh:source:1: no such file or directory:
/home/pmatos/.claude/shell-snapshots/snapshot-zsh-415f5359.sh
● Let me try a different approach:
● Bash(source _venv/bin/activate && python run.py &)
⎿ Error: zsh:source:1: no such file or directory:
/home/pmatos/.claude/shell-snapshots/snapshot-zsh-415f5359.sh
● Let me try a different approach without the problematic shell snapshot:
● Bash(_venv/bin/python run.py &)
⎿ Error: zsh:source:1: no such file or directory:
/home/pmatos/.claude/shell-snapshots/snapshot-zsh-415f5359.sh
● Bash(_venv/bin/python run.py &)
⎿ Error: zsh:source:1: no such file or directory:
/home/pmatos/.claude/shell-snapshots/snapshot-zsh-415f5359.sh
● Let me try a simpler approach:
● Bash(_venv/bin/python run.py &)
⎿ No (tell Claude what to do differently)I have another terminal running /init on another project, but unsure it's related. I have certainly ran multiple claude's simultaneously without any problems.
15 Comments
I am having the same issue for the last couple of days.
running into the same issue, I wonder if it's because I'm using multiple terminals too
Running into this. Also using multiple terminals. Now my Claude Code cannot delete files. What can we do to resolve this? This is a major issue and is causing serious disruptions in my workflow.
Anyone else who ran into this: Use
rm -rf ~/.claude/shell-snapshots/and then restart Claude Code.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. If you need to see it for debugging purposes,
claudewill write to a file when you run with--debugPlease let us know if you have any more trouble!
@wolffiex I'm running 1.0.53 and still ran into this error. It looks like
~/.claude/shell-snapshots/is still used?Oh sorry yes, I forgot to update this issue. We published 1.0.54 yesterday but it caused some problems for folks who have big shell environments. We have a fix for that which should go out with 1.0.55 today. I'll try to promote the new build early today so folks get this fix. Sorry again for the trouble.
In the meantime would
rm -rf ~/.claude/shell-snapshots/be fineThat will break in-progress sessions.
I did that too, but still got a crash after.
Ok 1.0.55 is out with the fix. Please let us know how it goes for you.
i still got this issue, even i updated the latest version 1.0.56.
Environment:
@ant-kurt is this a Windows-specific thing you think?
@thanhbn I'm not able to repro this one on v1.0.56 in WSL - can you try clearing out the
/home/admin88/.claude/shell-snapshotsfolder and restartingclaudeto see if it still occurs?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.