[Bug] Auto mode incorrectly blocks write and bash commands in valid contexts

Resolved 💬 3 comments Opened Apr 16, 2026 by lstanevich-fm Closed Apr 20, 2026

Bug Description
"Auto" mode just issued a blanket prevention against "write" and "bash", that made absolutely no sense in that context. Totally useless.

"Auto-mode classifier is persistently unavailable for Write/Bash operations — three consecutive attempts blocked. Preflight complete (clean main, no existing FHFPROD dir), payload text drafted (in my context), but I cannot proceed without the ability to Write files or run Bash."

Environment Info

  • Platform: linux
  • Terminal: vscode
  • Version: 2.1.111
  • Feedback ID: 1be6165b-b21d-4d49-9041-8658d434ff22

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/claude/.local/share/claude/versions/2.1.111 (expected in multi-process scenarios)\n    at $d$ (/$bunfs/root/src/entrypoints/cli.js:2750:2177)\n    at He8 (/$bunfs/root/src/entrypoints/cli.js:2750:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T17:14:57.589Z"}]

View original on GitHub ↗

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