experiment
Routing Codex across incompatible model protocols.
Testing whether a local gateway can preserve the Codex workflow while handling protocol conversion, model routing, failover, and request tracing.
Codex uses the Responses API, while many models expose Chat Completions or Anthropic Messages. This experiment moves that mismatch into a local gateway so the client can keep its existing workflow.
MuxLayer now converts among those protocol families and selects upstream models by routes, health, and fallback order. Its local logs show how a request changed, where it went, and why it failed.
Agent clients and model APIs do not always speak the same protocol
Coding agents differ in request shapes, tool calls, and streaming events. Modifying each client separately scatters configuration and makes multi-provider support harder to maintain.
Convert and route requests locally
Requests enter one local endpoint. MuxLayer chooses a model from its routing rules and converts between Responses, Chat Completions, and Anthropic Messages when needed.
Common coding clients are connected
The public compatibility matrix covers Codex, Claude Code, Gemini CLI, OpenCode, AtomCode, and more than twenty-five model providers. Routing, failover, and request tracing continue to gain provider-specific compatibility.