Integration Support Matrix¶
Use this page as the canonical support contract for Rampart's main integration surfaces.
For release-candidate validation and latest-agent checks, use the Release Compatibility Gate. The support tier below should match the most recent evidence from the exact Rampart candidate build and bundled plugin metadata.
At a glance¶
| Surface | Best path | rampart serve | Approval UX | Support tier |
|---|---|---|---|---|
| Claude Code | Native hooksrampart setup claude-code | Not required for local enforcement; yes for dashboard/headless approval flows | Claude native approval prompt | Recommended |
| Codex CLI | Preload + wrapperrampart setup codex | Typically yes | Wrapper/preload approval semantics | Recommended |
| Cline | Native hooksrampart setup cline | Not required for local enforcement | No native ask UI; approval-required actions cancel with context | Supported |
| OpenClaw >= 2026.5.2 | Native pluginrampart setup openclaw | Required | First-class plugin approvals / native approval UI | Recommended |
| Hermes Agent | Experimental user pluginrampart setup hermes | Required | ask blocks until plugin approval/resume support exists | Experimental |
| OpenClaw 2026.4.29 - 2026.5.1 | Native pluginrampart setup openclaw | Required | Native plugin startup/interception; approval delivery was not the launch baseline | Supported |
| OpenClaw 2026.3.28 - 2026.4.28 | Native pluginrampart setup openclaw | Required | Native enforcement; approval UX less polished than current builds | Supported |
| OpenClaw < 2026.3.28 | Legacy shim + bridge + patching | Required | Legacy bridge/shim behavior | Legacy compatibility |
| Cursor / Claude Desktop | MCP proxyrampart mcp -- | Required | MCP error / proxy-mediated behavior | Supported |
| Custom / Python / CI | HTTP API | Required | Caller-defined | Supported |
Best default choices¶
- Claude Code → best overall native path
- Codex CLI → best CLI path when you want strong coverage
- OpenClaw >= 2026.5.2 → best OpenClaw path; plugin + native approval UI
- Hermes Agent → experimental plugin path for early testing;
askdecisions block rather than resume - Cline → good supported path, but less polished approval UX than Claude Code
Degraded behavior notes¶
- Claude Code / Cline native hooks: local policy evaluation still works when
rampart serveis down, but dashboard features, approval APIs, and external approval state do not. - OpenClaw native plugin: depends on
rampart serve; sensitive tools block when the service is unavailable, while configured lower-risk fail-open tools may still proceed. - Hermes Agent plugin: depends on
rampart serve; mutating/high-risk tools fail closed when unavailable, while explicitly configured read-only tools may fail open. - Legacy OpenClaw patching: compatibility-only path; requires re-patching after upgrades.
- Wrapper / preload / API paths: behavior depends on integration settings and fail-open/fail-closed configuration.
Choosing the right path¶
- Use native hooks when the agent supports them.
- Use the OpenClaw native plugin on current OpenClaw builds.
- Use the Hermes Agent plugin for conservative early Hermes testing.
- Use wrapper / preload when the CLI agent has no hook system.
- Use MCP proxy or HTTP API for clients that integrate through MCP or custom service calls.