[Bug] Security prompt repeatedly appears despite folder being untrusted

Resolved 💬 2 comments Opened Feb 25, 2026 by fwends Closed Feb 25, 2026

Bug Description
Quick safety check: Is this a project you created or one you trust? (Like your own code, a well-known open source project, or work from your team). If not, take a moment to review what's in this folder first.

Claude Code'll be able to read, edit, and execute files here.

Security guide

❯ 1. Yes, I trust this folder

  1. No, exit

Enter to confirm · Esc to cancel
why am I getting this stupid crap on every single time I open Claude now? This is absolutely ridiculous, it's another stupid gimmick that you put in that causes more stress when working with Claude. Unbelievable. Every day I wake up to something that's completely changed or different that breaks my workflow. Why on earth have you put this in there? I don't want it. I've already untrusted this folder 50 times.

Environment Info

  • Platform: darwin
  • Terminal: tmux
  • Version: 2.1.53
  • Feedback ID: c6aec7a2-ca95-40f8-856e-f80aec23e2ff

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.1.53 (expected in multi-process scenarios)\n    at lPR (/$bunfs/root/claude:3631:2100)\n    at qvA (/$bunfs/root/claude:3631:1211)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-25T00:55:56.470Z"},{"error":"RangeError: stdout maxBuffer length exceeded\n    at unknown\n    at onData (node:child_process:153:110)\n    at emit (node:events:95:22)\n    at addChunk (internal:streams/readable:264:47)\n    at readableAddChunkPushByteMode (internal:streams/readable:242:18)\n    at handleNumberResult (internal:streams/native-readable:69:18)\n    at <anonymous> (internal:streams/native-readable:43:68)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-25T00:56:01.636Z"}]

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