INTEGRATIONS
Keep the tools.
Change the route.
Give each tool a SafetyRouter identity, then point it at your tenant gateway.
OpenCode v2
Use OpenCode 2's new provider schema with a protected file-based SafetyRouter credential.
OpenCode v2 guide →Tested · v1O1OpenCode v1
Keep an existing OpenCode 1.x installation working with its legacy provider configuration.
OpenCode v1 guide →TestedCXCodex
Tested with the Codex CLI and SafetyRouter's buffered Responses adapter.
Configuration guide →TestedCCClaude Code
Tested with the Claude Code CLI, Messages streaming, and local tool use.
Configuration guide →Community testedGHGitHub Copilot CLI
Use Copilot CLI's BYOK provider mode with a governed SafetyRouter identity.
macOS, Linux, and Windows guide →Compatible nowWUOpen WebUI
Run a governed browser chat in Docker through SafetyRouter's OpenAI-compatible interface.
Docker configuration guide →Compatible nowCLOpenClaw
Connect through OpenClaw's OpenAI Completions custom-provider interface.
Configuration guide →Compatible nowHAHermes Agent
Route Hermes through SafetyRouter as a custom OpenAI-compatible endpoint.
Configuration guide →Chat compatibleCRCursor
Route standard Chat models now. Agent and Tab have documented compatibility boundaries.
Setup and limitations →OpenCode v1 and v2, Codex, and Claude Code have client-tested protocol paths. The two OpenCode releases require different provider and credential configuration. GitHub Copilot CLI has been community-tested through its official BYOK provider mode. Open WebUI, OpenClaw, and Hermes use the supported /v1/chat/completions contract. Cursor Chat supports that contract for standard models, while Cursor Agent needs further adapter testing and Cursor Tab cannot use a custom endpoint.