1
00:00:00,320 --> 00:00:05,100
So, Jellypod is helping make this daily
show a reality, so thanks to them.

2
00:00:06,260 --> 00:00:12,380
Today is one default that changed in Codex
CLI 0.165.0,

3
00:00:13,100 --> 00:00:14,480
published October 27.

4
00:00:15,480 --> 00:00:19,700
Memory V2 is now the default engine for
freshly initialized profiles.

5
00:00:20,280 --> 00:00:22,820
That's PR 56211.

6
00:00:23,732 --> 00:00:29,932
Back in episode 0.155.0 we covered Memory
V2 as an opt in feature,

7
00:00:30,412 --> 00:00:33,012
with isolated storage and dual write
options.

8
00:00:33,632 --> 00:00:37,952
What's different now is that you don't opt
in anymore, if your profile is new.

9
00:00:38,432 --> 00:00:39,412
And the scope matters.

10
00:00:39,932 --> 00:00:41,712
This applies to fresh profiles.

11
00:00:42,072 --> 00:00:44,472
Existing profiles are not migrated
automatically.

12
00:00:44,972 --> 00:00:48,452
So if you've had Codex installed for
months, nothing flips under you.

13
00:00:49,142 --> 00:00:51,962
Right, and the release notes are scoped
that way too.

14
00:00:52,542 --> 00:00:53,702
Fresh profiles only.

15
00:00:54,682 --> 00:00:58,862
If you want to know which side you're on,
look at whether your profile was created

16
00:00:58,922 --> 00:01:00,642
before or after you updated.

17
00:01:01,390 --> 00:01:05,750
Let's talk about what the engine does,
because it explains why this is a workflow

18
00:01:05,790 --> 00:01:07,290
change and not just a toggle.

19
00:01:08,130 --> 00:01:11,970
Memory V2 doesn't stuff your past
conversations into the system prompt.

20
00:01:12,530 --> 00:01:17,270
It processes them in asynchronous
background sweeps, when sessions go idle.

21
00:01:17,890 --> 00:01:20,570
So the extraction happens while you're
away from the keyboard,

22
00:01:21,070 --> 00:01:24,490
and what persists across sessions are your
patterns and preferences.

23
00:01:25,030 --> 00:01:26,270
The prompt doesn't bloat.

24
00:01:38,958 --> 00:01:40,278
That's the concrete benefit.

25
00:01:41,018 --> 00:01:46,018
Say you tell the agent three sessions in a
row that your integration tests need a

26
00:01:46,078 --> 00:01:51,098
particular environment variable, or that
you never want a certain helper touched.

27
00:01:51,978 --> 00:01:54,738
Without memory, you repeat that every
time.

28
00:01:55,478 --> 00:01:59,298
With it, a later session can recall it
without you pasting it in.

29
00:02:00,057 --> 00:02:00,717
Where does it live?

30
00:02:01,417 --> 00:02:03,997
Locally, under ~/.codex/memories/.

31
00:02:05,157 --> 00:02:06,197
That's on your machine.

32
00:02:06,657 --> 00:02:07,957
And that's a boundary to understand.

33
00:02:08,437 --> 00:02:12,697
It doesn't synchronize across your
teammates, and it doesn't match the memory

34
00:02:12,817 --> 00:02:15,597
settings in ChatGPT Work enterprise
workspaces.

35
00:02:16,237 --> 00:02:20,117
Two engineers on the same repo will have
two different agent memories.

36
00:02:20,910 --> 00:02:22,450
Which is a double edged thing.

37
00:02:23,170 --> 00:02:25,850
It prevents unintended prompt leaks
between people.

38
00:02:26,410 --> 00:02:30,630
But it also means you can't assume a
teammate's agent knows what yours knows.

39
00:02:31,298 --> 00:02:34,898
For control inside a session, there's the
/memories command.

40
00:02:35,358 --> 00:02:40,198
In any active session you use it to toggle
whether the turn reads from or writes to

41
00:02:40,258 --> 00:02:41,278
the local memory store.

42
00:02:41,858 --> 00:02:45,218
So if you're doing something sensitive, or
you're testing a weird experiment you

43
00:02:45,258 --> 00:02:48,298
don't want remembered, turn writing off
for that turn.

44
00:02:48,975 --> 00:02:50,955
And that's worth building as a habit.

45
00:02:51,635 --> 00:02:55,995
Before you paste anything odd into a
session, check /memories.

46
00:02:56,715 --> 00:03:02,235
Then, separately, you can just open
~/.codex/memories/ and read what's in there.

47
00:03:03,055 --> 00:03:03,915
It's local files.

48
00:03:04,435 --> 00:03:05,155
You can inspect them.

49
00:03:05,900 --> 00:03:11,820
Now the second half of PR 56414, which is
importing memories from external agents.

50
00:03:12,460 --> 00:03:17,740
Codex CLI can ingest memory context and
conversation history from other coding

51
00:03:17,900 --> 00:03:21,060
agents, Claude Code and Cursor being the
examples.

52
00:03:21,620 --> 00:03:25,800
The CLI import pulls up to 50
conversations from the last 30 days,

