# Codex CLI 0.169.0 lets users add custom model providers and sign in with a device code

> Codex CLI 0.169.0 adds custom model provider editing in the terminal and a device-code sign-in option for supported gateways over SSH or without a local browser.

- Status: official (From the company, authors or authority themselves, with a link to their own page.)
- Topic: Products
- Published: 2026-11-13T08:39:10+00:00
- Updated: 2026-11-13T09:08:53.434378+00:00
- Web page: https://ai-news.ikangai.com/story/codex-cli-0-169-0-lets-users-add-custom-model-providers-and-sign-in-with-a-devic/
- Seen in: Codex CLI releases
- Change: capability (New capability)
- Applies to: Codex CLI 0.169.0, custom model providers, app-server, supported gateways

## What changed

Codex CLI 0.169.0 lets users add or edit custom model providers from the terminal and sign in with a device code for supported gateways over SSH or without a local browser.

Codex CLI 0.169.0, published on 13 November, lets users add or edit custom model providers from the terminal. When custom gateway onboarding is enabled, a provider can be created during sign-in. For supported gateways, sign-in can use a device code instead of a local browser. The release notes say this covers SSH sessions and machines without a browser.

The device-code option changes how sign-in works on remote machines. The GitHub release page links the work to several pull requests. #59779 added provider configuration editing to the TUI. #60009 added custom gateway selection to TUI sign-in. #60186 allowed creating custom providers during sign-in. #59822 added device-code authorization for gateway OAuth. #60486 added the same to the app-server, and #60662 brought gateway device-code sign-in to headless TUI sessions. The device flow therefore exists in both the terminal interface and the app-server layer that other clients use.

For app-server clients, the release notes say they can now list models and authorise a gateway for a configured provider without changing the default provider. That is the change tied to #59776, which allowed selecting a configured provider in model/list, and #59819, which allowed provider selection for gateway OAuth reads and logins. Related pull requests add credential export commands for gateway authentication (#59787), retry those exports after unauthorised responses (#59816), and enable model catalog discovery with gateway OAuth (#60414). The release notes do not say which gateways count as supported, and they do not name the setting that turns on custom gateway onboarding. The scope of the device-code option can only be inferred from the phrase 'supported gateways'.

## Why it matters

Organisations that route Codex through their own model gateways can onboard developers on remote or headless machines more easily, without needing a local browser.

## What you can do

Platform teams that use custom gateways with Codex could test the device-code sign-in on a remote host before rolling it out to developers.

## Original source

- [Release 0.169.0 · openai/codex · GitHub](https://github.com/openai/codex/releases/tag/rust-v0.169.0)

---

AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it.

Cite as: IKANGAI AI News, "Codex CLI 0.169.0 lets users add custom model providers and sign in with a device code", 2026-11-13, https://ai-news.ikangai.com/story/codex-cli-0-169-0-lets-users-add-custom-model-providers-and-sign-in-with-a-devic/
