1 00:00:00,080 --> 00:00:04,740 So, um, I was messing around with Codex Remote last night, which just hit, 2 00:00:04,800 --> 00:00:06,800 you know, general availability. 3 00:00:06,880 --> 00:00:10,700 And, uh, thanks to Jellypod to help make this daily show a reality. 4 00:00:11,500 --> 00:00:16,760 But, Ethan, I- I- I literally paired my iPhone to my MacBook Pro using just a 5 00:00:16,860 --> 00:00:22,030 single, quick QR code scan, and suddenly I'm running terminal commands from my 6 00:00:22,080 --> 00:00:22,460 couch. 7 00:00:23,220 --> 00:00:24,340 It- it's kind of wild. 8 00:00:25,530 --> 00:00:31,650 Wait, so you're telling me you are actually executing local code on your laptop from 9 00:00:31,750 --> 00:00:33,190 the ChatGPT mobile app? 10 00:00:33,590 --> 00:00:37,880 Like, how does that even work without opening up, like, massive security holes on 11 00:00:37,930 --> 00:00:38,670 your home network? 12 00:00:39,534 --> 00:00:40,384 Right? 13 00:00:40,394 --> 00:00:41,694 That was my first thought too. 14 00:00:42,234 --> 00:00:47,094 You think, oh great, I'm exposing my entire dev environment to the public internet. 15 00:00:47,854 --> 00:00:51,094 But- but they're using this secure relay layer. 16 00:00:51,774 --> 00:00:54,894 So, the mobile app is basically acting as a controller, right? 17 00:00:55,554 --> 00:01:00,434 It sends instructions through the relay, which then talks to the active host agent 18 00:01:00,494 --> 00:01:01,894 on your Mac or PC. 19 00:01:02,574 --> 00:01:08,914 It means your local files, your MCP servers, your credentials-they all stay local. 20 00:01:08,974 --> 00:01:11,654 It doesn't need an open incoming port. 21 00:01:12,722 --> 00:01:12,723 Huh. 22 00:01:12,792 --> 00:01:18,432 So it's more like a- a secure remote control than a full-blown exposure of your port 23 00:01:18,532 --> 00:01:20,132 8080 or whatever. 24 00:01:20,392 --> 00:01:23,172 But, okay, what are people actually using this for? 25 00:01:23,652 --> 00:01:26,602 Is it just a- a party trick, or are there real workflows here? 26 00:01:27,438 --> 00:01:29,508 Well, think about those long-running tasks. 27 00:01:30,138 --> 00:01:34,158 Say you're running a massive test suite or a Docker build that takes, 28 00:01:34,198 --> 00:01:36,018 what, fifteen, twenty minutes? 29 00:01:36,778 --> 00:01:40,928 Instead of sitting at your desk staring at a progress bar, you go make coffee, 30 00:01:41,438 --> 00:01:42,738 go for a walk. 31 00:01:42,798 --> 00:01:47,477 And then boom, you get a mobile push notification on your phone saying, 32 00:01:47,518 --> 00:01:53,117 hey, this task is finished, or, uh, it's asking for permission to run a database 33 00:01:53,198 --> 00:01:53,837 migration. 34 00:01:54,418 --> 00:01:58,158 You can review the diff right there on your phone, tap approve, 35 00:01:58,558 --> 00:01:59,558 and it keeps rolling. 36 00:02:01,114 --> 00:02:06,303 Okay, reviewing diffs on a five-inch screen sounds a little tight, 37 00:02:06,963 --> 00:02:10,423 but I get the appeal for long async tasks. 38 00:02:10,463 --> 00:02:13,663 It's- it's like a pager for your local AI agent. 39 00:02:15,267 --> 00:02:15,856 Exactly! 40 00:02:16,227 --> 00:02:17,397 It's exactly like that. 41 00:02:18,147 --> 00:02:22,267 A pager that actually lets you fix the issue without running back upstairs. 42 00:02:22,946 --> 00:02:25,396 But okay, let's talk about the catch. 43 00:02:25,656 --> 00:02:29,396 Because there is always a catch with these kinds of remote tools, 44 00:02:29,436 --> 00:02:32,716 especially when we're talking about cross-platform stuff. 45 00:02:32,796 --> 00:02:39,266 I was reading the release notes for Codex CLI 0.142.2, which came out alongside 46 00:02:39,316 --> 00:02:45,496 this, and, uh, the host sleep mode rules are incredibly strict. 47 00:02:45,616 --> 00:02:46,096 Oh, yeah. 48 00:02:46,536 --> 00:02:49,366 If your Mac goes to sleep, the party's over. 49 00:02:49,396 --> 00:02:51,076 The connection drops. 50 00:02:51,116 --> 00:02:53,856 And- and on Windows, it gets even weirder, doesn't it? 51 00:02:54,666 --> 00:02:55,106 Yes! 52 00:02:55,506 --> 00:02:59,826 If you're running Windows with foreground Computer Use, the machine has to stay 53 00:02:59,866 --> 00:03:01,246 completely unlocked. 54 00:03:01,566 --> 00:03:03,626 You can't just lock your screen and walk away. 55 00:03:04,226 --> 00:03:10,346 Plus, Windows cannot act as the controller device-only iOS and Android can do that. 56 00:03:10,386 --> 00:03:14,846 And, oh, there's this really annoying bug right now where if you revoke a 57 00:03:14,886 --> 00:03:18,306 connection, it stays cached on the mobile side. 58 00:03:18,366 --> 00:03:22,226 The only way to clear it is a- a complete logout of the ChatGPT app. 59 00:03:23,887 --> 00:03:24,467 Oh, wow. 60 00:03:25,007 --> 00:03:27,607 A full logout just to clear a stale connection? 61 00:03:28,227 --> 00:03:30,946 That- that is definitely a first-generation kind of bug. 62 00:03:31,607 --> 00:03:36,587 But, I suppose for GA, we have to expect some of these operational quirks. 63 00:03:37,441 --> 00:03:38,511 Totally. 64 00:03:38,551 --> 00:03:43,091 But they did pack some decent QOL updates into the actual CLI release, 65 00:03:43,651 --> 00:03:45,181 0.142.2. 66 00:03:45,761 --> 00:03:48,851 They finally enabled MCP tool search by default. 67 00:03:49,758 --> 00:03:50,848 Oh, thank goodness. 68 00:03:51,158 --> 00:03:52,138 Seriously. 69 00:03:52,177 --> 00:03:56,388 Before this, if you had a bunch of Model Context Protocol servers connected, 70 00:03:56,918 --> 00:04:01,918 the CLI would dump every single tool definition into the context window. 71 00:04:01,978 --> 00:04:04,438 It was just a- a massive waste of tokens. 72 00:04:05,078 --> 00:04:07,778 Now it actually searches and pulls them dynamically. 73 00:04:08,620 --> 00:04:14,820 Yes, saving those tokens is huge for latency and, frankly, your API bill. 74 00:04:14,860 --> 00:04:18,080 And they also added system proxy resolution. 75 00:04:18,119 --> 00:04:24,220 There's a new flag, respect_system_proxy, which is a lifesaver if you're behind one 76 00:04:24,260 --> 00:04:28,531 of those corporate VPNs or corporate PAC configurations that usually block this kind 77 00:04:28,530 --> 00:04:28,531 of relay traffic. 78 00:04:28,643 --> 00:04:33,033 Ah, that's a big deal for enterprise devs who want to try this out but are locked 79 00:04:33,063 --> 00:04:34,483 down by corporate IT. 80 00:04:35,283 --> 00:04:40,103 Well, it's a solid step forward for making local agents actually usable on the move. 81 00:04:40,823 --> 00:04:46,163 Definitely check out CLI 0.142.2 if you want to give it a spin. 82 00:04:46,963 --> 00:04:48,223 Alright, that's our quick take. 83 00:04:48,643 --> 00:04:49,443 Catch you next time. 84 00:04:50,850 --> 00:04:50,851 See ya.