Skip to content

Commit 2ec4327

Browse files
docs: the desktop environment comes from more than the login shell
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent 05761c4 commit 2ec4327

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

‎docs/user/managed-policy.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -181,9 +181,10 @@ provider's approvals. Pin the variables your users need, such as a gateway URL,
181181
`providers.instances`.
182182

183183
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.
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.
187188

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

0 commit comments

Comments
 (0)