1
00:00:00,340 --> 00:00:05,180
Imagine you are in the middle of a coding
flow, you type a prompt into the desktop

2
00:00:05,260 --> 00:00:08,840
app, hit enter, the model starts thinking,
and then...

3
00:00:09,420 --> 00:00:12,020
the text box just vanishes.

4
00:00:12,995 --> 00:00:13,995
Completely gone.

5
00:00:14,535 --> 00:00:17,715
Not scrolled off screen, not disabled,
just...

6
00:00:18,415 --> 00:00:20,815
empty space where your input field used to
be.

7
00:00:21,375 --> 00:00:22,095
Uh, yeah!

8
00:00:22,455 --> 00:00:28,415
That was the reality for a lot of people
running ChatGPT Desktop build 26.901.

9
00:00:29,015 --> 00:00:33,335
You would ask a question, the assistant
would answer, and then you literally could

10
00:00:33,375 --> 00:00:35,055
not type a follow up message.

11
00:00:35,600 --> 00:00:40,580
Under the hood, this was a pretty wild DOM
lifecycle bug in the Electron client.

12
00:00:41,200 --> 00:00:45,900
When you submitted a prompt, entering the
thinking state triggered an unmount of the

13
00:00:45,940 --> 00:00:47,120
message composer node.

14
00:00:47,760 --> 00:00:51,800
But when the assistant finished its
response, the app forgot to remount it.

15
00:00:52,313 --> 00:00:57,293
Right, but the funniest part to me was how
developers figured out how to get it

16
00:00:57,353 --> 00:00:57,793
back.

17
00:00:58,353 --> 00:01:01,773
Some people noticed that if you switched
conversation tabs and came back,

18
00:01:01,953 --> 00:01:02,913
it would re-render.

19
00:01:03,533 --> 00:01:05,073
But my favorite workaround...

20
00:01:05,633 --> 00:01:10,853
someone discovered that taking a
screenshot with Windows Shift S brought it back

21
00:01:10,933 --> 00:01:11,573
instantly!

22
00:01:12,915 --> 00:01:16,015
Because pressing the Shift key fired a
system keyboard event,

23
00:01:16,575 --> 00:01:20,935
which forced Electron to run a layout
reflow and repaint the UI!

24
00:01:21,655 --> 00:01:26,575
So pressing Shift literally snapped the
invisible input box back into existence.

25
00:01:26,965 --> 00:01:30,985
It is such a classic web tech ghost in the
machine moment.

26
00:01:31,705 --> 00:01:34,505
Oh, and before we dig into the project
context side of this,

27
00:01:34,945 --> 00:01:39,585
a quick shoutout to Jellypod for
supporting the show and helping us break down these

28
00:01:39,645 --> 00:01:41,025
daily technical updates.

29
00:01:41,678 --> 00:01:43,578
Absolutely, big thanks to Jellypod.

30
00:01:44,318 --> 00:01:47,298
Now, while the vanishing composer was
stealing the headlines,

31
00:01:47,758 --> 00:01:52,638
there was a second, much quieter bug in
that same release cycle that was hitting

32
00:01:52,698 --> 00:01:54,038
local workspace workflows.

33
00:01:54,465 --> 00:01:57,005
Wait, what was happening with local
projects?

34
00:01:57,333 --> 00:02:01,733
So if you opened a local Git project in
the app and started a new chat inside that

35
00:02:01,783 --> 00:02:07,413
project context, the conversation was
supposed to stay attached to that workspace.

36
00:02:07,453 --> 00:02:11,733
But instead, as soon as the first turn
completed, the chat would decouple.

37
00:02:12,650 --> 00:02:14,930
It would slip out of the project folder?

38
00:02:15,375 --> 00:02:19,775
Yeah, it fell straight down into your
general Recents list as an unanchored chat.

39
00:02:19,882 --> 00:02:25,295
Which meant it instantly lost access to
your repository paths and workspace

40
00:02:25,342 --> 00:02:25,935
environment.

41
00:02:26,378 --> 00:02:31,218
So if you were relying on that context for
background tools or subagents,

