WEBVTT 00:00:00.000 --> 00:00:02.459 Imagine texting your computer from a busy coffee 00:00:02.459 --> 00:00:04.639 shop to do your job. Right, while you're just 00:00:04.639 --> 00:00:06.620 waiting for your drink. You eventually return 00:00:06.620 --> 00:00:09.720 home to find the work completely finished. It's 00:00:09.720 --> 00:00:12.179 honestly kind of wild to think about. There's 00:00:12.179 --> 00:00:14.619 absolutely no movie magic happening here today. 00:00:15.500 --> 00:00:19.780 Beat, this is a reality as of March 2026. Yeah, 00:00:19.800 --> 00:00:22.980 it's totally real. Welcome to our deep dive. 00:00:23.120 --> 00:00:25.879 We're unpacking Anthropic's newly released Claw 00:00:25.879 --> 00:00:28.039 Dispatch Research Preview. Thanks for having 00:00:28.039 --> 00:00:30.410 me. It essentially turns your smartphone into 00:00:30.410 --> 00:00:33.450 a universal remote control. You can command a 00:00:33.450 --> 00:00:36.130 massive desktop brain from absolutely anywhere. 00:00:36.369 --> 00:00:39.649 It's a huge shift for complex desktop AI workflows. 00:00:39.969 --> 00:00:42.270 We'll explore why this finally solves those terrible 00:00:42.270 --> 00:00:45.509 DIY agent headaches. And we'll see what this 00:00:45.509 --> 00:00:47.689 means for the future of asynchronous work. Let's 00:00:47.689 --> 00:00:50.350 start by unpacking the core shift happening here. 00:00:50.490 --> 00:00:53.490 For years, we basically treated AI like a smart 00:00:53.490 --> 00:00:56.149 search engine. You typed a detailed prompt and 00:00:56.149 --> 00:00:58.429 you just sat there waiting. Exactly. That is 00:00:58.429 --> 00:01:00.890 synchronous work, and it requires your full attention. 00:01:01.130 --> 00:01:03.810 You are completely tethered to an active browser 00:01:03.810 --> 00:01:06.430 window. If you close the tab, the whole process 00:01:06.430 --> 00:01:09.030 died. Now we're completely moving to asynchronous 00:01:09.030 --> 00:01:11.629 AI models. You don't wait for a chatbot response 00:01:11.629 --> 00:01:14.450 anymore at all. You simply delegate a highly 00:01:14.450 --> 00:01:18.010 complex job to an agent. Beat. And you just walk 00:01:18.010 --> 00:01:20.640 away and live your life. Claude Dispatch just 00:01:20.640 --> 00:01:24.840 officially launched on March 17th, 2026. It's 00:01:24.840 --> 00:01:27.340 currently available for Macs and Pro tier subscribers. 00:01:27.780 --> 00:01:30.219 Yeah, it's starting on Mac OS for this early 00:01:30.219 --> 00:01:33.099 release phase. Windows support is actively rolling 00:01:33.099 --> 00:01:36.319 out in later scheduled phases. The whole concept 00:01:36.319 --> 00:01:39.260 bridges your mobile app with your desktop. It 00:01:39.260 --> 00:01:41.079 connects directly to something called Claude 00:01:41.079 --> 00:01:43.840 Cowork. Claude Cowork lives directly on your 00:01:43.840 --> 00:01:47.150 actual physical desktop computer. This introduces 00:01:47.150 --> 00:01:49.569 a very specific word we need to focus on. We 00:01:49.569 --> 00:01:52.329 really need to define what agentic actually means. 00:01:52.549 --> 00:01:54.430 Let's take a quick second to properly define 00:01:54.430 --> 00:01:57.409 that. AI taking multi -step actions without you 00:01:57.409 --> 00:01:59.930 supervising every single step. That's a perfect 00:01:59.930 --> 00:02:02.170 definition. It's like having a tireless intern 00:02:02.170 --> 00:02:04.129 sitting at your desk while you're out running 00:02:04.129 --> 00:02:08.509 errands. Whoa, imagine texting, scrape 200 leads 00:02:08.509 --> 00:02:11.430 from an airport and the spreadsheet is just waiting 00:02:11.430 --> 00:02:13.740 for you at home. It's a fundamental change in 00:02:13.740 --> 00:02:16.699 how we mentally process work. You aren't just 00:02:16.699 --> 00:02:19.099 getting a simple paragraph of generated text 00:02:19.099 --> 00:02:21.580 anymore. You're receiving a completely finished 00:02:21.580 --> 00:02:24.819 deliverable safely stored on your drive. Think 00:02:24.819 --> 00:02:27.360 about the immense mental freedom that actually 00:02:27.360 --> 00:02:30.039 gives you. Why does the computer have to stay 00:02:30.039 --> 00:02:32.020 awake if I'm using my phone? Because the phone 00:02:32.020 --> 00:02:34.319 is just the remote control here. The desktop 00:02:34.319 --> 00:02:37.159 is the actual brain doing the heavy lifting locally. 00:02:37.479 --> 00:02:40.389 So the phone gives orders. But your awake computer 00:02:40.389 --> 00:02:43.530 does the actual sweating. Right. And that distinction 00:02:43.530 --> 00:02:45.770 is incredibly important to grasp completely. 00:02:46.110 --> 00:02:48.110 Let's clearly separate the remote control from 00:02:48.110 --> 00:02:50.710 the desktop engine. People might easily get confused 00:02:50.710 --> 00:02:53.169 by the two different names. Dispatch is simply 00:02:53.169 --> 00:02:55.969 the mobile control layer you use. It's just the 00:02:55.969 --> 00:02:57.930 interface on your phone sending the initial commands. 00:02:58.210 --> 00:03:00.689 Right. And co -work is the actual desktop engine 00:03:00.689 --> 00:03:03.530 doing the real work. That engine is what accesses 00:03:03.530 --> 00:03:06.370 your local computer files directly. it uses saved 00:03:06.370 --> 00:03:08.409 skills and connects to professional business 00:03:08.409 --> 00:03:11.550 tools think of mcp connectors for your external 00:03:11.550 --> 00:03:15.169 software apps yeah those are crucial they allow 00:03:15.169 --> 00:03:17.830 co -work to interact with complex third -party 00:03:17.830 --> 00:03:20.930 platforms directly it can easily integrate with 00:03:20.930 --> 00:03:23.810 notion or google sheets it can even connect directly 00:03:23.810 --> 00:03:26.849 into your private github repositories that opens 00:03:26.849 --> 00:03:29.330 up massive workflow possibilities for developers 00:03:29.330 --> 00:03:31.689 wait people will assume their phone is doing 00:03:31.689 --> 00:03:34.500 the scraping We need to be clear that the phone 00:03:34.500 --> 00:03:37.219 is doing zero processing here. Absolutely zero 00:03:37.219 --> 00:03:40.259 processing whatsoever. The phone simply passes 00:03:40.259 --> 00:03:42.819 the text message over to the desktop. Let's look 00:03:42.819 --> 00:03:45.360 at three specific real -world use cases right 00:03:45.360 --> 00:03:48.379 now. First up is lead scraping on demand from 00:03:48.379 --> 00:03:51.580 absolutely anywhere. You literally text, scrape 00:03:51.580 --> 00:03:54.930 200 agency owners in California. And maybe you 00:03:54.930 --> 00:03:57.789 add a filter for teams under 50 people. The specific 00:03:57.789 --> 00:04:00.069 task instantly hits your local desktop machine. 00:04:00.490 --> 00:04:02.909 CoWork basically opens a hidden browser window 00:04:02.909 --> 00:04:05.069 in the background. It actually navigates the 00:04:05.069 --> 00:04:06.969 complex search results completely automatically 00:04:06.969 --> 00:04:10.110 for you. It reviews the pages and parses the 00:04:10.110 --> 00:04:12.849 data cleanly. Then it formats everything perfectly 00:04:12.849 --> 00:04:16.389 into a spreadsheet. Exactly. Minutes later, structured 00:04:16.389 --> 00:04:18.870 data comes right back to your phone. The entire 00:04:18.870 --> 00:04:21.310 cycle happens without you ever touching a laptop. 00:04:21.660 --> 00:04:24.120 It's kind of amazing to watch it work. Data gathering 00:04:24.120 --> 00:04:26.720 is merely step one of real professional work. 00:04:26.860 --> 00:04:29.699 The second practical use case involves heavy 00:04:29.699 --> 00:04:32.759 inbox management tasks. Claude safely reviews 00:04:32.759 --> 00:04:35.040 your inbox and filters low priority messages 00:04:35.040 --> 00:04:37.860 automatically. It highlights the specific emails 00:04:37.860 --> 00:04:40.620 that actually matter most to you. Then it drafts 00:04:40.620 --> 00:04:43.779 replies based on your past writing habits. Heavy 00:04:43.779 --> 00:04:46.740 email users can easily save hours. every single 00:04:46.740 --> 00:04:48.839 day you just trigger this from your phone during 00:04:48.839 --> 00:04:51.500 a busy commute you arrive in an inbox that's 00:04:51.500 --> 00:04:55.040 already perfectly organized two sec silence you 00:04:55.040 --> 00:04:57.399 just review the drafts and hit send on them it's 00:04:57.399 --> 00:05:00.120 a massive time saver for business owners the 00:05:00.120 --> 00:05:02.300 third example from the guide is creative thumbnail 00:05:02.300 --> 00:05:05.000 generation you can text a youtube link directly 00:05:05.000 --> 00:05:07.600 to co -work it recreates the thumbnail using 00:05:07.600 --> 00:05:10.360 a saved local creative skill You're triggering 00:05:10.360 --> 00:05:13.100 multi -step creative tasks remotely from your 00:05:13.100 --> 00:05:15.040 pocket. All three of these workflows share the 00:05:15.040 --> 00:05:17.540 exact same structure. They involve multiple steps 00:05:17.540 --> 00:05:20.819 that usually require a computer locally. Dispatch 00:05:20.819 --> 00:05:23.319 completely removes that physical limitation from 00:05:23.319 --> 00:05:26.540 the entire equation. What happens if a task requires 00:05:26.540 --> 00:05:29.360 multiple different applications at once? Cowork 00:05:29.360 --> 00:05:32.379 automatically spins up specific subagents. They 00:05:32.379 --> 00:05:35.540 safely handle parallel or nested tasks entirely 00:05:35.540 --> 00:05:38.259 locally on your machine. It spawns many workers 00:05:38.259 --> 00:05:40.379 on your desktop to juggle different apps at the 00:05:40.379 --> 00:05:43.170 same time. That's exactly how this system architecture 00:05:43.170 --> 00:05:45.470 is designed. It sounds completely seamless on 00:05:45.470 --> 00:05:48.029 the surface right now. But anyone who tried building 00:05:48.029 --> 00:05:50.769 AI agents knows the actual truth. Oh, yeah. The 00:05:50.769 --> 00:05:53.410 underlying reality was usually a nightmare. DIY 00:05:53.410 --> 00:05:55.810 agent stacks traditionally suffered from three 00:05:55.810 --> 00:05:59.350 major operational flaws. They were fragile, incredibly 00:05:59.350 --> 00:06:02.509 insecure, and highly expensive to run. Small 00:06:02.509 --> 00:06:04.470 configuration changes would break your workflows 00:06:04.470 --> 00:06:07.149 completely unexpectedly. Fixing them took more 00:06:07.149 --> 00:06:09.329 patience than most people actually have. The 00:06:09.329 --> 00:06:11.089 security aspect was always particularly concerning 00:06:11.089 --> 00:06:14.709 for businesses. DIY setups often required exposing 00:06:14.709 --> 00:06:17.399 your highly private... API keys. You were leaking 00:06:17.399 --> 00:06:20.660 credentials into loosely managed community cloud 00:06:20.660 --> 00:06:23.339 environments? It was an absolute nightmare for 00:06:23.339 --> 00:06:25.180 enterprise security teams. Cowork completely 00:06:25.180 --> 00:06:27.379 fixes this by running in an isolated virtual 00:06:27.379 --> 00:06:30.160 machine. It's a secure digital sandbox isolated 00:06:30.160 --> 00:06:32.800 entirely from your main system. You control exactly 00:06:32.800 --> 00:06:36.100 which files and applications Claude safely accesses. 00:06:36.160 --> 00:06:38.680 There is absolutely no silent access allowed 00:06:38.680 --> 00:06:41.600 in this system. Why is silent access such a massive 00:06:41.600 --> 00:06:44.050 deal breaker for business? Because businesses 00:06:44.050 --> 00:06:47.250 cannot risk AI hallucinating and deleting important 00:06:47.250 --> 00:06:51.129 files. It requires explicit allow or deny prompts 00:06:51.129 --> 00:06:53.569 for sensitive files. Nothing gets touched without 00:06:53.569 --> 00:06:56.810 your direct, explicit user approval. That added 00:06:56.810 --> 00:06:59.689 friction is a totally intentional, secure design 00:06:59.689 --> 00:07:02.790 choice. It solves the cloud leak problem by keeping 00:07:02.790 --> 00:07:05.860 the brain local. Then we really have to consider 00:07:05.860 --> 00:07:08.540 the massive cost argument. DIY stacks suffered 00:07:08.540 --> 00:07:11.259 from a massive open -ended token bleed issue. 00:07:11.579 --> 00:07:13.860 Every message and sub -agent invocation cost 00:07:13.860 --> 00:07:16.720 you direct API tokens. A background task might 00:07:16.720 --> 00:07:20.060 easily eat $100 overnight. I still wrestle with 00:07:20.060 --> 00:07:22.220 burning through API credits late at night on 00:07:22.220 --> 00:07:24.259 broken scripts. It's an incredibly frustrating 00:07:24.259 --> 00:07:27.439 experience for anyone. Building DIY stacks feels 00:07:27.439 --> 00:07:31.279 like stacking Lego blocks of data over a bottomless 00:07:31.279 --> 00:07:34.639 pit of API costs. That's a very accurate way 00:07:34.639 --> 00:07:37.459 to describe the old method because every tiny 00:07:37.459 --> 00:07:40.980 subtask triggers a brand new API call. A simple 00:07:40.980 --> 00:07:43.660 loop error can drain your wallet incredibly quickly. 00:07:43.899 --> 00:07:46.300 Dispatch completely solves this with a highly 00:07:46.300 --> 00:07:48.819 predictable subscription model. It basically 00:07:48.819 --> 00:07:51.279 changes the taxi meter into an unlimited bus 00:07:51.279 --> 00:07:54.139 pass. You get much better system stability and 00:07:54.139 --> 00:07:57.100 full cost visibility. Doesn't a complex workflow 00:07:57.100 --> 00:07:59.860 still consume massive amounts of compute? Yes. 00:07:59.959 --> 00:08:02.639 Anthropic admits multi -step agents use heavy 00:08:02.759 --> 00:08:05.160 processing. That's exactly why it requires a 00:08:05.160 --> 00:08:08.399 paid tier, but your cost remains totally capped. 00:08:08.579 --> 00:08:10.879 Anthropic eats the heavy processing costs while 00:08:10.879 --> 00:08:13.100 keeping your monthly bill totally predictable. 00:08:13.339 --> 00:08:15.579 Predictability matters way more than marginal 00:08:15.579 --> 00:08:17.779 cost differences here. We are going to take a 00:08:17.779 --> 00:08:20.319 brief pause right here. Stick around. We'll be 00:08:20.319 --> 00:08:22.680 right back. Insert placeholder for the sponsor 00:08:22.680 --> 00:08:24.620 read here. And we're back to the discussion. 00:08:24.899 --> 00:08:27.759 We need to move from theory into immediate practical 00:08:27.759 --> 00:08:31.319 action. How can you actually deploy this powerful 00:08:31.319 --> 00:08:33.980 system today? Let's briefly walk through the 00:08:33.980 --> 00:08:36.500 actual data routing loop. The process starts 00:08:36.500 --> 00:08:39.039 right inside your mobile phone app interface. 00:08:39.399 --> 00:08:41.720 The message safely routes to your desktop co 00:08:41.720 --> 00:08:44.379 -work session directly. The desktop runs the 00:08:44.379 --> 00:08:46.799 necessary skills and active sub -agents locally. 00:08:47.120 --> 00:08:49.480 It completes the designated work locally on your 00:08:49.480 --> 00:08:51.700 physical machine. Then it naturally returns the 00:08:51.700 --> 00:08:54.519 final completed results to your phone. The initial 00:08:54.519 --> 00:08:56.960 setup really only takes about five minutes total. 00:08:57.360 --> 00:09:00.080 First, you simply update both your desktop and 00:09:00.080 --> 00:09:02.500 mobile apps. Then you just open the co -work 00:09:02.500 --> 00:09:05.019 tab on your desktop app. Inside that interface, 00:09:05.259 --> 00:09:07.940 you'll find the dedicated dispatch icon. You 00:09:07.940 --> 00:09:10.740 just scan the QR code to pair your devices. It 00:09:10.740 --> 00:09:13.100 creates a very simple, secure bridge between 00:09:13.100 --> 00:09:15.980 them quickly. But there's a massive point of 00:09:15.980 --> 00:09:18.600 failure to mention here. It's step five in the 00:09:18.600 --> 00:09:21.059 guide we're reviewing today. Your computer's 00:09:21.059 --> 00:09:23.460 sleep settings are the biggest potential hurdle. 00:09:23.720 --> 00:09:26.360 Right, and this specific issue catches absolutely 00:09:26.360 --> 00:09:29.639 everyone off guard. If your laptop goes to sleep, 00:09:30.039 --> 00:09:32.899 the workflow completely dies. Anthropic states 00:09:32.899 --> 00:09:35.139 this directly in their official support documentation 00:09:35.139 --> 00:09:38.799 online. Claude cannot continue the work if the 00:09:38.799 --> 00:09:41.000 machine sleeps physically. You must keep your 00:09:41.000 --> 00:09:42.960 machine awake for long background workflows. 00:09:43.340 --> 00:09:45.179 Now there's a really smart trick for advanced 00:09:45.179 --> 00:09:48.639 tech users. This is specifically useful for existing 00:09:48.639 --> 00:09:51.840 cloud code power users. You can easily reuse 00:09:51.840 --> 00:09:54.799 your existing IDE workflow coding skills. It's 00:09:54.799 --> 00:09:57.279 a dedicated programming environment where software 00:09:57.279 --> 00:09:59.480 developers write code. You bring them directly 00:09:59.480 --> 00:10:01.799 inside the new co -work interface seamlessly. 00:10:02.220 --> 00:10:04.159 You don't have to rebuild your automations from 00:10:04.159 --> 00:10:06.320 scratch again. It basically becomes a mobile 00:10:06.320 --> 00:10:09.809 control layer. for real desktop automation. Do 00:10:09.809 --> 00:10:11.889 I need to repair my phone with a new QR code 00:10:11.889 --> 00:10:14.110 every time I leave the house? No, you really 00:10:14.110 --> 00:10:16.309 don't. The connection stays active persistently 00:10:16.309 --> 00:10:18.549 in the background after that first setup. Scan 00:10:18.549 --> 00:10:21.309 the code once and your phone is permanently tethered 00:10:21.309 --> 00:10:24.009 to your desktop agent. Exactly. It becomes a 00:10:24.009 --> 00:10:26.490 permanent secure link to your workspace. Let's 00:10:26.490 --> 00:10:28.330 zoom out and look at the macro technological 00:10:28.330 --> 00:10:30.669 shift. Yeah. How are we actually interacting 00:10:30.669 --> 00:10:33.500 with our computers now? Dispatch brings agentic 00:10:33.500 --> 00:10:35.679 workflows directly to non -technical everyday 00:10:35.679 --> 00:10:38.659 users. It accomplishes this securely and without 00:10:38.659 --> 00:10:42.059 massive API billing surprises. It's perfect for 00:10:42.059 --> 00:10:44.539 professionals running repeated workflows or daily 00:10:44.539 --> 00:10:46.980 pipelines. Freelancers and operators can trigger 00:10:46.980 --> 00:10:49.620 their heavy tasks remotely now. We're seeing 00:10:49.620 --> 00:10:52.320 three major themes signaling the technological 00:10:52.320 --> 00:10:55.940 future. First, we're seeing truly persistent 00:10:55.940 --> 00:10:59.590 digital AI workspaces emerging. Second, There's 00:10:59.590 --> 00:11:01.970 growing memory for your complex recurring daily 00:11:01.970 --> 00:11:05.450 tasks. Third, we have seamless mobile to desktop 00:11:05.450 --> 00:11:08.730 continuity from absolutely anywhere. The AI is 00:11:08.730 --> 00:11:11.009 no longer just a basic textual chat bot. You 00:11:11.009 --> 00:11:12.789 don't just open it for a quick factual answer. 00:11:12.929 --> 00:11:16.009 It operates as a persistent, continuously running 00:11:16.009 --> 00:11:18.730 virtual digital worker. It bridges the gap between 00:11:18.730 --> 00:11:21.509 mobile freedom. and desktop power. You don't 00:11:21.509 --> 00:11:23.330 need to be highly technical to use it. You don't 00:11:23.330 --> 00:11:25.549 need to be incredibly tolerant to financial risk. 00:11:25.669 --> 00:11:28.169 That's the real magic of this specific software 00:11:28.169 --> 00:11:31.169 release. It democratizes access to incredibly 00:11:31.169 --> 00:11:33.590 powerful background automation tools safely. 00:11:33.850 --> 00:11:36.070 It's viable for serious business environments 00:11:36.070 --> 00:11:39.250 because of the security controls. I want to leave 00:11:39.250 --> 00:11:41.710 you with a final thought today. Two sec silence. 00:11:42.720 --> 00:11:45.779 Our computers can now complete hours -long tasks 00:11:45.779 --> 00:11:47.980 in the background. While we're just walking in 00:11:47.980 --> 00:11:50.039 the park with our phones. What does the definition 00:11:50.039 --> 00:11:53.120 of a workday even look like a year from now? 00:11:53.399 --> 00:11:56.740 Are we managing tools or are we managing digital 00:11:56.740 --> 00:11:59.240 employees? That is the absolute most important 00:11:59.240 --> 00:12:01.500 question right now. We encourage you to update 00:12:01.500 --> 00:12:04.720 your desktop app today. Try delegating one really 00:12:04.720 --> 00:12:07.139 painful recurring task this afternoon. See if 00:12:07.139 --> 00:12:09.000 this asynchronous loop actually works for you. 00:12:09.100 --> 00:12:11.059 Thanks for joining us on this fascinating deep 00:12:11.059 --> 00:12:11.360 dive.