You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
7.**Managed config files** (`/Library/Application Support/opencode/` on macOS) - admin-controlled
53
+
8.**macOS managed preferences** (`.mobileconfig` via MDM) - highest priority, not user-overridable
52
54
53
-
This means project configs can override global defaults, and global configs can override remote organizational defaults.
55
+
This means project configs can override global defaults, and global configs can override remote organizational defaults. Managed settings override everything.
54
56
55
57
:::note
56
58
The `.opencode` and `~/.config/opencode` directories use **plural names** for subdirectories: `agents/`, `commands/`, `modes/`, `plugins/`, `skills/`, `tools/`, and `themes/`. Singular names (e.g., `agent/`) are also supported for backwards compatibility.
@@ -149,6 +151,106 @@ The custom directory is loaded after the global config and `.opencode` directori
149
151
150
152
---
151
153
154
+
### Managed settings
155
+
156
+
Organizations can enforce configuration that users cannot override. Managed settings are loaded at the highest priority tier.
157
+
158
+
#### File-based
159
+
160
+
Drop an `opencode.json` or `opencode.jsonc` file in the system managed config directory:
These directories require admin/root access to write, so users cannot modify them.
169
+
170
+
#### macOS managed preferences
171
+
172
+
On macOS, OpenCode reads managed preferences from the `ai.opencode.managed` preference domain. Deploy a `.mobileconfig` via MDM (Jamf, Kandji, FleetDM) and the settings are enforced automatically.
0 commit comments