Integrations for OpenClaw, Claude Code, Codex, Gemini, Copilot, and OpenCode.
The integrations page covers the runtime layer: which tools and agents connect, what the adapter does, and how each runtime gets mapped into the same control language.
Know where the control plane ends and where each runtime begins.
Compile the same control model into runtime-specific files and config.
Every runtime keeps its own surface. The adapter makes those differences explicit.
Deep filesystem and config mapping with skills, approvals, and manifests.
A similar vocabulary for rules, skills, permissions, and local project settings.
Task-specific skills and local workspace control with a lightweight runtime model.
Coverage for the runtimes users already ask about.
The adapter explains what can be written, what can be observed, and what must stay manual.
Each runtime gets the same product story, but the implementation surface stays honest.
Where the skill folder lives and how it is updated.
What the runtime can allow, deny, or ask for.
What changes can take effect without a restart.
How the control plane learns whether the runtime matched the desired state.
Keep the wording close to the tools people already use.
Runtime pages are where people look for compatibility, not marketing adjectives.
This is the page cluster for runtime and adapter searches.
One runtime per long-tail page.
Choose the runtime you want to govern first.