1
00:00:00,079 --> 00:00:03,519
Quick shoutout to Jellypod for supporting
our daily show .

2
00:00:03,559 --> 00:00:10,300
Now, if you updated Codex CLI to version
0.154.0 recently, you,

3
00:00:10,659 --> 00:00:14,899
uh, you might have noticed your laptop fan
kicking into overdrive for no obvious

4
00:00:14,979 --> 00:00:15,299
reason.

5
00:00:16,014 --> 00:00:16,914
Oh yeah .

6
00:00:18,314 --> 00:00:21,514
I thought my terminal was running a heavy
build in the background,

7
00:00:21,674 --> 00:00:23,994
but my machine was basically idle.

8
00:00:24,375 --> 00:00:25,335
That is the thing!

9
00:00:25,435 --> 00:00:31,015
Current community reports trace that idle
load directly to a status indicator in the

10
00:00:31,175 --> 00:00:35,495
TUI that schedules redraws about every 32
milliseconds.

11
00:00:35,623 --> 00:00:41,895
That is around 31 frames per second,
constantly, even when Codex is just waiting on

12
00:00:41,935 --> 00:00:43,015
a background task.

13
00:00:43,401 --> 00:00:46,161
Wait, 31 frames per second ?

14
00:00:46,561 --> 00:00:47,821
In a text terminal?

15
00:00:48,167 --> 00:00:48,967
Right!

16
00:00:49,007 --> 00:00:54,847
And that loop alone can consume up to 30
percent CPU on the codex main process.

17
00:00:54,935 --> 00:00:56,087
Just standing by.

18
00:00:56,484 --> 00:00:58,204
That is wild .

19
00:00:59,365 --> 00:01:02,605
And, and, and it gets worse than just CPU
usage.

20
00:01:03,244 --> 00:01:08,824
The update also added a sparkle effect for
the new GPT 6 Astra model.

21
00:01:09,024 --> 00:01:14,264
Users on GitHub reported that those
continuous star animations cause the cursor to

22
00:01:14,284 --> 00:01:20,364
jump wildly around the input area, and it
completely broke mouse text selection in

23
00:01:20,424 --> 00:01:23,064
terminal emulators like Kitty and Ptyxis.

24
00:01:23,641 --> 00:01:28,042
Ugh , cursor jumping while trying to type
a prompt sounds infuriating.

25
00:01:28,711 --> 00:01:29,971
It really is .

26
00:01:30,691 --> 00:01:35,212
But the most severe side effect was for
screen reader users.

27
00:01:35,772 --> 00:01:41,771
Accessibility reports showed that on macOS
VoiceOver, those non stop redraws caused

28
00:01:41,851 --> 00:01:47,792
VoiceOver to repeatedly announce tiny
fragments of terminal output over and over.

29
00:01:48,312 --> 00:01:52,371
It made the tool completely unusable until
animations were turned off.

30
00:01:53,231 --> 00:01:57,951
One user noted that disabling terminal
animations alone restores usability on the

31
00:01:58,031 --> 00:01:58,851
updated version.

32
00:01:59,307 --> 00:01:59,686
Man .

33
00:02:00,586 --> 00:02:04,786
That really highlights a fundamental
breakdown in how CLI rendering should work.

34
00:02:05,546 --> 00:02:09,607
Terminal emulators are designed for
streaming plain text as it arrives.

35
00:02:10,206 --> 00:02:13,307
When you start running a full graphical
render loop in a terminal,

36
00:02:13,906 --> 00:02:18,946
polling faster than a display even
updates, you flood the terminal buffer with ANSI

37
00:02:19,066 --> 00:02:20,087
escape sequences.

38
00:02:20,687 --> 00:02:24,886
You end up with massive terminal writes
and crazy tmux history bloat.

39
00:02:25,557 --> 00:02:30,177
I actually ran into that exact tmux issue
last night !

40
00:02:31,197 --> 00:02:36,177
I was running a long test suite in tmux,
and the tab title spinner was updating so

41
00:02:36,217 --> 00:02:40,878
fast that the entire pane buffer started
lagging behind my keystrokes.

42
00:02:40,937 --> 00:02:42,197
I thought I was losing my mind.

