u/GMeTroFuN

Disclosure: I build Swobu (swobuforge/swobu), the open-source local compatibility gateway used here.

I wanted to run GLM-5.2 in the actual Codex harness.

The problem is protocol compatibility: Codex speaks the Responses API, while Z.AI currently exposes different interfaces. So pointing Codex directly at Z.AI is not enough. Swobu translates between them locally.

Setup is through the terminal UI:

1. Add Z.AI
2. Paste your General API key
3. Select glm-5.2
4. Copy the local Swobu endpoint into Codex

No hand-edited Swobu config files. No OpenRouter. No Codex fork.

Run it:

curl -fsSL https://swobu.com/install.sh | sh

Disclosure: I build Swobu (swobuforge/swobu), the open-source local compatibility gateway used here.

I wanted to use Codex’s harness with DeepSeek V4 Pro. The protocols do not line up directly: Codex sends Responses API requests, while DeepSeek currently exposes V4 Pro through Chat Completions and Anthropic-compatible interfaces. Native Responses support is available only for Flash.

Swobu translates between those protocols locally. Setup happens through an interactive terminal UI: add DeepSeek, paste your API key, then copy the local endpoint into Codex.

No hand-edited Swobu config files. No OpenRouter. No Codex fork.

Run it:

curl -fsSL https://swobu.com/install.sh | sh

I am not claiming this is the first DeepSeek–Codex bridge. DeepSeek’s official ecosystem already documents Moon Bridge. I am testing whether a general-purpose local gateway becomes more useful once you also want multiple providers, stable routes, account switching or fallback.

Swobu is still maturing, so I would especially appreciate reports of difficult edge cases.