From 05761c4cb648ac88bf904978526a409b95bad22c Mon Sep 17 00:00:00 2001 From: Julius Marminge <51714798+juliusmarminge@users.noreply.github.com> Date: Mon, 2 Nov 2026 19:31:16 -0800 Subject: [PATCH 1/2] docs: pin an absolute binary path under a permission cap Co-Authored-By: Claude Opus 5.5 --- docs/user/managed-policy.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/user/managed-policy.md b/docs/user/managed-policy.md index e1ba501e6fa3d..97ee9015c1569 100644 --- a/docs/user/managed-policy.md +++ b/docs/user/managed-policy.md @@ -178,8 +178,12 @@ config home, and the environment variables set on each provider. They come from [`providers.instances`](#providers) or T3 Code's defaults, and users cannot change them, because a wrapper script, a launch flag, or a variable such as `NODE_OPTIONS` could otherwise turn off the provider's approvals. Pin the variables your users need, such as a gateway URL, in -`providers.instances`. Variables in the environment that starts T3 Code itself still reach -providers. +`providers.instances`. + +Variables in the environment that starts T3 Code itself still reach providers, and a default +binary path such as `claude` is looked up on that environment's `PATH`. The desktop app takes both +from the user's login shell, so a user could put their own `claude` earlier on their `PATH`. Pin an +absolute `binaryPath` in `providers.instances` for each provider you allow. ACP agents' own mode menus have no effect under `maxRuntimeMode`, except Antigravity's, whose modes T3 Code can place under the limit. Users still choose which ACP Registry agent runs; leave From 2ec432729cfe66a3a3909ca513aa8722586232c0 Mon Sep 17 00:00:00 2001 From: Julius Marminge <51714798+juliusmarminge@users.noreply.github.com> Date: Mon, 2 Nov 2026 19:45:23 -0800 Subject: [PATCH 2/2] docs: the desktop environment comes from more than the login shell Co-Authored-By: Claude Opus 5.5 --- docs/user/managed-policy.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/user/managed-policy.md b/docs/user/managed-policy.md index 97ee9015c1569..db557d8aa4130 100644 --- a/docs/user/managed-policy.md +++ b/docs/user/managed-policy.md @@ -181,9 +181,10 @@ provider's approvals. Pin the variables your users need, such as a gateway URL, `providers.instances`. Variables in the environment that starts T3 Code itself still reach providers, and a default -binary path such as `claude` is looked up on that environment's `PATH`. The desktop app takes both -from the user's login shell, so a user could put their own `claude` earlier on their `PATH`. Pin an -absolute `binaryPath` in `providers.instances` for each provider you allow. +binary path such as `claude` is looked up on that environment's `PATH`. The desktop app builds that +environment from settings the user controls, such as their shell profile, so a user could put their +own `claude` earlier on their `PATH`. Pin an absolute `binaryPath` in `providers.instances` for each +provider you allow. ACP agents' own mode menus have no effect under `maxRuntimeMode`, except Antigravity's, whose modes T3 Code can place under the limit. Users still choose which ACP Registry agent runs; leave