1
00:00:00,099 --> 00:00:03,619
You know that feeling when you have an AI
coding agent running in the background,

2
00:00:04,079 --> 00:00:08,859
working on a long task, and you realize
you forgot to tell it one crucial detail?

3
00:00:10,507 --> 00:00:11,046
Oh, yeah.

4
00:00:11,366 --> 00:00:16,046
You end up tab jumping across five open
terminal windows, trying to find the right

5
00:00:16,147 --> 00:00:21,266
interactive session just to type one line,
or worse, trying to attach to the

6
00:00:21,306 --> 00:00:24,206
terminal interface without breaking what
it is doing.

7
00:00:24,583 --> 00:00:25,543
Exactly.

8
00:00:25,623 --> 00:00:28,023
It is a total context switch penalty.

9
00:00:28,163 --> 00:00:32,263
And thanks to Jellypod for helping make
this daily show a reality,

10
00:00:32,330 --> 00:00:38,503
today we are breaking down Codex CLI
version zero point one forty nine point zero,

11
00:00:38,610 --> 00:00:44,503
which drops a really clever fix for that
exact headache, a new command called codex

12
00:00:44,596 --> 00:00:45,143
queue.

13
00:00:45,484 --> 00:00:47,424
Okay, codex queue.

14
00:00:48,264 --> 00:00:50,364
How does this actually work under the
hood?

15
00:00:50,744 --> 00:00:54,864
Is it just piping text into a running
process or something cleaner?

16
00:00:55,167 --> 00:00:57,407
It is much cleaner than raw piping.

17
00:00:57,507 --> 00:01:03,887
The command format is basically codex
queue, then the session ID or session name,

18
00:01:03,923 --> 00:01:06,047
followed by your instruction in quotes.

19
00:01:06,691 --> 00:01:11,752
Hmm, so if I have a session running
locally or even on a remote machine,

20
00:01:12,212 --> 00:01:17,172
I can just push a prompt straight to it
from anywhere in my terminal without opening

21
00:01:17,191 --> 00:01:18,431
its interactive interface?

22
00:01:18,949 --> 00:01:19,310
Right.

23
00:01:19,689 --> 00:01:24,609
It pushes the prompt input directly into
that existing session's message stream.

24
00:01:25,250 --> 00:01:29,909
And the big thing is, if the background
process was idle, waiting for input,

25
00:01:30,529 --> 00:01:32,369
codex queue wakes it right back up.

26
00:01:32,757 --> 00:01:37,056
Wait, what if the agent is right in the
middle of executing a command or writing

27
00:01:37,116 --> 00:01:38,776
code when you queue the message?

28
00:01:39,125 --> 00:01:42,325
It preserves deferred command execution
semantics.

29
00:01:42,415 --> 00:01:47,205
Meaning it queues your message safely,
lets the active turn complete,

30
00:01:47,225 --> 00:01:50,725
and then immediately processes your queued
instruction next,

31
00:01:50,775 --> 00:01:54,885
without interrupting the current tool call
or corrupting state.

32
00:01:55,174 --> 00:01:57,294
That is huge for automation.

33
00:01:57,875 --> 00:02:02,815
As someone who spent years on the messy
end of test pipelines and build scripts,

34
00:02:03,414 --> 00:02:05,974
my mind immediately goes to automation
here.

35
00:02:06,675 --> 00:02:11,154
You do not even need a human sitting at
the keyboard to steer the agent anymore.

36
00:02:11,500 --> 00:02:12,540
No, totally!

37
00:02:12,633 --> 00:02:15,500
Think about a Git post commit hook, for
instance.

38
00:02:15,620 --> 00:02:20,380
You push a branch or make a commit, and
your hook automatically fires a background

39
00:02:20,449 --> 00:02:20,940
script.

40
00:02:21,127 --> 00:02:25,660
It can invoke codex queue to tell your
background refactoring agent,

41
00:02:25,820 --> 00:02:30,460
hey, the new branch is pushed, go ahead
and run the lint and fix pass on those

42
00:02:30,522 --> 00:02:31,660
modified files.

43
00:02:31,947 --> 00:02:35,486
And your main terminal stays completely
free the whole time.

44
00:02:36,027 --> 00:02:39,726
You keep working on your primary feature
branch while the refactoring agent

45
00:02:39,786 --> 00:02:41,686
processes the queue in the background.

46
00:02:42,561 --> 00:02:43,522
Exactly.

47
00:02:43,621 --> 00:02:47,542
No context switching, no terminal tab
management gymnastics.

48
00:02:47,822 --> 00:02:50,641
Okay, but I have to ask about the edge
cases.

49
00:02:51,221 --> 00:02:55,842
How does codex queue know which session to
message if you use names instead of

50
00:02:55,922 --> 00:02:56,741
UUIDs?

51
00:02:57,083 --> 00:03:00,203
Ah, that is the exact trap to watch out
for.

52
00:03:00,627 --> 00:03:06,027
Right, because if you name two background
sessions something generic like worker or

53
00:03:06,168 --> 00:03:11,708
refactor, and you run codex queue worker
do this, you get routing ambiguity.

54
00:03:12,367 --> 00:03:16,708
In zero point one forty nine point zero,
if duplicate session names exist,

55
00:03:16,947 --> 00:03:21,827
it can fail or misroute unless you specify
the exact session UUID.

