1
00:00:00,260 --> 00:00:04,864
If you've ever SSH'd into a box, run a
login command, and watched it try to open a

2
00:00:04,924 --> 00:00:08,147
browser that doesn't exist, this one's for
you.

3
00:00:09,008 --> 00:00:11,550
Thanks to Jellypod AI for sponsoring this
episode.

4
00:00:12,111 --> 00:00:18,857
Today on The Codex Changelog: Codex CLI
0.169.0, and the new way to add a custom

5
00:00:18,917 --> 00:00:21,860
model provider without ever touching
config.toml.

6
00:00:22,407 --> 00:00:23,368
Here's what changed.

7
00:00:23,808 --> 00:00:29,792
In 0.169.0, you can add or edit custom
model providers right from the terminal UI.

8
00:00:30,172 --> 00:00:32,173
That's PR 59779.

9
00:00:32,733 --> 00:00:37,817
And PR 60009 adds custom gateway selection
to the sign-in flow itself.

10
00:00:39,237 --> 00:00:43,420
So with custom gateway onboarding enabled,
you can create a provider during sign-in.

11
00:00:43,840 --> 00:00:45,201
The release notes say that plainly.

12
00:00:45,961 --> 00:00:50,844
On top of that, PR 59822 adds device code
authorization for gateway OAuth.

13
00:00:51,365 --> 00:00:54,787
That's the piece for SSH sessions or
machines without a local browser.

14
00:00:56,126 --> 00:00:56,846
Why does it matter?

15
00:00:57,507 --> 00:01:01,089
Before this, pointing Codex at an OpenAI
compatible gateway,

16
00:01:01,430 --> 00:01:06,013
think a corporate proxy or an internal
router, generally meant hand editing

17
00:01:06,073 --> 00:01:08,134
config.toml before you started.

18
00:01:09,655 --> 00:01:13,678
And an OAuth login that assumes a browser
can stall on a headless server,

19
00:01:13,918 --> 00:01:15,680
a container, or a remote cluster.

20
00:01:16,460 --> 00:01:20,603
Now the whole onboarding can happen in the
terminal, and the approval happens on a

21
00:01:20,663 --> 00:01:22,765
different device, like your laptop or
phone.

22
00:01:23,463 --> 00:01:24,084
How to use it.

23
00:01:24,684 --> 00:01:28,206
On a fresh environment, run codex, and at
the sign-in chooser,

24
00:01:28,466 --> 00:01:30,267
pick the custom gateway option.

25
00:01:30,848 --> 00:01:34,189
Remember, that only shows up when custom
gateway onboarding is enabled.

26
00:01:34,930 --> 00:01:37,611
From there you create the provider in the
TUI.

27
00:01:37,611 --> 00:01:40,873
You'll enter things like the base URL and
how credentials are sourced.

28
00:01:43,255 --> 00:01:46,497
If your gateway supports device code,
choose that sign-in.

29
00:01:47,137 --> 00:01:49,758
The terminal shows a short one time code
and a link.

30
00:01:50,659 --> 00:01:55,502
Open the link on any machine with a
browser, approve it, and the CLI picks up the

31
00:01:55,522 --> 00:01:57,163
result and finishes logging in.

32
00:01:57,822 --> 00:01:59,623
A few supporting pieces landed too.

33
00:02:00,183 --> 00:02:05,466
PR 59787 supports credential export
commands for gateway authentication,

34
00:02:06,046 --> 00:02:11,128
and PR 59816 retries those exports after
an unauthorized response.

35
00:02:11,648 --> 00:02:16,451
So if a token goes stale mid session,
Codex can try again instead of just failing.

36
00:02:17,231 --> 00:02:22,413
PR 59823 binds runtime auth to the
provider's selected credential source.

37
00:02:23,254 --> 00:02:27,256
And for app server clients, you can now
list models, or authorize a gateway,

38
00:02:27,376 --> 00:02:30,597
for a configured provider without changing
your default provider.

39
00:02:31,157 --> 00:02:35,359
That's PRs 59776 and 59819.

40
00:02:36,760 --> 00:02:39,721
If you build editor integrations or
tooling on the app server,

41
00:02:39,841 --> 00:02:40,862
that's a real unlock.

42
00:02:41,488 --> 00:02:42,329
Caveats.

43
00:02:42,869 --> 00:02:46,372
Device code only works if your gateway
actually implements it.

44
00:02:46,892 --> 00:02:51,395
If it only takes a static API key or a raw
bearer token, you'll configure a

45
00:02:51,475 --> 00:02:52,776
credential source instead.

46
00:02:53,797 --> 00:02:57,099
Also, device codes are short lived, so
approve it quickly.

47
00:02:58,460 --> 00:03:02,683
And on managed or enterprise gateways,
your admin policy may block device

48
00:03:02,763 --> 00:03:03,483
authorization.

49
00:03:04,484 --> 00:03:08,707
I'd treat those as things to check, not
guarantees, because the release notes don't

50
00:03:08,827 --> 00:03:10,248
spell out the failure behavior.

51
00:03:10,862 --> 00:03:13,123
Now, a few smaller things in the same
release.

52
00:03:13,664 --> 00:03:17,966
First, in the full screen transcript
there's a Collapse turn details option.

53
00:03:18,506 --> 00:03:22,088
It folds completed activity under each
prompt, keeps answers visible,

54
00:03:22,368 --> 00:03:24,029
and tool output stays searchable.

55
00:03:24,949 --> 00:03:26,550
Honestly that's great for long sessions.

56
00:03:27,290 --> 00:03:32,373
Second, in the terminal report editor,
Ctrl+S saves a diagnostic ZIP locally,

57
00:03:32,633 --> 00:03:33,933
even when uploads are disabled.

58
00:03:35,034 --> 00:03:37,455
Handy when you want to attach logs to an
issue yourself.

59
00:03:38,276 --> 00:03:43,618
Third, the option, Yes, clear context and
implement, now hands the full approved

60
00:03:43,658 --> 00:03:47,780
plan to the fresh session, and if that
handoff fails, your current session stays

61
00:03:47,840 --> 00:03:48,080
open.

62
00:03:49,141 --> 00:03:51,062
That one fixes a nasty little failure
mode.

63
00:03:51,800 --> 00:03:56,225
And if you caught our earlier episodes on
the gated Cloud backend and the untrusted

64
00:03:56,285 --> 00:03:59,828
directory hardening in this same release,
this is the third piece.

65
00:04:00,349 --> 00:04:04,372
Less about what Codex can reach, more
about how you get connected in the first

66
00:04:04,393 --> 00:04:04,713
place.

67
00:04:05,814 --> 00:04:06,475
That's it for today.

68
00:04:07,175 --> 00:04:10,559
Go try the device code flow on a box you
normally avoid logging into,

69
00:04:10,699 --> 00:04:11,740
and see how it feels.

