Skip to content

Commit 05761c4

Browse files
docs: pin an absolute binary path under a permission cap
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent 61c3794 commit 05761c4

1 file changed

Lines changed: 6 additions & 2 deletions

File tree

‎docs/user/managed-policy.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -178,8 +178,12 @@ config home, and the environment variables set on each provider. They come from
178178
[`providers.instances`](#providers) or T3 Code's defaults, and users cannot change them, because a
179179
wrapper script, a launch flag, or a variable such as `NODE_OPTIONS` could otherwise turn off the
180180
provider's approvals. Pin the variables your users need, such as a gateway URL, in
181-
`providers.instances`. Variables in the environment that starts T3 Code itself still reach
182-
providers.
181+
`providers.instances`.
182+
183+
Variables in the environment that starts T3 Code itself still reach providers, and a default
184+
binary path such as `claude` is looked up on that environment's `PATH`. The desktop app takes both
185+
from the user's login shell, so a user could put their own `claude` earlier on their `PATH`. Pin an
186+
absolute `binaryPath` in `providers.instances` for each provider you allow.
183187

184188
ACP agents' own mode menus have no effect under `maxRuntimeMode`, except Antigravity's, whose modes
185189
T3 Code can place under the limit. Users still choose which ACP Registry agent runs; leave

0 commit comments

Comments
 (0)