1
00:00:00,260 --> 00:00:02,102
Hey, hope the terminal's treating you well
today.

2
00:00:02,382 --> 00:00:06,165
Quick thanks first: thanks to Jellypod AI
for sponsoring this episode.

3
00:00:06,845 --> 00:00:12,670
Okay, today is about one feature from
Codex CLI 0.169.0, and it ties back to the

4
00:00:12,770 --> 00:00:18,635
0.168.0 and 0.169.0 stuff we've covered,
the Cloud backend and the custom gateways.

5
00:00:19,215 --> 00:00:23,639
It's the terminal workspace, with multiple
side chat tabs, and saved side chats that

6
00:00:23,679 --> 00:00:24,800
come back after you restart.

7
00:00:25,697 --> 00:00:26,818
Here's the problem it solves.

8
00:00:28,360 --> 00:00:32,084
One chat thread means every side question
either interrupts the main task,

9
00:00:32,264 --> 00:00:34,206
or waits until the main task ends.

10
00:00:35,488 --> 00:00:39,272
You've got an agent running a long turn,
and you just want to ask what some regex

11
00:00:39,372 --> 00:00:39,652
does.

12
00:00:40,173 --> 00:00:42,695
Before this, you either waited, or you
cancelled.

13
00:00:43,256 --> 00:00:43,936
Neither is great.

14
00:00:44,657 --> 00:00:45,318
So what changed.

15
00:00:45,938 --> 00:00:47,219
The workspace is opt-in.

16
00:00:47,840 --> 00:00:51,963
You turn it on with the feature flag,
features dot tui underscore workspace.

17
00:00:52,603 --> 00:00:57,107
In your config dot toml, under the
features table, set tui underscore workspace

18
00:00:57,207 --> 00:00:58,087
equals true.

19
00:01:00,029 --> 00:01:03,111
Or you can pass the enable flag on the
command line, codex,

20
00:01:03,471 --> 00:01:06,113
dash dash enable, tui underscore
workspace.

21
00:01:06,834 --> 00:01:10,377
That's the form you'd use to try it for
one session before committing it to config.

22
00:01:11,173 --> 00:01:15,336
Once it's on, the terminal shows a side
conversation beside the main chat.

23
00:01:16,277 --> 00:01:19,739
Version 0.168.0 introduced that layout.

24
00:01:20,519 --> 00:01:24,002
Version 0.169.0 added tabs to it.

25
00:01:24,782 --> 00:01:29,946
So as of 0.169.0, the workspace supports
multiple side chat tabs,

26
00:01:30,386 --> 00:01:32,928
and you can switch between them with the
keyboard or the mouse.

27
00:01:33,648 --> 00:01:39,532
The changelog credits that to pull
requests 59784, 60152 and

28
00:01:39,652 --> 00:01:40,713
60181.

29
00:01:41,445 --> 00:01:42,667
Layout controls are simple.

30
00:01:43,027 --> 00:01:45,349
You drag the divider to resize the two
panes.

31
00:01:45,890 --> 00:01:50,635
And you press leader z to zoom the focused
pane, so one conversation fills the

32
00:01:50,655 --> 00:01:50,975
screen.

33
00:01:51,936 --> 00:01:53,497
Press it again, and the split comes back.

34
00:01:54,879 --> 00:01:59,664
That zoom matters more than it sounds,
because a split terminal gets cramped fast

35
00:01:59,684 --> 00:02:00,505
when you're reading a diff.

36
00:02:01,280 --> 00:02:03,802
Now the part I think is the real headline.

37
00:02:04,282 --> 00:02:05,063
Persistence.

38
00:02:05,823 --> 00:02:09,606
Saved local side chats can be reopened
after you restart Codex.

39
00:02:10,267 --> 00:02:14,169
A side conversation no longer disappears
with the terminal session that created it.

40
00:02:14,830 --> 00:02:17,712
So that scratchpad where you worked out a
log parsing approach,

41
00:02:17,812 --> 00:02:21,435
or had a library explained to you, is
still there tomorrow.

42
00:02:22,255 --> 00:02:24,157
The condition is in the word local.

43
00:02:24,757 --> 00:02:27,059
Only saved local side chats reopen.

44
00:02:27,479 --> 00:02:28,440
Don't assume more than that.

45
00:02:29,092 --> 00:02:30,813
Why does it matter in practice?

46
00:02:32,594 --> 00:02:34,836
The side chat is its own conversation.