43
00:02:42,667 --> 00:02:47,627
It is just way too much redraw churn for
what is supposed to be a lightweight

44
00:02:47,677 --> 00:02:48,827
command line helper.

45
00:02:49,312 --> 00:02:55,652
So , if you are dealing with screen
flicker, high CPU, or accessibility issues right

46
00:02:55,692 --> 00:02:57,272
now, what is the fix?

47
00:02:57,708 --> 00:03:02,028
Well, thankfully there are a few config
toggles you can set in your configuration

48
00:03:02,108 --> 00:03:05,468
file, inside your home dot codex
directory.

49
00:03:05,879 --> 00:03:06,219
Right.

50
00:03:06,819 --> 00:03:12,399
In your config dot toml file, you want to
find or create a single tui section

51
00:03:12,480 --> 00:03:12,719
header.

52
00:03:13,339 --> 00:03:18,539
Inside that block, you set animations
equals false, whimsy equals false,

53
00:03:18,939 --> 00:03:22,940
and terminal title equals project in
quotes inside brackets.

54
00:03:23,600 --> 00:03:27,959
Setting whimsy equals false turns off the
Astra sparkle effect specifically.

55
00:03:28,500 --> 00:03:33,559
In fact, one tester confirmed that
reopening the same conversation with tui dot

56
00:03:33,760 --> 00:03:37,399
whimsy equals false greatly reduced the
cursor flicker frequency.

57
00:03:37,829 --> 00:03:41,589
And if you do not want to edit your global
configuration file permanently,

58
00:03:42,170 --> 00:03:44,609
you can pass a flag on the command line .

59
00:03:44,710 --> 00:03:51,409
Just launch with codex space minus c space
tui dot animations equals

60
00:03:51,469 --> 00:03:52,589
false.

61
00:03:52,689 --> 00:03:55,069
That works great for a quick temporary
session.

62
00:03:55,424 --> 00:03:59,485
Just a quick warning on editing the TOML
file directly, though .

63
00:04:00,184 --> 00:04:05,344
Do not accidentally add a second tui table
header if one is already there.

64
00:04:05,465 --> 00:04:09,924
Duplicate section headers will cause Codex
to completely reject your config file on

65
00:04:10,005 --> 00:04:10,404
startup.

66
00:04:10,792 --> 00:04:11,592
Good catch.

67
00:04:11,752 --> 00:04:16,872
Also, keep in mind that changing the
config file does not affect an active session

68
00:04:16,979 --> 00:04:18,072
retroactively.

69
00:04:18,212 --> 00:04:23,112
You have to do a full process restart for
the new TUI settings to take effect.

70
00:04:23,484 --> 00:04:29,184
Oh, and while we are talking about caveats
in version 0.154.0,

71
00:04:29,424 --> 00:04:31,684
there is another bug to watch out for .

72
00:04:32,925 --> 00:04:36,144
The slash rename command is currently
broken.

73
00:04:36,924 --> 00:04:42,645
If you try to rename an active thread, it
silently fails and logs an os error 2

74
00:04:42,684 --> 00:04:43,984
behind the scenes.

75
00:04:44,104 --> 00:04:47,725
So do not be surprised if your session
name refuses to change.

76
00:04:48,244 --> 00:04:50,684
It really makes you step back and think .

77
00:04:50,744 --> 00:04:56,085
As terminal AI agents get more advanced,
teams keep adding visual polish like

78
00:04:56,144 --> 00:04:58,704
shimmer effects, spinners, and sparkles.

79
00:04:59,364 --> 00:05:03,585
But in a terminal, performance and
accessibility have to come first.

80
00:05:04,126 --> 00:05:05,386
100 percent .

81
00:05:06,266 --> 00:05:11,026
Do you think CLI frameworks should just
stick to plain text by default and make

82
00:05:11,167 --> 00:05:12,686
graphic animations opt in?

83
00:05:13,421 --> 00:05:14,501
I really do .

84
00:05:14,681 --> 00:05:19,401
Save the machine cycles for the actual AI
reasoning, not the sparkle effects.

85
00:05:20,081 --> 00:05:23,081
That is all for today's quick take, talk
soon everyone!

86
00:05:23,125 --> 00:05:24,725
Bye everyone !