docs: clarify codex plugin auto-enable boundary

This commit is contained in:
Peter Steinberger
2026-04-24 06:38:36 +01:00
parent cc28989b4b
commit 6c509d8d4b
3 changed files with 21 additions and 0 deletions

View File

@@ -189,6 +189,13 @@ OpenClaw scans for plugins in this order (first match wins):
- Workspace-origin plugins are **disabled by default** (must be explicitly enabled)
- Bundled plugins follow the built-in default-on set unless overridden
- Exclusive slots can force-enable the selected plugin for that slot
- Some bundled opt-in plugins are enabled automatically when config names a
plugin-owned surface, such as a provider model ref, channel config, or harness
runtime
- OpenAI-family Codex routes keep separate plugin boundaries:
`openai-codex/*` belongs to the OpenAI plugin, while the bundled Codex
app-server plugin is selected by `embeddedHarness.runtime: "codex"` or legacy
`codex/*` model refs
## Plugin slots (exclusive categories)