47
00:02:35,036 --> 00:02:40,740
So a throwaway question, say explaining an
unfamiliar library or drafting a helper

48
00:02:40,800 --> 00:02:43,501
regex, lives there instead of in your main
thread.

49
00:02:44,402 --> 00:02:45,603
That's the point of the split.

50
00:02:46,203 --> 00:02:49,745
Your main turn keeps running, and the main
conversation doesn't fill up with

51
00:02:49,805 --> 00:02:50,326
detours.

52
00:02:52,007 --> 00:02:55,229
I'd frame that isolation as the design
intent of a separate chat,

53
00:02:55,309 --> 00:02:57,931
rather than something with measured token
numbers behind it,

54
00:02:58,231 --> 00:02:59,772
because the changelog doesn't give any.

55
00:03:00,487 --> 00:03:02,588
Caveats, and there are a few.

56
00:03:03,689 --> 00:03:07,831
First, it's opt-in, so nothing changes
until you set the flag,

57
00:03:08,091 --> 00:03:10,172
and flagged features can change.

58
00:03:11,232 --> 00:03:15,534
Second, tabs need 0.169.0 or later.

59
00:03:15,534 --> 00:03:21,517
On 0.168.0 you only get the single side
pane with the divider and zoom.

60
00:03:22,858 --> 00:03:26,760
Third, the tab shortcuts aren't spelled
out in the changelog.

61
00:03:26,860 --> 00:03:30,481
So check what your build offers before you
build muscle memory around them,

62
00:03:31,002 --> 00:03:33,403
and mouse clicking works fine in the
meantime.

63
00:03:34,283 --> 00:03:36,244
And fourth, screen space.

64
00:03:36,865 --> 00:03:41,367
It's a split view, so give it a wide
window, and lean on leader z when it gets

65
00:03:41,407 --> 00:03:41,687
tight.

66
00:03:42,342 --> 00:03:43,323
A good first test.

67
00:03:43,664 --> 00:03:48,629
Turn the flag on, start a long task in the
main chat, open a side chat next to it,

68
00:03:48,789 --> 00:03:50,190
and ask something unrelated.

69
00:03:50,711 --> 00:03:51,952
Then open a second tab.

70
00:03:52,853 --> 00:03:57,358
Then quit Codex, relaunch, and check that
your saved local side chats reopen.

71
00:03:57,858 --> 00:04:00,882
That one restart check tells you whether
it fits your workflow.

72
00:04:01,633 --> 00:04:06,117
A few smaller things from 0.169.0 worth
knowing.

73
00:04:06,878 --> 00:04:12,582
First, the plan handoff fix, pull request
60763.

74
00:04:12,582 --> 00:04:17,806
When you pick Yes, clear context and
implement, the fresh session now gets the full

75
00:04:17,907 --> 00:04:18,827
approved plan.

76
00:04:19,428 --> 00:04:23,631
And if the handoff fails, your current
session stays open, so the plan isn't lost.

77
00:04:24,612 --> 00:04:25,533
That's one I'm glad about.

78
00:04:26,175 --> 00:04:29,140
Second, the agent command center now has
search.

79
00:04:29,781 --> 00:04:33,727
You can find older tasks by name, prompt
preview, or working directory.

80
00:04:34,247 --> 00:04:38,894
That's pull request 60286, and it helps if
you run a lot of parallel sessions.

81
00:04:39,697 --> 00:04:44,424
Third, in the full screen transcript
there's a setting called Collapse turn details.

82
00:04:45,025 --> 00:04:48,610
It folds completed activity beneath each
prompt, answers stay visible,

83
00:04:48,990 --> 00:04:50,593
and tool output is still searchable.

84
00:04:50,833 --> 00:04:53,176
So long sessions get much easier to scan.

85
00:04:54,010 --> 00:04:58,954
And fourth, in the terminal report editor,
Ctrl and S saves a diagnostic ZIP

86
00:04:59,114 --> 00:05:01,175
locally, even when uploads are disabled.

87
00:05:02,156 --> 00:05:08,160
One more for scripts: codex exec keeps
project config and MCP servers disabled in

88
00:05:08,301 --> 00:05:14,525
untrusted directories, and you pass dash
dash trust to codex exec or codex review to

89
00:05:14,605 --> 00:05:15,886
save trust explicitly.

90
00:05:17,407 --> 00:05:18,148
That's the episode.

91
00:05:18,588 --> 00:05:20,750
Go flip that flag, and I'll catch you
tomorrow.

