CSupported
Codex
OpenAI Responses protocol
Point the installed Codex client at Hormuz, keep native model behavior, and authenticate with a revocable employee profile.
hormuz client-config codexClient integrations
Keep the tools.
Change the control point.
Hormuz meets employees inside existing Codex and Claude Code workflows. No new chat surface. No provider key on the laptop.
Supported clients
Governed access where work already happens.
Hormuz implements the provider protocols these clients already understand, then adds identity, policy, budgets, DLP, and evidence at the gateway.
CSupported
Claude Code
Anthropic Messages protocol
Use authenticated model discovery and the Messages API path while the company policy remains the final authorization layer.
hormuz client-config claudeProvider protocols
Native request shapes. One policy envelope.
Hormuz preserves provider model IDs and client behavior while enforcing a consistent organization policy before egress.
SurfaceCurrent contractBoundary
OpenAIResponses + streaming + compaction relayProvider-compatible
AnthropicMessages + token count + streamingProvider-compatible
IdentityBootstrap, OIDC JWT, or Hormuz sessionHormuz-owned
EvidenceUsage, cost, policy, DLP, security metadataContent-free
Compatibility without overclaiming
Every client claim is tied to evidence.
The public compatibility matrix distinguishes exact installed-client proof, protocol-shaped local tests, development-only surfaces, and production gates that remain open.
Read the compatibility matrix ↗Exact client
Installed binary and protocol path explicitly verified.
Protocol-shaped
Deterministic local contract evidence, not a live provider claim.
Open gate
Requires customer environment, operations, or independent review.
One workflow first
Bring one governed client path.
We will map its identity, credentials, policy, egress, budget, and evidence boundary together.