I made isolated Codex Desktop profiles for alternative model providers

I built Codex Desktop Custom Models because experimenting with alternative model providers inside one desktop installation can quickly mix sessions, automation state, ports, and provider-specific configuration.

Instead of modifying the main Codex setup, the project creates isolated desktop profiles. Each profile can have:

• its own app identity and icon

• a separate CODEX_HOME

• independent sessions and automation state

• a dedicated local bridge process

• provider-specific configuration

The bridge translates between the Responses-style workflow expected by Codex and OpenAI-compatible Chat Completions APIs, including tool calls and tool outputs rather than acting as a text-only proxy.

The current reference profile uses MiniMax, but the structure is intended to be adapted to other compatible providers. It supports macOS and Linux and is explicitly unofficial.

Open source: https://github.com/ademisler/cod...

For people experimenting with multiple providers: would you prefer a fully isolated app per provider, or a lighter profile switcher inside one app?