1
00:00:00,240 --> 00:00:04,585
Codex CLI zero point one seven one point
zero dropped on November twentieth,

2
00:00:04,645 --> 00:00:08,709
twenty twenty six, and if you spend your
day staring at a terminal footer,

3
00:00:08,989 --> 00:00:11,852
there is a really practical change tucked
into this release.

4
00:00:12,993 --> 00:00:16,697
Before we get into the config, thanks to
Jellypod AI for sponsoring this episode.

5
00:00:17,338 --> 00:00:19,120
They help make this daily breakdown
possible.

6
00:00:19,740 --> 00:00:22,583
Last time we talked about zero point one
seven one point zero,

7
00:00:23,143 --> 00:00:27,967
we covered remote control, the new model
defaults, and the stable TUI workspace.

8
00:00:28,588 --> 00:00:31,230
Today we are looking at something much
more hands on.

9
00:00:31,931 --> 00:00:37,116
OpenAI added custom MCP status line
selection and authoring through slash

10
00:00:37,296 --> 00:00:41,740
statusline, gated behind the
tui_extensions_statusline feature flag.

11
00:00:42,447 --> 00:00:47,311
To understand why this matters, think
about how slash statusline worked before.

12
00:00:48,011 --> 00:00:51,433
Previously, you could only toggle and
reorder built in footer items.

13
00:00:51,834 --> 00:00:55,676
Things like model with reasoning, context
remaining, current dir,

14
00:00:55,956 --> 00:00:57,437
git branch, or fast mode.

15
00:00:58,638 --> 00:01:02,961
Your choices saved under tui dot
status_line in config dot toml,

16
00:01:03,422 --> 00:01:07,084
and if you wanted to hide it for a session
you ran slash statusline with the clear

17
00:01:07,144 --> 00:01:09,986
flag, or set status_line to an empty
array.

18
00:01:11,778 --> 00:01:16,684
That was fine for basic stats, but if you
wanted project specific telemetry in your

19
00:01:16,764 --> 00:01:18,206
footer, you were stuck.

20
00:01:18,867 --> 00:01:23,332
Maybe you wanted a custom VCS change ID, a
specific spend readout,

21
00:01:23,692 --> 00:01:25,334
or your own rate limit formatting.

22
00:01:25,835 --> 00:01:28,038
You could not plug in your own data
source.

23
00:01:28,697 --> 00:01:33,242
In zero point one seven one point zero,
Codex changes that architecture.

24
00:01:33,602 --> 00:01:37,966
Under the hood, they added local status
line provider configuration and persistence,

25
00:01:38,267 --> 00:01:42,611
plus MCP inventory and bounded streaming
discovery for status line providers.

26
00:01:43,231 --> 00:01:47,676
There are also thread scoped resource
reads and a structured status line snapshot

27
00:01:47,736 --> 00:01:48,697
for the displayed thread.

28
00:01:49,403 --> 00:01:51,425
That snapshot is the key piece.

29
00:01:51,966 --> 00:01:56,610
It exposes token usage totals, context
usage, thread costs,

30
00:01:56,830 --> 00:01:59,572
the workspace headline, and Codex rate
limits.

31
00:02:00,934 --> 00:02:06,278
When tui_extensions_statusline is enabled,
slash statusline can discover,

32
00:02:06,619 --> 00:02:11,163
select, and even author MCP backed status
line providers right from the picker.

33
00:02:12,007 --> 00:02:13,788
So how do you actually use it?

34
00:02:14,489 --> 00:02:18,732
First, make sure you are on zero point one
seven one point zero,

35
00:02:19,112 --> 00:02:25,146
which you can grab via npm install
globally at openai slash codex at zero point one

36
00:02:25,146 --> 00:02:26,237
seven one point zero.

37
00:02:27,038 --> 00:02:32,302
Then you need to enable the
tui_extensions_statusline feature flag in your local

38
00:02:32,342 --> 00:02:32,622
setup.

39
00:02:33,542 --> 00:02:37,945
Once that flag is active, running slash
statusline in the TUI opens up the new

40
00:02:37,986 --> 00:02:39,727
provider discovery and authoring flow.

41
00:02:40,445 --> 00:02:42,987
Now, here is the caveat you need to watch
out for.

42
00:02:43,787 --> 00:02:50,771
Because this is gated behind
tui_extensions_statusline, the release

43
00:02:50,831 --> 00:02:55,834
notes do not document the exact config dot
toml schema for custom providers yet.

44
00:02:56,534 --> 00:03:00,357
You will want to verify the flag and test
your provider setup in your local build

45
00:03:00,517 --> 00:03:02,298
rather than copying an older config.

46
00:03:03,939 --> 00:03:08,962
Also, note that thread cost and usage
reads explicitly reject stale data,

47
00:03:09,302 --> 00:03:13,784
so if a provider is slow or disconnected,
you will not get outdated numbers sitting

48
00:03:13,804 --> 00:03:14,245
in your footer.

49
00:03:15,005 --> 00:03:20,532
Beyond the status line work, zero point
one seven one point zero also shipped a

50
00:03:20,593 --> 00:03:25,939
handful of smaller quality of life fixes
that honestly make daily terminal use a lot

51
00:03:25,999 --> 00:03:26,400
smoother.

52
00:03:27,982 --> 00:03:30,025
Let us run through the ones you will
actually notice.

53
00:03:30,717 --> 00:03:33,480
First up is the non Vim prompt composer.

54
00:03:33,841 --> 00:03:38,886
They added configurable undo and redo
shortcuts, and the best part is that they

55
00:03:38,946 --> 00:03:41,388
restore attachments and large pastes.

56
00:03:41,969 --> 00:03:47,274
If you have ever accidentally wiped out a
huge pasted stack trace and hit undo only

57
00:03:47,334 --> 00:03:49,457
to get nothing back, this fixes that.

58
00:03:50,594 --> 00:03:53,878
Next, session switching is much less
punishing now.

59
00:03:54,418 --> 00:03:59,244
Codex preserves drafts, queued follow ups,
and interrupted input with their original

60
00:03:59,304 --> 00:04:01,466
threads when you switch or resume
sessions.

61
00:04:03,168 --> 00:04:06,712
You no longer lose half a prompt just
because you jumped over to check another

62
00:04:06,752 --> 00:04:07,073
thread.

63
00:04:07,902 --> 00:04:10,425
There are also three quick fixes worth
keeping in mind.

64
00:04:10,925 --> 00:04:14,229
Permission profiles now stay intact when
you change working directories.

65
00:04:15,190 --> 00:04:19,574
Earlier edits are preserved in aggregate
diffs when you are steering an active turn.

66
00:04:20,034 --> 00:04:25,680
And if you are on Windows using WSL, Codex
now resolves pasted Windows paths with

67
00:04:25,960 --> 00:04:27,302
wslpath automatically.

68
00:04:28,070 --> 00:04:34,877
That is the practical rundown for Codex
CLI zero point one seven one point zero.

69
00:04:35,538 --> 00:04:41,163
Try enabling tui_extensions_statusline if
you want to experiment with MCP backed

70
00:04:41,204 --> 00:04:45,208
footers, and enjoy not losing your pasted
attachments on undo.

71
00:04:46,289 --> 00:04:47,290
I will catch you in the next one.