42
00:02:31,678 --> 00:02:32,858
it just dropped the thread.

43
00:02:33,550 --> 00:02:34,170
Exactly.

44
00:02:34,710 --> 00:02:41,390
But the good news is build 26.903.71938
fixed both

45
00:02:41,470 --> 00:02:41,870
issues.

46
00:02:42,470 --> 00:02:47,750
The composer now stays mounted cleanly
across turn states, and local project chats

47
00:02:47,970 --> 00:02:49,950
actually stay anchored where they belong.

48
00:02:50,340 --> 00:02:53,820
How do folks make sure they are actually
on that fixed build?

49
00:02:54,167 --> 00:02:59,687
You want to open the question mark or help
menu, click About ChatGPT,

50
00:02:59,707 --> 00:03:01,527
and confirm you are on version

51
00:03:01,687 --> 00:03:08,127
26.903.71938 or higher.

52
00:03:08,215 --> 00:03:12,727
That version string is what guarantees
your composer lifecycle and workspace

53
00:03:12,794 --> 00:03:14,647
persistence are intact.

54
00:03:15,047 --> 00:03:15,607
Okay, good.

55
00:03:16,187 --> 00:03:20,227
But if you are on Windows, there is
another surprise you might run into,

56
00:03:20,527 --> 00:03:23,087
especially if you use Codex for code
patches.

57
00:03:23,658 --> 00:03:25,838
Oh right, the Defender false positive?

58
00:03:26,875 --> 00:03:27,275
Yes!

59
00:03:27,795 --> 00:03:33,415
Windows Defender has been flagging certain
Codex patch commands as actual malware.

60
00:03:34,095 --> 00:03:38,755
Specifically, when Codex tries to apply a
source patch using a PowerShell here

61
00:03:38,895 --> 00:03:43,855
string, Defender flags it as Trojan Win32
Commando A.

62
00:03:44,208 --> 00:03:50,208
Ah, because the generated command line
passes a huge literal string into the codex

63
00:03:50,273 --> 00:03:54,208
executable helper with the run as apply
patch flag.

64
00:03:54,568 --> 00:03:55,308
Exactly.

65
00:03:55,868 --> 00:04:00,668
Windows Defender sees a massive thirteen
thousand character PowerShell command

66
00:04:00,848 --> 00:04:06,548
trying to spawn a process and immediately
blocks it with Access Denied OS Error 5.

67
00:04:07,008 --> 00:04:09,148
It does not even let the patch execute.

68
00:04:09,640 --> 00:04:13,980
That is tricky because read only
operations work fine through that same route,

69
00:04:14,460 --> 00:04:18,180
but the moment a large C sharp patch here
string is attached,

70
00:04:18,740 --> 00:04:20,340
heuristic detection triggers.

71
00:04:20,797 --> 00:04:21,137
Right.

72
00:04:21,397 --> 00:04:25,657
So if your background agent suddenly stops
making file edits on Windows,

73
00:04:26,157 --> 00:04:29,437
check your Protection History before
assuming your prompt failed.

74
00:04:29,875 --> 00:04:32,035
And one last tip on checking for updates.

75
00:04:32,142 --> 00:04:37,715
Do not rely on the in app What is new menu
inside the desktop app to know if you are

76
00:04:37,768 --> 00:04:38,355
up to date.

77
00:04:39,883 --> 00:04:43,063
Yeah, that menu can lag behind by weeks.

78
00:04:43,463 --> 00:04:47,443
It showed August dates well into September
for a lot of users.

79
00:04:47,792 --> 00:04:50,752
Always check the build string directly in
the About dialog.

80
00:04:50,864 --> 00:04:55,392
That is the single source of truth for
what client code is actually running on your

81
00:04:55,462 --> 00:04:56,032
machine.

82
00:04:56,462 --> 00:05:00,982
Check those build numbers, watch out for
Defender alerts, and keep your local

83
00:05:01,022 --> 00:05:02,122
workspaces anchored.

84
00:05:02,762 --> 00:05:04,382
That is it for today's quick take.