56
00:03:22,167 --> 00:03:26,247
So pro tip for anyone writing shell
scripts or hook automation,

57
00:03:26,327 --> 00:03:31,927
always pass the explicit session UUID in
your scripts rather than relying on loose

58
00:03:31,967 --> 00:03:32,807
session names.

59
00:03:32,792 --> 00:03:36,792
Now, speaking of maintaining session state
without breaking things,

60
00:03:36,872 --> 00:03:43,112
zero point one forty nine point zero also
fixes a subtle, super frustrating problem

61
00:03:43,192 --> 00:03:46,552
with working directories inside the agent
interface.

62
00:03:46,988 --> 00:03:48,227
Oh, let me guess.

63
00:03:48,287 --> 00:03:52,347
Is this about running standard cd commands
inside the agent tool calls?

64
00:03:53,970 --> 00:03:54,589
You guessed it.

65
00:03:55,029 --> 00:04:00,489
Previously, if you asked Codex to run cd
into a sub folder inside its shell

66
00:04:00,549 --> 00:04:05,489
execution tool, the sub process might
change directories for that one shell command,

67
00:04:06,090 --> 00:04:10,709
but Codex's internal workspace index
stayed right where it was at the root.

68
00:04:11,502 --> 00:04:12,083
Right!

69
00:04:12,422 --> 00:04:13,902
Classic state drift.

70
00:04:14,442 --> 00:04:20,303
The shell sub process thinks it is in
package slash auth, but Codex's internal file

71
00:04:20,442 --> 00:04:24,862
search and system context still think you
are sitting in the repository root.

72
00:04:25,402 --> 00:04:29,662
So tool calls start resolving relative
file paths completely wrong.

73
00:04:30,000 --> 00:04:30,960
Exactly.

74
00:04:31,067 --> 00:04:36,720
To fix that state drift, Codex zero point
one forty nine point zero introduces

75
00:04:36,784 --> 00:04:43,360
dedicated slash commands, slash cd, slash
pwd, and slash cwd

76
00:04:43,467 --> 00:04:46,160
right inside the interactive session
interface.

77
00:04:46,546 --> 00:04:51,746
So when you type slash cd followed by a
path, what happens differently?

78
00:04:52,083 --> 00:04:57,043
It updates both the active session context
and the agent's tool execution sandbox in

79
00:04:57,123 --> 00:04:57,603
place.

80
00:04:57,843 --> 00:05:02,963
So if you shift context from your root
project directory down into a specific

81
00:05:03,043 --> 00:05:07,763
microservice sub directory, the sandbox,
the file indexing,

82
00:05:07,783 --> 00:05:11,843
and the relative path resolution all
update instantly together.

83
00:05:12,319 --> 00:05:16,639
Without having to stop the session, export
your history, and spin up a whole new

84
00:05:16,759 --> 00:05:18,059
agent from the sub directory?

85
00:05:18,417 --> 00:05:22,177
Without losing a single line of
conversation history or memory,

86
00:05:22,241 --> 00:05:22,577
yeah.

87
00:05:23,298 --> 00:05:27,757
Having spent so much time dealing with
monorepo launches, where you have three

88
00:05:27,817 --> 00:05:32,317
services, shared libraries, and infra code
all sitting in one repo,

89
00:05:32,918 --> 00:05:35,357
that is a massive quality of life fix.

90
00:05:35,918 --> 00:05:40,537
You can start high level at the monorepo
root, outline your architectural changes,

91
00:05:40,718 --> 00:05:44,897
and then slash cd into the backend service
directory to let the agent write code

92
00:05:44,958 --> 00:05:45,497
right there.

93
00:05:45,792 --> 00:05:50,512
And to manage all these sessions, they
also added an interactive codex agents

94
00:05:50,568 --> 00:05:51,872
dashboard in this release.

95
00:05:52,012 --> 00:05:58,592
You can search, start, open, rename, and
stop active tasks from one centralized

96
00:05:58,648 --> 00:05:59,312
dashboard.

97
00:05:59,591 --> 00:06:02,611
Plus codex doctor got a big upgrade too,
right?

98
00:06:02,958 --> 00:06:08,398
Yeah, codex doctor now checks endpoint
protection, network proxy failures,

99
00:06:08,478 --> 00:06:14,398
desktop app state, and update connectivity
automatically, which saves so much triage

100
00:06:14,462 --> 00:06:16,798
time when a local environment gets quirky.

101
00:06:17,132 --> 00:06:22,071
When you zoom out and look at all of this
together, headless queuing with codex

102
00:06:22,192 --> 00:06:28,172
queue, live directory switching with slash
cd, and interactive task management with

103
00:06:28,231 --> 00:06:32,391
codex agents, it really feels like Codex
is evolving.

104
00:06:32,750 --> 00:06:37,390
It is shifting from just a chat window in
your terminal into a real background

105
00:06:37,452 --> 00:06:42,110
software engineering daemon that fits
right into local developer workflows.

106
00:06:42,405 --> 00:06:47,704
Alright, that is zero point one forty nine
point zero in a nutshell.

107
00:06:47,784 --> 00:06:49,384
Time to go update our terminal hooks.

108
00:06:50,467 --> 00:06:51,107
Definitely.

109
00:06:51,587 --> 00:06:52,448
Talk soon, everyone.