@devries-cameron20 / t3code Mirror · read-only / commits / 15707a84b0
Fork 0

The best way to control Claude Code, Codex and more from any computer or phone

Mirrored from https://github.com/Camo67/t3code.git

Synced Nov 22, 05:45 UTC

docs: pin an absolute binary path under a permission cap (#29916)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Julius Marminge committed Nov 3, 2026 at 11:46 UTC 15707a84b03e27bb257d60e027812ebf94bbda25
1 file changed +7 -2
docs/user/managed-policy.md
+7 -2
@@ -178,8 +178,13 @@ config home, and the environment variables set on each provider. They come from
178 [`providers.instances`](#providers) or T3 Code's defaults, and users cannot change them, because a
179 wrapper script, a launch flag, or a variable such as `NODE_OPTIONS` could otherwise turn off the
180 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.
188
189 ACP agents' own mode menus have no effect under `maxRuntimeMode`, except Antigravity's, whose modes
190 T3 Code can place under the limit. Users still choose which ACP Registry agent runs; leave