[Feature Request] Add persistent disallowedTools configuration to settings.json

Resolved 💬 3 comments Opened Feb 10, 2026 by Crazytieguy Closed Mar 11, 2026

Bug Description
The --disallowedTools CLI flag strips tools from the model's context entirely, which is preferable to the deny permission rule that keeps tools visible but blocks them at runtime. However, --disallowedTools is only available as a CLI flag with no persistent equivalent. It would be nice to have the same functionality via settings.json

Environment Info

  • Platform: darwin
  • Terminal: WezTerm
  • Version: 2.1.38
  • Feedback ID: 93fa0d5d-929d-4f55-a6c6-5dad18bbcb0e

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/yoav/.local/share/claude/versions/2.1.38 (expected in multi-process scenarios)\n    at QVR (/$bunfs/root/claude:3622:2098)\n    at yMA (/$bunfs/root/claude:3622:1209)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-10T10:14:56.486Z"},{"error":"Error: Agent type 'Plan' has been denied by permission rule 'Task(Plan)' from userSettings.\n    at call (/$bunfs/root/claude:2054:22079)\n    at async qW8 (/$bunfs/root/claude:3477:13995)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-10T10:15:37.590Z"}]

View original on GitHub ↗

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