4 people reported
All time, since Sep 20, including 1 thumbs-up on GitHub.
Sandbox ~/** globs freeze TUI
“On Linux, with sandbox denyRead rules like ~/**/.env, every sandboxed Bash command freezes the TUI for a minute or more.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/893/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Sandbox ~/** deny globs freeze the TUI while walking home. With patterns like "~/**/.env" in denyRead or credentials.files, the glob expander walks all of ~, at startup or on Bash commands.
Is this your bug?
File my report- Where
- sandbox config
- Error text
[WARN] [event-loop-stall] blocked for 56690ms monotonic ... cpu=28500ms- Versions
- 2.1.276 to 2.1.296
- Platforms
- Linux
- How bad
- Stops work: a core feature can't be used. Most reports say it used to work. Some reports say it blocks them completely.
Not quite your bug?
- Startup hangs on Read rule paths2 people
- Sandbox fails on symlinked paths2 people
- Sandbox placeholder files in .git2 people
Original reports3, newest first
- Linux: sandbox denyRead glob (~/**/.env) now freezes the TUI on every Bash command (regression)#101404
- 2.1.284 freezes on first Enter: new sandbox glob expander synchronously walks all of ~ for "~/**/…" denyRead patterns (follows symlinks, unbounded memory); 2.1.280 fine#98023
- sandbox.credentials.files glob expansion costs ~7GB RSS and ~50s on every session start#95695