1
00:00:00,079 --> 00:00:03,079
So I, I was actually looking at my
terminal history yesterday,

2
00:00:03,639 --> 00:00:09,059
and I, I realized I haven't opened WSL or
spun up a background virtual machine in...

3
00:00:09,659 --> 00:00:11,119
man, four days now.

4
00:00:11,920 --> 00:00:14,979
Because the preview is, it is finally
here.

5
00:00:15,679 --> 00:00:21,219
The ChatGPT desktop app for Linux is
available in preview for supported Ubuntu,

6
00:00:21,760 --> 00:00:24,579
Debian, and Fedora desktop distributions.

7
00:00:25,079 --> 00:00:28,340
And it runs native Codex execution right
on the metal.

8
00:00:29,436 --> 00:00:31,016
Wait, native?

9
00:00:31,536 --> 00:00:37,196
So no subtle translation layer, no running
inside a heavy web view wrapper

10
00:00:37,337 --> 00:00:38,896
pretending to be a system app?

11
00:00:39,250 --> 00:00:39,890
None of that.

12
00:00:39,993 --> 00:00:46,370
Native deb and rpm packages built
specifically for x64 and ARM64

13
00:00:46,427 --> 00:00:47,330
architectures.

14
00:00:47,517 --> 00:00:54,290
We are talking full official builds for
Ubuntu 24.04 LTS

15
00:00:54,410 --> 00:01:01,250
and 26.04 LTS, Debian 13, and Fedora 43
and

16
00:01:01,330 --> 00:01:02,050
44.

17
00:01:02,290 --> 00:01:06,050
Oh, and by the way, before we dive into
the process architecture,

18
00:01:06,330 --> 00:01:09,970
a quick shout out to Jellypod for making
our daily show possible.

19
00:01:10,130 --> 00:01:12,930
But yeah, Maya, no virtual machines
needed.

20
00:01:14,296 --> 00:01:21,016
Okay, Ubuntu 24.04 LTS and 26.04 LTS
getting

21
00:01:21,096 --> 00:01:24,936
direct package love right out of the gate
is massive.

22
00:01:25,636 --> 00:01:30,277
But, okay, let me stop you there, Ethan,
because the thing that caught my eye wasn't

23
00:01:30,357 --> 00:01:31,636
just the execution loop.

24
00:01:32,036 --> 00:01:34,696
It was the cross agent sync engine.

25
00:01:35,337 --> 00:01:39,376
You can literally bring over your entire
environment from Claude Code,

26
00:01:39,516 --> 00:01:42,757
Claude Cowork, or Cursor with one command.

27
00:01:43,284 --> 00:01:45,865
Wait, how seamless is that import
actually?

28
00:01:46,524 --> 00:01:51,385
Is it just pulling basic system prompts,
or is it grabbing full workspace context?

29
00:01:51,777 --> 00:01:53,437
It grabs everything.

30
00:01:53,918 --> 00:01:58,657
You go to Settings, then Import, or you
just type slash import in the CLI,

31
00:01:59,137 --> 00:02:03,338
and it ingests custom skills, settings,
background plugins,

32
00:02:03,737 --> 00:02:06,437
prompt instructions, and active workspace
state.

33
00:02:07,037 --> 00:02:11,777
So if you spent weeks fine tuning skills
inside Cursor or Claude Code,

34
00:02:12,298 --> 00:02:17,138
Codex ingests them in the background with
auto updates so you aren't re-keying

35
00:02:17,197 --> 00:02:18,037
configurations.

36
00:02:18,494 --> 00:02:23,894
Hmm, that auto update piece is big because
workspace drift is usually where multi

37
00:02:24,014 --> 00:02:25,574
tool workflows go to die.

38
00:02:26,234 --> 00:02:31,514
And on the local execution side, they
implemented native Linux process sandboxing.

39
00:02:32,215 --> 00:02:37,974
So when Codex runs code or spins up a
local dev server, it isolates those process

40
00:02:38,034 --> 00:02:43,434
trees locally, while letting the bundled
browser plugin render file backed pages

41
00:02:43,534 --> 00:02:44,654
right inside the app frame.

42
00:02:45,048 --> 00:02:51,467
Which sounds incredible until you look at
how OpenAI actually decided to distribute

43
00:02:51,507 --> 00:02:51,887
the thing!

44
00:02:52,688 --> 00:02:59,287
I mean, deb and rpm packages for Debian 13
and Fedora 44 are great

45
00:02:59,727 --> 00:03:02,388
if you stay inside those standard
distributions.

46
00:03:02,987 --> 00:03:08,367
But why on earth did they skip Flatpak or
AppImage for an initial Linux preview?

47
00:03:08,947 --> 00:03:13,167
Ah, you are thinking about the Arch and
NixOS folks, aren't you?

48
00:03:14,187 --> 00:03:14,747
Yes!

49
00:03:15,247 --> 00:03:20,467
If you are on Arch Linux or NixOS, you are
literally forced to pull out utilities

50
00:03:20,567 --> 00:03:27,088
like alien or bsdtar just to manually
extract the binary payload from the deb file

51
00:03:27,447 --> 00:03:29,647
and patch your library paths manually.

52
00:03:30,228 --> 00:03:35,767
It creates this weird unnecessary friction
for the exact power users who want local

53
00:03:35,907 --> 00:03:37,468
agent execution most.

54
00:03:37,833 --> 00:03:39,273
That is a very fair point.

55
00:03:39,413 --> 00:03:46,393
You get raw native performance on Ubuntu
26.04 LTS, but if

56
00:03:46,433 --> 00:03:51,353
you step two inches outside the main
distribution path, you are unpacking archives

