1
00:00:00,079 --> 00:00:04,000
You know, if you have ever had an AI
coding assistant running in your terminal,

2
00:00:04,599 --> 00:00:04,899
and...

3
00:00:05,299 --> 00:00:09,979
and it is halfway through refactoring a
feature, and suddenly a production hotfix

4
00:00:10,039 --> 00:00:10,519
comes in...

5
00:00:11,399 --> 00:00:12,719
it is total chaos.

6
00:00:13,299 --> 00:00:18,079
You either have to stash your dirty
working tree, or dirty the git state so bad the

7
00:00:18,180 --> 00:00:20,420
agent gets confused and breaks everything.

8
00:00:21,359 --> 00:00:26,520
Before we dive into how to fix that, a
huge shoutout to Jellypod for helping make

9
00:00:26,559 --> 00:00:30,419
this daily show possible every single day.

10
00:00:30,519 --> 00:00:37,099
So, in the new OpenAI Codex CLI release,
version zero point one hundred fifty four

11
00:00:37,259 --> 00:00:42,979
point zero, they added native git worktree
support with the worktree flag and the

12
00:00:43,040 --> 00:00:44,360
slash worktree command.

13
00:00:45,361 --> 00:00:46,841
Oh, this is huge!

14
00:00:47,282 --> 00:00:51,801
Because, um, previously, if you wanted an
agent to work on two things at once,

15
00:00:52,321 --> 00:00:57,602
you were basically copying folders
manually or, or praying that git stash wouldn't

16
00:00:57,641 --> 00:00:59,061
break your build context.

17
00:00:59,761 --> 00:01:04,341
Now, it literally provisions isolated git
checkouts on demand.

18
00:01:04,708 --> 00:01:05,428
Right.

19
00:01:05,481 --> 00:01:11,828
So if you are in the terminal, you can run
codex dash dash worktree fix auth bug,

20
00:01:11,961 --> 00:01:16,548
or if you are already inside the
interactive interface, you just type slash

21
00:01:16,628 --> 00:01:17,588
worktree.

22
00:01:17,688 --> 00:01:18,228
And...

23
00:01:18,248 --> 00:01:21,108
and what actually happens under the hood
when you hit enter?

24
00:01:21,524 --> 00:01:27,404
So under the hood, git creates a
completely separate directory attached to the same

25
00:01:27,464 --> 00:01:32,164
repository history, but with its own
isolated working tree and index.

26
00:01:32,904 --> 00:01:36,744
Codex spins up your new session inside
that clean directory.

27
00:01:37,284 --> 00:01:38,764
So your main working directory...

28
00:01:39,104 --> 00:01:42,564
where you might have three uncommitted
files and a broken test...

29
00:01:42,664 --> 00:01:44,244
stays completely untouched.

30
00:01:44,884 --> 00:01:45,245
Wow.

31
00:01:45,745 --> 00:01:49,784
So if I am working on a complex UI rewrite
in my main terminal,

32
00:01:50,344 --> 00:01:55,585
and I drop into a worktree session for a
quick bug fix, the agent in the worktree

33
00:01:55,664 --> 00:01:59,204
cannot see or mess up my uncommitted draft
files?

34
00:01:59,590 --> 00:02:00,809
Exactly.

35
00:02:00,870 --> 00:02:05,969
And even better, you can browse, switch
between, and resume those worktree sessions

36
00:02:06,109 --> 00:02:06,849
later.

37
00:02:06,909 --> 00:02:12,149
It keeps the full agent session history
attached to that specific isolated directory

38
00:02:12,189 --> 00:02:12,710
context.

39
00:02:13,265 --> 00:02:18,585
Okay, but as someone who used to test
messy edge cases, you know there have got to

40
00:02:18,625 --> 00:02:20,764
be operational risks here.

41
00:02:20,844 --> 00:02:25,645
What happens if an agent session crashes
or gets hard killed while it is sitting

42
00:02:25,664 --> 00:02:26,924
inside one of these worktrees?

43
00:02:27,977 --> 00:02:30,277
Yep, you hit the nail on the head.

44
00:02:30,817 --> 00:02:34,717
If you force kill the process or the
terminal dies unexpectedly,

45
00:02:35,277 --> 00:02:38,918
git does not automatically clean up that
temporary directory on disk.

46
00:02:39,378 --> 00:02:42,177
You can end up with orphaned worktrees
taking up space.

47
00:02:42,737 --> 00:02:42,878
And...

48
00:02:43,257 --> 00:02:44,857
and here is the other tricky part...

49
00:02:45,337 --> 00:02:50,177
if two separate background agents are
operating on worktrees tied to the exact same

50
00:02:50,277 --> 00:02:55,378
git repository, and they both try to run
rebase or commit commands at the same time,

51
00:02:55,878 --> 00:02:59,517
you can trigger git index lock conflicts
on shared reference histories.

52
00:03:00,114 --> 00:03:04,054
Ah, right, because they still share the
underlying dot git folder,

