1
00:00:00,099 --> 00:00:04,539
Before we dive in, a quick thanks to
Jellypod for making our daily show possible.

2
00:00:05,179 --> 00:00:09,319
Now, if you are like me, you are
constantly jumping between tools when you build.

3
00:00:09,920 --> 00:00:13,799
You write code in Cursor, you bounce over
to Claude Code in your terminal,

4
00:00:14,340 --> 00:00:17,539
and then you try to bring it all back
together in Codex CLI.

5
00:00:18,239 --> 00:00:22,959
But until this week, doing that was, well,
it was a total mess for your session

6
00:00:23,019 --> 00:00:23,359
history.

7
00:00:23,757 --> 00:00:25,938
Oh, it, it was awful.

8
00:00:26,577 --> 00:00:32,178
Every single time you ran an import, it
would just drop duplicate threads all over

9
00:00:32,218 --> 00:00:33,017
your database.

10
00:00:33,617 --> 00:00:38,418
You ended up with like, seven identical
looking conversation fragments for one

11
00:00:38,477 --> 00:00:39,577
refactoring session.

12
00:00:40,155 --> 00:00:45,034
Right, because the database did not know
that the session you were importing was the

13
00:00:45,154 --> 00:00:47,454
exact same session you imported an hour
ago.

14
00:00:48,135 --> 00:00:53,854
But Codex CLI version 0.147.0 fixes this
completely.

15
00:00:54,534 --> 00:01:01,194
They added source aware session parsers
under pull request 36356 and pull request

16
00:01:01,414 --> 00:01:02,834
35623.

17
00:01:03,614 --> 00:01:09,214
Now, the system tracks external session
UUIDs, timestamps, and your working

18
00:01:09,254 --> 00:01:11,754
directory metadata, your cwd path.

19
00:01:12,191 --> 00:01:17,811
So when you run codex import or use that
interactive slash import command in the

20
00:01:17,851 --> 00:01:21,391
terminal, what actually happens to the
database under the hood?

21
00:01:21,787 --> 00:01:27,708
It performs an in place delta sync right
on your existing state dot db records

22
00:01:27,787 --> 00:01:29,467
inside the dot codex directory.

23
00:01:30,208 --> 00:01:34,807
So instead of spawning duplicate threads,
it updates the existing record.

24
00:01:34,887 --> 00:01:39,708
It keeps your original thread titles, it
preserves your connector bindings,

25
00:01:39,767 --> 00:01:45,128
and it synchronizes changes to imported
Claude and Cursor conversations without

26
00:01:45,187 --> 00:01:46,147
creating duplicates.

27
00:01:46,567 --> 00:01:49,607
That exact behavior is a lifesaver.

28
00:01:50,127 --> 00:01:55,428
I was actually testing this exact scenario
two days ago while tracking down a multi

29
00:01:55,548 --> 00:01:59,747
day refactoring bug across Cursor and my
imported sessions in Codex.

30
00:02:00,407 --> 00:02:07,147
Before 0.147.0, I had to sift through
those seven separate conversation fragments

31
00:02:07,427 --> 00:02:09,607
just to find where a prompt failed.

32
00:02:09,727 --> 00:02:15,467
Now, you run slash import, and it just
updates the existing history seamlessly.

33
00:02:15,947 --> 00:02:17,347
It is clean.

34
00:02:17,848 --> 00:02:20,627
And that is only half of what landed in
this release.

35
00:02:21,247 --> 00:02:28,128
The other massive addition in version
0.147.0 is support for importing Cursor

36
00:02:28,187 --> 00:02:29,567
managed skills.

37
00:02:29,628 --> 00:02:36,347
Under pull request 36361, Codex now
automatically ingests your dot cursor

38
00:02:36,388 --> 00:02:39,587
slash rules files during the import
process.

39
00:02:40,421 --> 00:02:45,522
Wait, so it converts those Cursor prompt
rules into native Codex skills?

40
00:02:46,241 --> 00:02:48,002
How does it handle context limits?

41
00:02:48,432 --> 00:02:53,253
It converts those Cursor managed
instructions into native host skills directly,

42
00:02:53,793 --> 00:02:57,312
while staying strictly within your defined
context budget limits.

43
00:02:58,112 --> 00:03:02,773
But there is an important nuance you have
to keep in mind if you rely heavily on

44
00:03:02,912 --> 00:03:04,513
custom editor integrations.

45
00:03:04,902 --> 00:03:06,083
What kind of nuance?

46
00:03:06,462 --> 00:03:11,063
Like if a rule depends on VS Code buttons
or GUI triggers?

47
00:03:11,717 --> 00:03:12,617
Exactly that.

48
00:03:13,198 --> 00:03:18,797
If your Cursor rules depend on VS Code
graphical interface hooks or specific editor

49
00:03:18,898 --> 00:03:23,878
state, Codex cannot trigger those visual
IDE actions inside your terminal.

50
00:03:24,557 --> 00:03:30,058
Instead, Codex translates them into system
prompt instructions and tool schemas that

51
00:03:30,097 --> 00:03:32,657
get evaluated right before permission
checks run.

52
00:03:33,109 --> 00:03:39,269
Okay, so the logic carries over into your
terminal prompt, even if the editor UI

53
00:03:39,309 --> 00:03:43,130
button itself does not exist in the CLI
environment.

54
00:03:43,189 --> 00:03:43,829
That makes sense.

55
00:03:44,670 --> 00:03:48,089
What about safety and quality of life
updates in this build?

56
00:03:48,599 --> 00:03:51,259
They put in some really nice security
polish.

57
00:03:51,919 --> 00:03:58,779
Under pull requests 36893 and 36908, Codex
now automatically

58
00:03:58,899 --> 00:04:03,139
redacts bearer tokens and secret keys from
displayed command items,

59
00:04:03,739 --> 00:04:09,319
so you do not accidentally leak API keys
in your terminal scrollback or logs.

60
00:04:10,914 --> 00:04:15,234
As someone who has accidentally shown a
bearer token on a stream before,

61
00:04:15,614 --> 00:04:16,375
thank you for that.

62
00:04:17,114 --> 00:04:20,534
Did they fix that weird input lockup in
Ghostty terminal too?

63
00:04:21,132 --> 00:04:21,573
Yes!

64
00:04:22,032 --> 00:04:28,692
Pull requests 35649 and 36834 resolved
those TUI focus

65
00:04:28,793 --> 00:04:33,872
bugs that used to freeze input queues in
Ghostty during Model Context Protocol

66
00:04:33,992 --> 00:04:34,452
startup.

67
00:04:35,152 --> 00:04:36,912
Everything stays responsive now.

68
00:04:37,546 --> 00:04:39,407
That really brings it all together.

69
00:04:40,066 --> 00:04:45,286
When you combine secret redaction and TUI
stability with the ability to import

70
00:04:45,406 --> 00:04:50,446
Cursor managed skills and synchronize
changes to imported Claude and Cursor

71
00:04:50,507 --> 00:04:57,386
conversations without creating duplicates,
Codex CLI becomes a true stateful hub for

72
00:04:57,507 --> 00:04:58,687
cross tool development.

73
00:04:59,121 --> 00:04:59,881
Absolutely.

74
00:05:00,381 --> 00:05:04,381
Alright, that is the quick breakdown for
0.147.0.

75
00:05:04,942 --> 00:05:07,462
Go update your CLI and happy coding.