Skip to content

Integration Support Matrix

Use this page as the canonical support contract for Rampart's main integration surfaces.

At a glance

Surface Best path rampart serve Approval UX Support tier
Claude Code Native hooks
rampart setup claude-code		 Not required for local enforcement;
yes for dashboard/headless approval flows		 Claude native approval prompt Recommended
Codex CLI Preload + wrapper
rampart setup codex		 Typically yes Wrapper/preload approval semantics Recommended
Cline Native hooks
rampart setup cline		 Not required for local enforcement No native ask UI; approval-required actions cancel with context Supported
OpenClaw >= 2026.4.11 Native plugin
rampart setup openclaw		 Required OpenClaw native approval UI Recommended
OpenClaw 2026.3.28 - 2026.4.10 Native plugin
rampart 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 proxy
rampart 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.4.11 → best OpenClaw path; plugin + native approval UI
  • 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 serve is 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.
  • 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 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.