1
00:00:00,280 --> 00:00:05,045
If you run Codex on a remote box over SSH,
you've probably walked away from an

2
00:00:05,065 --> 00:00:09,309
approval prompt and come back twenty
minutes later to find the agent just sitting

3
00:00:09,349 --> 00:00:09,549
there.

4
00:00:10,650 --> 00:00:16,636
Codex CLI 0.168.0, published November 13,
2026, has a fix for that.

5
00:00:17,357 --> 00:00:20,180
And thanks to Jellypod AI for sponsoring
this episode.

6
00:00:20,843 --> 00:00:22,425
The change is one config key.

7
00:00:23,106 --> 00:00:29,872
Under the tui table in your
~/.codex/config.toml, set tui.notification_method

8
00:00:29,872 --> 00:00:33,056
equal to the string osc777.

9
00:00:33,736 --> 00:00:35,918
You can also flip it from the /config
screen.

10
00:00:36,639 --> 00:00:40,103
The pull request is number 59256, if you
want to read the source.

11
00:00:40,800 --> 00:00:42,602
Now, what does it actually do?

12
00:00:43,763 --> 00:00:48,067
Before this, notifications mostly leaned
on desktop system alerts,

13
00:00:48,567 --> 00:00:50,749
audio chimes, or title bar tricks.

14
00:00:51,450 --> 00:00:55,714
Those depend on a notification daemon
running on the same machine as the terminal.

15
00:00:57,495 --> 00:01:02,320
Over SSH, or inside a multiplexer, that
chain often just breaks.

16
00:01:02,988 --> 00:01:07,191
With osc777, Codex doesn't call a desktop
daemon at all.

17
00:01:07,632 --> 00:01:10,474
It writes a terminal escape sequence into
standard output.

18
00:01:11,014 --> 00:01:15,778
The shape is escape, right bracket, 777,
semicolon, notify,

19
00:01:16,298 --> 00:01:20,161
semicolon, a title, semicolon, a body,
then a string terminator.

20
00:01:21,422 --> 00:01:21,743
That's it.

21
00:01:22,223 --> 00:01:25,105
Your terminal emulator reads the stream,
spots the sequence,

22
00:01:25,245 --> 00:01:28,408
and raises a native desktop notification
on your local machine.

23
00:01:29,152 --> 00:01:31,215
And that's why it survives SSH.

24
00:01:31,535 --> 00:01:34,118
The bytes travel down the same connection
as your text.

25
00:01:34,619 --> 00:01:38,323
The terminal on your laptop is the one
interpreting them, so it doesn't matter that

26
00:01:38,403 --> 00:01:41,206
Codex is running on a headless server
three hops away.

27
00:01:41,847 --> 00:01:45,571
The terminals named as supporting it are
Ghostty, Kitty, WezTerm,

28
00:01:45,731 --> 00:01:46,152
and foot.

29
00:01:46,903 --> 00:01:48,464
There's a second improvement tied to this.

30
00:01:49,365 --> 00:01:54,810
Approval notifications sent over OSC 777
show an expanded preview of the command,

31
00:01:55,330 --> 00:01:57,612
and they distinguish between two
situations.

32
00:01:58,332 --> 00:02:01,275
One, the agent is waiting for interactive
terminal input.

33
00:02:01,775 --> 00:02:04,477
Two, it's asking for outbound network
access.

34
00:02:05,338 --> 00:02:09,601
Those need different reactions from you,
and now the notification tells you which

35
00:02:09,741 --> 00:02:11,223
one before you even switch windows.

36
00:02:12,153 --> 00:02:14,436
To set it up, add this to your config.

37
00:02:14,796 --> 00:02:19,502
Under the tui table, notification_method
equals osc777.

38
00:02:20,103 --> 00:02:24,488
Restart Codex, kick off a task that needs
approval, and switch to another window.

39
00:02:25,169 --> 00:02:28,512
If your terminal supports the sequence,
you should get a native alert.

40
00:02:29,360 --> 00:02:32,964
Now the caveats, and there are two worth
knowing.

41
00:02:33,664 --> 00:02:35,226
First, terminal support.

42
00:02:35,766 --> 00:02:41,972
If your emulator doesn't parse OSC 777, it
may silently ignore the sequence.

43
00:02:42,773 --> 00:02:47,377
Or, if passthrough is misconfigured, it
may print the raw escape string into your

44
00:02:47,417 --> 00:02:47,757
screen.

45
00:02:49,519 --> 00:02:49,919
Not pretty.

46
00:02:50,965 --> 00:02:51,966
Second, tmux.

47
00:02:52,567 --> 00:02:55,790
Inside tmux, the escape codes have to
reach the outer terminal,

48
00:02:56,030 --> 00:03:01,916
so you need set -g allow-passthrough on in
your .tmux.conf.

49
00:03:01,916 --> 00:03:05,480
Without it, tmux swallows the sequence and
you're back to missing approvals.

50
00:03:06,100 --> 00:03:10,384
If notifications work outside tmux but not
inside, check that line first.

51
00:03:11,135 --> 00:03:16,044
This also pairs nicely with the split-pane
TUI workspace, the opt-in

52
00:03:16,044 --> 00:03:18,622
features.tui_workspace flag.

53
00:03:19,443 --> 00:03:23,267
With several panes and tabs on screen,
you're less likely to be watching the one

54
00:03:23,267 --> 00:03:23,847
that needs you.

55
00:03:24,488 --> 00:03:27,150
A native notification pulls your attention
to the right one.

56
00:03:27,851 --> 00:03:30,573
That's my interpretation, not something
the release notes claim,

57
00:03:30,693 --> 00:03:31,915
but it's the natural fit.

58
00:03:32,817 --> 00:03:34,819
A few smaller things from the same window.

59
00:03:35,240 --> 00:03:40,405
In 0.169.0, the workspace gets multi-tab
side chats.

60
00:03:40,766 --> 00:03:45,130
You can open several, switch by keyboard
or mouse, and recover local side chats

61
00:03:45,310 --> 00:03:46,492
after restarting Codex.

62
00:03:47,032 --> 00:03:51,176
Those are pull requests 59784 and 60152.

63
00:03:51,847 --> 00:03:55,712
There's a new Collapse turn details toggle
in the full-screen transcript.

64
00:03:57,234 --> 00:04:01,640
It folds completed execution activity
under each prompt, keeps the responses

65
00:04:01,680 --> 00:04:04,243
visible, and tool logs stay searchable.

66
00:04:04,804 --> 00:04:06,687
That's number 60554.

67
00:04:07,362 --> 00:04:12,229
Also, pressing Ctrl+S in the terminal
report editor now creates a local diagnostic

68
00:04:12,329 --> 00:04:14,913
ZIP file, even when remote uploads are
disabled.

69
00:04:15,353 --> 00:04:18,738
That's handy if you're in a locked down
environment and still need to share a bug

70
00:04:18,798 --> 00:04:19,179
report.

71
00:04:19,579 --> 00:04:21,322
That's 60542.

72
00:04:21,907 --> 00:04:26,652
And finally, under Sessions, then Model
providers, you can browse providers and set

73
00:04:26,672 --> 00:04:28,675
the default for new chats right in the
TUI.

74
00:04:29,315 --> 00:04:30,997
That's 59541.

75
00:04:31,798 --> 00:04:35,903
If you work over SSH, try the osc777
setting today.

76
00:04:36,363 --> 00:04:39,687
It's a one line change, and it might save
you a lot of idle agent time.

