TypeScript
docs: pin an absolute binary path under a permission cap (#29916)
Julius Marminge15707a84b03e
diff --git a/docs/user/managed-policy.md b/docs/user/managed-policy.mdindex f9d170624bd..16febe7aaaf 100644--- a/docs/user/managed-policy.md+++ b/docs/user/managed-policy.md@@ -178,8 +178,13 @@ 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 awrapper script, a launch flag, or a variable such as `NODE_OPTIONS` could otherwise turn off theprovider'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 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 modesT3 Code can place under the limit. Users still choose which ACP Registry agent runs; leave