Last updated August 7, 2026

Codex Router Compatible Apps — T3 Code Guide

Some apps need no dedicated router integration because they wrap an official CLI that the router already integrates. This page explains the pattern and walks through the supported example: T3 Code.

Why some apps need no integration

T3 Code is a GUI that drives official coding CLIs through adapters rather than talking to models directly. Because the router exposes its model catalog through the endpoint the driven CLI already consumes, you integrate the underlying CLI and the app inherits the added models — there is no separate T3 Code target to install or configure.

T3 Code

Install the router for the CLI T3 Code drives. For the Codex adapter:
```
./install.sh --target codex --guided
```
Fully quit and reopen T3 Code so its adapter reloads the model list.
Pick the added model in T3 Code’s model selector. Project context and thread history are preserved by T3 Code as usual.

The router’s job for T3 Code is only to expose the shared provider registry through the endpoint the driven CLI already knows how to consume. Nothing here changes the app’s own subscriptions, history or settings beyond the additive model configuration the router owns.

The general pattern

Any GUI that wraps the Codex CLI — by launching codex and reading its model list — benefits from the same additive behavior:

The app inherits every model the router merges into Codex’s catalog.
OAuth and API-key setup happens once, in the router, through hidden prompts.
Native GPT models and your ChatGPT login remain untouched.

If the app talks to models directly (its own API keys, its own protocol), it is not covered by this pattern — you would configure that app separately.

What changed: Cursor and opencode app targets

Older versions of the router shipped dedicated Cursor and opencode app targets. Those targets were removed; the router now focuses on Codex, and --target codex is the sole installer target. Two consequences are worth knowing:

opencode the app is no longer an install target. The opencode Go provider (the flat-rate Go subscription and the pay-per-use Zen endpoint) remains available as a regular provider inside Codex — see the models overview.
Anyone with a previously installed Cursor or opencode integration should remove the old service with that checkout’s model-router <target> uninstall before updating, because those port blocks are released.

Verification

After adding models through T3 Code or another CLI-wrapping app:

./bin/model-router codex doctor
./bin/model-router codex providers

Then confirm the model appears in the app’s selector. If it does not, the app may need a full quit-and-reopen (not just a window close) so its adapter re-reads the model list. See models missing from the picker if the underlying Codex picker is also missing entries.