Cap permission modes and allowed providers
Permissions and secrets
maxRuntimeMode sets the broadest permission mode any thread may use, from Supervised up to full-access. providers.allowedDrivers lists which providers may run.
T3 Code docs: managed policy
What it’s for
Use them to stop users, agents, and scheduled tasks from running threads above an approved mode, or on providers you have not allowed.
T3 Code docs: managed policy
When to use it
Use them when your organization requires agents to ask for approval or to use only vetted providers.
T3 Code docs: managed policy
How to use it
In the policy's limits section, set maxRuntimeMode to the broadest permission mode threads may use, such as auto-accept-edits.
T3 Code docs: managed policy
Under limits.providers, list the provider IDs that may run in allowedDrivers, such as claudeAgent and codex.
T3 Code docs: managed policy
In providers.instances, pin an absolute binaryPath for each provider you allow.
T3 Code docs: managed policy
Lower the mode of any thread above the limit so it can run again and send its queued messages.
T3 Code docs: managed policy
Unofficial notes. Not affiliated with Theo or t3.gg.