53
00:03:26,160 --> 00:03:27,400
along with project memories.

54
00:03:28,140 --> 00:03:29,680
The impact is on migration.

55
00:03:30,420 --> 00:03:34,080
If you're adopting Codex alongside Claude
Code, or after it,

56
00:03:34,580 --> 00:03:35,560
you don't start from zero.

57
00:03:36,260 --> 00:03:41,000
Repository quirks, architectural patterns,
the preferences you spent weeks teaching

58
00:03:41,060 --> 00:03:43,020
another tool, those can come across.

59
00:03:43,777 --> 00:03:47,457
In practice, you start the import through
the CLI migration flow,

60
00:03:47,857 --> 00:03:51,277
and you do it when you're not inside a
running task or a remote session.

61
00:03:51,857 --> 00:03:52,977
Do it from a clean prompt.

62
00:03:53,537 --> 00:03:57,537
Then, and this is the step people will
skip, review what came across.

63
00:03:57,977 --> 00:04:02,317
Especially tool restrictions, hooks, and
authenticated MCP servers.

64
00:04:02,857 --> 00:04:03,737
Those aren't just notes.

65
00:04:03,957 --> 00:04:07,337
They change what the agent is allowed to
do, or what it can reach.

66
00:04:07,937 --> 00:04:10,097
Two related fixes landed with it.

67
00:04:11,137 --> 00:04:17,837
PR 56462 prevents memory imports from
racing with the background consolidation

68
00:04:18,016 --> 00:04:18,377
engine.

69
00:04:19,297 --> 00:04:19,957
Think about it.

70
00:04:20,997 --> 00:04:25,357
You import a batch while the sweep is
merging memories at the same time.

71
00:04:26,337 --> 00:04:27,557
That's a classic race.

72
00:04:28,637 --> 00:04:32,497
Now the import and the consolidation don't
step on each other.

73
00:04:33,817 --> 00:04:39,937
And PR 56465 adds experimental reads of
thread memory summaries,

74
00:04:40,877 --> 00:04:44,257
so that's early, and I wouldn't build on
it yet.

75
00:04:45,077 --> 00:04:45,637
Caveats.

76
00:04:46,237 --> 00:04:50,897
First, and OpenAI is explicit about this,
memories are a recall layer,

77
00:04:51,237 --> 00:04:52,697
not authoritative policy.

78
00:04:53,217 --> 00:04:58,637
If a rule has to hold for everyone on the
team, it belongs in AGENTS.md or your

79
00:04:58,677 --> 00:05:00,297
repository docs, checked in.

80
00:05:00,817 --> 00:05:02,917
Don't rely on a memory to enforce it.

81
00:05:03,712 --> 00:05:04,912
Second, redaction.

82
00:05:06,052 --> 00:05:11,352
Codex redacts recognized secrets and API
tokens during background consolidation.

83
00:05:12,492 --> 00:05:14,192
Recognized is the key word.

84
00:05:14,912 --> 00:05:15,952
It's not guaranteed.

85
00:05:16,832 --> 00:05:22,512
So before you share a ~/.codex folder, or
attach a snapshot to a bug report,

86
00:05:23,192 --> 00:05:24,892
audit the memory files yourself.

87
00:05:25,833 --> 00:05:27,313
Third, stale context.

88
00:05:27,873 --> 00:05:32,473
A memory captured months ago might
describe a module layout you've since refactored.

89
00:05:32,953 --> 00:05:36,173
The agent may confidently recall something
that's no longer true.

90
00:05:36,773 --> 00:05:39,213
Prune the memory store when you do a big
restructure.

91
00:05:39,633 --> 00:05:43,893
And if you import from another agent,
remember those 30 days of conversations might

92
00:05:43,933 --> 00:05:45,433
include old assumptions too.

93
00:05:46,017 --> 00:05:50,317
A few smaller things in 0.165.0.

94
00:05:51,337 --> 00:05:57,717
PR 56308 adds a repository filter to the
session picker, plus

95
00:05:58,257 --> 00:06:01,137
directory grouping in the agent command
center.

96
00:06:02,357 --> 00:06:06,037
If you run multiple linked worktrees, that
keeps things tidy.

97
00:06:07,093 --> 00:06:13,493
PR 56330 stops queued agent messages from
waking work after an interrupt,

98
00:06:13,953 --> 00:06:18,633
so Ctrl+C actually means stop, or when you
switch to Plan mode.

99
00:06:19,593 --> 00:06:26,293
And PR 56132 cancels remote MCP tool
requests as soon as the local response

100
00:06:26,333 --> 00:06:30,093
futures are dropped, which should cut down
on hung backend requests.

101
00:06:31,113 --> 00:06:33,473
So the practical checklist is short.

102
00:06:34,373 --> 00:06:37,293
Update to 0.165.0.

103
00:06:38,153 --> 00:06:39,953
Know whether your profile is fresh.

104
00:06:40,893 --> 00:06:44,153
Use /memories for per turn control.

105
00:06:45,073 --> 00:06:48,733
Read ~/.codex/memories/ once.

106
00:06:49,373 --> 00:06:52,833
And keep real rules in AGENTS.md.