Skip to content

Commit 15707a8

Browse files
docs: pin an absolute binary path under a permission cap (#29916)
Co-authored-by: Claude Opus 5.5 <[email protected]>
1 parent dd24b37 commit 15707a8

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

‎docs/user/managed-policy.md‎

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -178,8 +178,13 @@ 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 builds that
185+
environment from settings the user controls, such as their shell profile, so a user could put their
186+
own `claude` earlier on their `PATH`. Pin an absolute `binaryPath` in `providers.instances` for each
187+
provider you allow.
183188

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

0 commit comments

Comments
 (0)