Codex VS Code plugin lacks custom endpoints

The hot take is that this is less a Codex feature request than a demand for an editor-native agent shell that is not tied to one backend. OpenAI's docs present Codex as a bundled agent across CLI, IDE, and cloud, while community issues show custom-provider support in the VS Code extension is still shaky. OpenAI positions Codex as an integrated product across the IDE, CLI, and cloud, not as a generic endpoint router, which limits how far custom API swapping can go. GitHub issues around custom models and providers in the VS Code extension suggest the current implementation may ignore or hardcode model selection in some flows. If the real need is "same UI, different backend," third-party extensions such as idoapico or Codexia are closer to what this Reddit user wants. This is a strong signal that developer demand is shifting from single-vendor coding agents to pluggable, OpenAI-compatible editor tooling.