53
00:03:04,214 --> 00:03:05,914
even though their working trees are
separate.

54
00:03:06,238 --> 00:03:06,997
Precisely.

55
00:03:07,377 --> 00:03:12,217
So it gives you isolated file editing, but
you still have to be mindful if multiple

56
00:03:12,257 --> 00:03:16,317
background processes are trying to
manipulate git history simultaneously.

57
00:03:17,004 --> 00:03:21,525
Now, the worktree stuff is only half the
story for multitasking in version zero

58
00:03:21,664 --> 00:03:23,044
point one hundred fifty four point zero.

59
00:03:23,704 --> 00:03:29,164
They also solved another massive annoying
bottleneck with inline user questions.

60
00:03:29,657 --> 00:03:33,517
You mean when the agent stops cold and
waits for you to answer a clarification

61
00:03:33,597 --> 00:03:33,938
question?

62
00:03:34,740 --> 00:03:35,299
Yes!

63
00:03:35,719 --> 00:03:40,319
It used to block the entire terminal
execution pipeline until you responded.

64
00:03:40,980 --> 00:03:44,679
Now, Codex introduces non blocking inline
Q and A.

65
00:03:45,259 --> 00:03:49,539
So while the background agent is grinding
away on compilation or running tests,

66
00:03:49,979 --> 00:03:54,840
a terminal overlay prompts you with
suggested choices or a custom text field.

67
00:03:55,340 --> 00:03:55,459
And...

68
00:03:55,559 --> 00:04:00,279
and the best part is, it does not wipe out
or interrupt your active draft prompt

69
00:04:00,379 --> 00:04:01,859
buffer while you answer.

70
00:04:02,266 --> 00:04:03,527
Oh, that is so nice.

71
00:04:04,066 --> 00:04:08,607
So you can answer its quick question
without losing whatever long instruction you

72
00:04:08,627 --> 00:04:10,887
were currently typing out into the
composer.

73
00:04:11,357 --> 00:04:12,417
Exactly.

74
00:04:12,477 --> 00:04:17,217
It just keeps working in the background
without stealing your focus or resetting

75
00:04:17,237 --> 00:04:18,077
your draft state.

76
00:04:18,537 --> 00:04:22,697
Beyond that, there are some pretty major
system level updates in this release too.

77
00:04:23,477 --> 00:04:28,197
Windows users finally get feature parity
with the background server daemon using

78
00:04:28,277 --> 00:04:33,797
codex daemon, meaning Windows sessions can
now share a persistent background server

79
00:04:33,857 --> 00:04:35,737
with managed lifecycle updates.

80
00:04:36,398 --> 00:04:40,817
Also, if you upgrade or rollback local
plugins while a session is live,

81
00:04:41,378 --> 00:04:46,997
Codex rehydrates the tool skills and hooks
automatically without forcing you to

82
00:04:47,037 --> 00:04:48,037
restart the whole app.

83
00:04:48,781 --> 00:04:49,841
Oh, nice!

84
00:04:50,201 --> 00:04:53,482
And did I see something about copy
formatting improvements too?

85
00:04:53,917 --> 00:04:59,437
Yeah, slash copy now preserves rich text
formatting when pasting into rich text

86
00:04:59,497 --> 00:05:03,677
editors, or you can use it to target
specific session fields directly.

87
00:05:03,917 --> 00:05:05,117
But...

88
00:05:05,144 --> 00:05:08,477
we should highlight a couple breaking
changes and safety additions.

89
00:05:09,018 --> 00:05:14,378
Right, like the deprecated entry point,
codex mcp server...

90
00:05:14,958 --> 00:05:17,017
that is completely gone now, right?

91
00:05:17,417 --> 00:05:18,617
Gone completely.

92
00:05:18,830 --> 00:05:24,217
If you were still calling codex mcp server
directly in your custom scripts,

93
00:05:24,270 --> 00:05:26,377
those will break until you update them.

94
00:05:26,497 --> 00:05:29,097
And there is a new concurrency safety
lock.

95
00:05:29,310 --> 00:05:34,137
If you try to resume a session that is
already open in another terminal or desktop

96
00:05:34,183 --> 00:05:40,617
window, Codex locks it into a read only
transcript view with a retry prompt,

97
00:05:40,670 --> 00:05:45,497
so two windows cannot accidentally
overwrite the same active conversation state.

98
00:05:45,780 --> 00:05:50,719
When you combine isolated worktrees with
non blocking prompts and background

99
00:05:50,819 --> 00:05:56,019
daemons, it really feels like Codex is
shifting from a simple back and forth chatbot

100
00:05:56,359 --> 00:05:58,859
into a true concurrent workstation tool.

101
00:05:59,766 --> 00:06:00,546
Yeah, definitely.

102
00:06:01,086 --> 00:06:03,266
Alright, that is the quick breakdown for
today.

103
00:06:03,667 --> 00:06:04,766
Talk to you all next time!