1
00:00:00,941 --> 00:00:06,645
Codex CLI 0.171.0 dropped on November
twentieth, twenty twenty six,

2
00:00:07,445 --> 00:00:11,168
and it finally solves a workflow headache
that has been bugging anyone running

3
00:00:11,208 --> 00:00:12,569
persistent agent servers.

4
00:00:13,490 --> 00:00:17,553
Before we get into the flags and commands,
thanks to Jellypod AI for sponsoring this

5
00:00:17,613 --> 00:00:18,033
episode.

6
00:00:18,934 --> 00:00:22,116
If you are building developer tools or
just trying to keep up with fast moving

7
00:00:22,156 --> 00:00:27,180
releases, having a clean way to turn
changelogs into audio is pretty handy.

8
00:00:28,022 --> 00:00:31,584
So, what actually changed in 0.171.0?

9
00:00:32,565 --> 00:00:37,412
The centerpiece for automation and multi
device workflows is a new flag on codex

10
00:00:37,412 --> 00:00:37,768
exec.

11
00:00:38,668 --> 00:00:43,531
In pull request sixty one thousand seven
hundred seven, OpenAI added the remote

12
00:00:43,571 --> 00:00:47,393
flag, which you pass as double dash remote
followed by an address.

13
00:00:48,414 --> 00:00:52,516
Instead of spinning up a fresh local
process every time you run a noninteractive

14
00:00:52,556 --> 00:00:56,939
script, codex exec can now attach directly
to an existing app server.

15
00:00:58,179 --> 00:01:02,222
You can start a new session or resume an
existing one right on that running server.

16
00:01:04,679 --> 00:01:07,421
And it pairs with a second update in the
terminal UI.

17
00:01:07,882 --> 00:01:12,945
Pull request sixty two thousand one
hundred twenty one introduces two new slash

18
00:01:12,985 --> 00:01:16,708
commands inside the TUI, slash rc and
slash remote.

19
00:01:17,489 --> 00:01:21,672
Those let you manage local remote control
and display device pairing codes right

20
00:01:21,692 --> 00:01:22,653
from your terminal session.

21
00:01:23,794 --> 00:01:27,877
No manual tunnel setup, no wrestling with
port forwarding just to check in on a

22
00:01:27,977 --> 00:01:29,218
session from another machine.

23
00:01:30,590 --> 00:01:32,151
Why does this matter in practice?

24
00:01:32,712 --> 00:01:36,614
Think about how people actually run Codex
in production or on a team.

25
00:01:37,454 --> 00:01:41,356
A lot of developers keep a persistent
Codex app server running as a background

26
00:01:41,376 --> 00:01:43,578
daemon, or on a beefy remote dev box.

27
00:01:44,558 --> 00:01:47,840
Previously, if you wanted to trigger a
scripted codex exec run,

28
00:01:47,960 --> 00:01:50,341
it would spin up its own isolated local
process.

29
00:01:51,102 --> 00:01:55,844
Now, your CI scripts, local cron jobs, or
automation hooks can target that

30
00:01:55,884 --> 00:01:57,225
persistent server directly.

31
00:01:58,106 --> 00:02:01,047
And if you are working interactively in
the TUI on your workstation,

32
00:02:01,527 --> 00:02:05,350
running slash remote lets you pair an
external device cleanly without leaving the

33
00:02:05,410 --> 00:02:05,730
session.

34
00:02:06,923 --> 00:02:08,444
Here is how to use it today.

35
00:02:09,184 --> 00:02:16,167
First, update your CLI with npm install
global at openai slash codex at

36
00:02:16,407 --> 00:02:18,728
0.171.0.

37
00:02:18,728 --> 00:02:24,650
Once you are on 0.171.0, you can run codex
exec with the double dash remote flag and

38
00:02:24,691 --> 00:02:28,332
your target server address to start or
resume a noninteractive session.

39
00:02:30,033 --> 00:02:35,675
Inside an active TUI session, just type
slash rc or slash remote to bring up remote

40
00:02:35,695 --> 00:02:38,276
control management and view your device
pairing codes.

41
00:02:39,356 --> 00:02:43,618
One caveat to watch out for: the release
notes do not specify the exact address

42
00:02:43,698 --> 00:02:47,340
format or any authentication flags
required for the remote address,

43
00:02:48,520 --> 00:02:54,122
so you will want to run codex exec help
locally to check the exact syntax before

44
00:02:54,182 --> 00:02:55,363
wiring it into a pipeline.

45
00:02:56,648 --> 00:03:02,011
Beyond remote execution, 0.171.0 packs a
few major default changes you will notice

46
00:03:02,031 --> 00:03:03,032
the moment you upgrade.

47
00:03:04,192 --> 00:03:05,553
First, the model catalog.

48
00:03:06,113 --> 00:03:12,897
Pull request sixty two thousand one
hundred six adds GPT 6.2 Sol and GPT 6.2 Astra

49
00:03:12,997 --> 00:03:16,678
to the catalog, and Sol is now the default
catalog selection.

50
00:03:17,519 --> 00:03:20,520
According to OpenAI's November seventeenth
Model Release Notes,

51
00:03:21,021 --> 00:03:24,943
Astra is built for advanced reasoning,
coding, and complex professional work,

52
00:03:25,323 --> 00:03:28,644
while Sol balances speed and lower cost
for multistep tasks.

53
00:03:29,585 --> 00:03:32,726
Both models also generate fewer output
tokens than their predecessors,

54
00:03:33,067 --> 00:03:35,228
which should keep latency and token burn
down.

55
00:03:36,637 --> 00:03:40,840
Second, the TUI workspace is now marked
stable and enabled by default.

56
00:03:41,220 --> 00:03:44,362
That gives you searchable document
previews, image previews,

57
00:03:44,442 --> 00:03:47,944
and subagent transcripts sitting right
alongside your main conversation.

58
00:03:48,945 --> 00:03:53,607
If you are using the non Vim prompt
composer, you also get configurable undo and

59
00:03:53,688 --> 00:03:57,590
redo shortcuts now, and they actually
restore attachments and large pastes,

60
00:03:57,670 --> 00:03:59,891
which was a real pain point before.

61
00:04:00,672 --> 00:04:06,235
Plus, if you enable the tui extensions
statusline flag, you can use slash statusline

62
00:04:06,255 --> 00:04:09,257
to select and author custom MCP status
lines.

63
00:04:10,687 --> 00:04:15,029
Finally, there is a solid batch of
reliability and security fixes worth noting.

64
00:04:15,870 --> 00:04:20,411
Drafts, queued follow ups, and interrupted
input now stay attached to their original

65
00:04:20,472 --> 00:04:22,672
threads when you switch or resume
sessions.

66
00:04:23,393 --> 00:04:26,474
Permission profiles stay intact when you
change working directories,

67
00:04:26,934 --> 00:04:32,056
and late completion events will no longer
cancel approvals for a newer turn.

68
00:04:32,056 --> 00:04:36,538
On the security and enterprise side, MCP
sign in now works for identity providers

69
00:04:36,578 --> 00:04:41,640
that issue ID tokens without refresh
tokens, Linux seccomp restrictions are enforced

70
00:04:41,660 --> 00:04:46,903
for x32 syscalls, and request key is
blocked in Linux network sandbox filters.

71
00:04:48,543 --> 00:04:50,544
That is a clean, high impact release.

72
00:04:51,004 --> 00:04:56,767
Go grab 0.171.0, test out the remote flag,
and we will catch you on the next

73
00:04:56,787 --> 00:04:57,347
changelog.

