Auto mode classifier inconsistently blocks production deploys explicitly allowed in autoMode.allow

Auto mode classifier blocks production deploys that the user explicitly allowed, inconsistently

(Written on behalf of the account owner, a hotel manager who uses Claude Code on his own property-management application. Original complaint in French below.)

My .claude/settings.local.json explicitly allows powershell -NoProfile -ExecutionPolicy Bypass -File ./deploy.ps1, both in permissions.allow and in autoMode.allow. The autoMode.allow rule is a written sentence saying this production deploy is authorized by me and must not be refused.

On 2026-09-24/25, the exact same command:

• was allowed at 06:58, 08:38 and 21:20;
• was refused at 15:02 and 18:55, and twice around midnight, with reasons [Production Deploy] or just Blocked by classifier.

A read-only HTTP GET of the app's /api/version endpoint (to check which commit production serves) was also refused under [Production Deploy].

I am not satisfied with this. I pay for this service, I gave a written and explicit authorization, and the tool applies it unpredictably. At night, I had to intervene myself for an action I had authorized.

Request: user-written autoMode.allow rules should be honored consistently, or the tool should explain precisely which rule was evaluated and why it was not honored.

---

Je ne suis pas satisfait de cette interdiction. Je paie un service, j'ai donné une autorisation écrite et explicite, et l'outil l'applique de façon imprévisible. Je dois intervenir moi-même en pleine nuit pour un geste que j'ai autorisé. Je demande que les règles autoMode.allow rédigées par l'utilisateur soient respectées de façon constante, ou que l'outil explique précisément pourquoi une règle n'a pas été honorée.