From a01bd8d50a1e5c0b476424fbaa5e5faaab3ac430 Mon Sep 17 00:00:00 2001
From: Leonid Bugaev <leonsbox@gmail.com>
Date: Wed, 4 Mar 2026 09:11:03 +0000
Subject: [PATCH] fix: accept noDefaultAllow/noDefaultDeny aliases in
 bashConfig

Visor's BashConfig uses noDefaultAllow/noDefaultDeny field names, but
probe only accepted disableDefaultAllow/disableDefaultDeny. Accept both
so workflow YAML using visor's convention works without a separate
mapping step.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---
 npm/src/tools/bash.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/npm/src/tools/bash.js b/npm/src/tools/bash.js
index 5b065ebd..8a4ec5ab 100644
--- a/npm/src/tools/bash.js
+++ b/npm/src/tools/bash.js
@@ -45,8 +45,8 @@ export const bashTool = (options = {}) => {
   const permissionChecker = new BashPermissionChecker({
     allow: bashConfig.allow,
     deny: bashConfig.deny,
-    disableDefaultAllow: bashConfig.disableDefaultAllow,
-    disableDefaultDeny: bashConfig.disableDefaultDeny,
+    disableDefaultAllow: bashConfig.disableDefaultAllow || bashConfig.noDefaultAllow,
+    disableDefaultDeny: bashConfig.disableDefaultDeny || bashConfig.noDefaultDeny,
     debug,
     tracer
   });