57
00:03:51,406 --> 00:03:51,993
by hand.

58
00:03:52,319 --> 00:03:57,920
And speaking of edge cases on Linux, we
need to talk about Wayland.

59
00:03:58,480 --> 00:04:03,759
Because if you use Wayland compositors
like Hyprland, there is a very specific input

60
00:04:03,859 --> 00:04:05,559
bug waiting to jump scare you.

61
00:04:05,833 --> 00:04:08,553
Wait, is this the virtual keyboard issue?

62
00:04:08,833 --> 00:04:13,193
I saw someone talking about speech to text
macros getting completely garbled.

63
00:04:13,667 --> 00:04:14,208
Yes!

64
00:04:14,607 --> 00:04:20,367
If you use automated macro tools or speech
to text like wtype to inject text into

65
00:04:20,407 --> 00:04:25,168
the ChatGPT app under Wayland, all your
letters turn into random numbers and

66
00:04:25,307 --> 00:04:25,708
symbols.

67
00:04:26,147 --> 00:04:29,827
It is like the virtual keyboard map
completely loses its mind.

68
00:04:30,304 --> 00:04:31,384
Oh, weird.

69
00:04:31,424 --> 00:04:32,524
So what is the workaround?

70
00:04:32,744 --> 00:04:33,924
Is it a permission flag?

71
00:04:34,417 --> 00:04:39,557
No, you have to ditch wtype for that
specific workflow and route through ydotool

72
00:04:39,677 --> 00:04:42,037
using uinput at the system level instead.

73
00:04:42,838 --> 00:04:47,357
Once you route through uinput, the virtual
keycodes map cleanly into the desktop

74
00:04:47,418 --> 00:04:47,937
window again.

75
00:04:48,333 --> 00:04:50,293
That is a super handy tip.

76
00:04:50,383 --> 00:04:55,453
And speaking of state confusion, there is
another subtle gotcha with the CLI to

77
00:04:55,513 --> 00:04:56,813
Desktop project mapping.

78
00:04:57,080 --> 00:05:02,013
If you have been using the Codex CLI on
your machine and then open the brand new

79
00:05:02,083 --> 00:05:07,693
Desktop app, your existing CLI sessions do
not automatically group into Desktop

80
00:05:07,743 --> 00:05:08,733
project folders.

81
00:05:09,109 --> 00:05:10,970
Wait, they don't sync up?

82
00:05:11,750 --> 00:05:14,769
So where do those active CLI terminal
sessions go?

83
00:05:15,208 --> 00:05:20,248
They show up as standalone unlinked chats
floating in your main history thread.

84
00:05:20,381 --> 00:05:25,128
To stop your state from fragmenting, you
have to launch the desktop app directly

85
00:05:25,176 --> 00:05:29,848
from your project's working directory or
explicitly bind the project directory

86
00:05:29,974 --> 00:05:33,128
inside the GUI settings before running
commands.

87
00:05:33,504 --> 00:05:38,664
Right, so if you don't anchor the working
directory first, the app treats your

88
00:05:38,744 --> 00:05:43,444
terminal session like an isolated one off
query instead of a project component.

89
00:05:44,164 --> 00:05:44,704
Good to know.

90
00:05:45,182 --> 00:05:45,901
Exactly.

91
00:05:46,522 --> 00:05:51,361
Now, while we are talking about setup
shifts, there is a strict migration deadline

92
00:05:51,601 --> 00:05:53,761
every team needs on their calendar right
now.

93
00:05:54,661 --> 00:06:00,901
On August 31, 2026, gpt 5.4 and gpt

94
00:06:01,261 --> 00:06:05,621
5.4 mini will be retired for authenticated
ChatGPT sign ins.

95
00:06:06,646 --> 00:06:09,167
August 31, 2026?

96
00:06:09,526 --> 00:06:11,446
That is coming up fast.

97
00:06:12,206 --> 00:06:14,286
What are the recommended drop in
replacements?

98
00:06:14,583 --> 00:06:20,663
You need to update your config files and
environment variables to gpt 5.6 terra and

99
00:06:20,783 --> 00:06:22,583
gpt 5.6 luna.

100
00:06:22,823 --> 00:06:29,383
If your desktop or CLI tools hardcode gpt
5.4, those calls are going to fail the

101
00:06:29,429 --> 00:06:30,663
moment September hits.

102
00:06:31,146 --> 00:06:38,107
So swap gpt 5.4 for gpt 5.6 terra, and
swap gpt

103
00:06:38,426 --> 00:06:41,786
5.4 mini for gpt 5.6 luna.

104
00:06:42,426 --> 00:06:42,766
Got it.

105
00:06:43,125 --> 00:06:43,885
Right.

106
00:06:43,955 --> 00:06:48,965
And for my practical workflow tip today:
when you move those long running terminal

107
00:06:49,058 --> 00:06:54,005
tasks over to the desktop project view,
make sure you double check your workspace

108
00:06:54,058 --> 00:06:54,965
trust settings.

109
00:06:55,178 --> 00:07:00,485
By default, native process execution will
prompt for permission on network calls

110
00:07:00,592 --> 00:07:06,245
until you explicitly trust the workspace
directory root in your config flags.

111
00:07:06,609 --> 00:07:10,509
That saves about fifty unnecessary prompt
popups a day.

112
00:07:11,150 --> 00:07:17,710
Alright, update your models to gpt 5.6
terra, point ydotool at uinput,

113
00:07:18,090 --> 00:07:19,469
and grab those deb packages.

114
00:07:20,009 --> 00:07:20,809
Talk soon, everyone.