WEBVTT 00:00:00.000 --> 00:00:02.980 Well, the reality of 2026 is actually quite stark. 00:00:04.219 --> 00:00:06.700 Beat. The real productivity gap isn't between 00:00:06.700 --> 00:00:09.720 those who use AI and those who don't. It is between 00:00:09.720 --> 00:00:12.720 those who just chat with it and those who architect 00:00:12.720 --> 00:00:15.460 an autonomous digital workforce. That is exactly 00:00:15.460 --> 00:00:17.879 the dividing line. I mean, it changes absolutely 00:00:17.879 --> 00:00:20.399 everything about how we work. Welcome to the 00:00:20.399 --> 00:00:23.199 deep dive. We are really glad you are here. Today, 00:00:23.320 --> 00:00:26.059 our mission is to unpack a comprehensive 2026 00:00:26.059 --> 00:00:28.719 tutorial on this topic. We are exploring the 00:00:28.719 --> 00:00:31.440 multi -layered Claude ecosystem. Okay, let's 00:00:31.440 --> 00:00:34.240 unpack this. We will explore the three distinct 00:00:34.240 --> 00:00:37.500 rooms of this system. We have chat, co -work, 00:00:37.560 --> 00:00:40.060 and code. We will dive into the power add -ons. 00:00:40.179 --> 00:00:42.899 Those are skills, connectors, and plugins. And 00:00:42.899 --> 00:00:44.899 finally, we will show you how to push this AI 00:00:44.899 --> 00:00:46.899 further. It can manipulate your local files. 00:00:46.960 --> 00:00:48.820 You can run automated schedules while you sleep. 00:00:49.079 --> 00:00:51.420 It really is a massive shift in perspective. 00:00:51.740 --> 00:00:53.520 You know, people often treat the system as just 00:00:53.520 --> 00:00:56.000 a single website. You log in, type a question, 00:00:56.140 --> 00:00:58.280 get an answer. But that is fundamentally incorrect. 00:00:58.460 --> 00:01:00.719 It is actually a triple product strategy. Right. 00:01:00.799 --> 00:01:02.539 It's not just a single conversational interface 00:01:02.539 --> 00:01:05.239 anymore. Exactly. Using only the chat window 00:01:05.239 --> 00:01:08.060 is incredibly limiting. It is like buying a massive 00:01:08.060 --> 00:01:11.459 professional toolkit. But then, you only use 00:01:11.459 --> 00:01:14.739 one small screwdriver. You are missing out on 00:01:14.739 --> 00:01:17.859 incredible power. The ecosystem is actually three 00:01:17.859 --> 00:01:20.219 distinct rooms, and they all share the exact 00:01:20.219 --> 00:01:23.579 same underlying brain. But they serve very different 00:01:23.579 --> 00:01:25.739 functional purposes. Yeah, completely different. 00:01:25.859 --> 00:01:28.870 Chat is for fast... transient tasks, you know, 00:01:28.950 --> 00:01:31.849 things under 10 minutes. Cowork is for long -term 00:01:31.849 --> 00:01:34.250 project persistence. It actually remembers things. 00:01:34.709 --> 00:01:37.689 And code is for local software development. But 00:01:37.689 --> 00:01:40.329 here is the critical step for any of this. You 00:01:40.329 --> 00:01:43.150 absolutely must download the desktop application. 00:01:43.329 --> 00:01:45.430 I have to pause you there. Why is the web browser 00:01:45.430 --> 00:01:47.510 not enough anymore? We have been doing everything 00:01:47.510 --> 00:01:49.989 in the cloud for years. What fundamentally changes 00:01:49.989 --> 00:01:52.329 for power users? Well, browsers are limited by 00:01:52.329 --> 00:01:54.450 design. They are walled gardens. They protect 00:01:54.450 --> 00:01:56.349 your computer, which is good for security. But 00:01:56.349 --> 00:01:59.170 the desktop application unlocks agentic features. 00:01:59.510 --> 00:02:01.890 Those are tools letting AI act without constant 00:02:01.890 --> 00:02:04.549 human prompting. The desktop app lets the AI 00:02:04.549 --> 00:02:06.829 interact directly with your file system. It bridges 00:02:06.829 --> 00:02:09.030 the gap between the cloud and your actual machine. 00:02:09.550 --> 00:02:12.569 So real automation needs the desktop app to actually 00:02:12.569 --> 00:02:14.770 touch your local files. Right. And without that, 00:02:14.770 --> 00:02:17.310 you are just talking to a screen. Establishing 00:02:17.310 --> 00:02:20.550 that we need the whole toolkit is step one. Now 00:02:20.550 --> 00:02:22.669 we should look at the most familiar room first. 00:02:23.129 --> 00:02:25.789 We need to uncover its hidden mechanics. That 00:02:25.789 --> 00:02:28.129 brings us to the chat product. This is where 00:02:28.129 --> 00:02:30.629 everyone naturally starts. It is built purely 00:02:30.629 --> 00:02:33.090 for speed and immediate answers. Think of it 00:02:33.090 --> 00:02:36.370 as your everyday workspace. It is highly reactive. 00:02:36.830 --> 00:02:39.289 You draft quick emails here. You summarize uploaded 00:02:39.289 --> 00:02:42.169 PDFs. You can parse dense financial spreadsheets. 00:02:42.530 --> 00:02:45.469 You drop a raw CSV file in, and it reads it instantly. 00:02:45.750 --> 00:02:48.509 But chat has a major structural problem. It forgets. 00:02:48.550 --> 00:02:50.830 Once you start a new conversation, your custom 00:02:50.830 --> 00:02:53.389 instructions vanish. That is exactly why they 00:02:53.389 --> 00:02:56.009 built the project's feature. Projects are fascinating. 00:02:56.330 --> 00:02:58.370 Think of a project as a highly sterile clean 00:02:58.370 --> 00:03:00.770 room. Like a decontamination chamber for your 00:03:00.770 --> 00:03:03.099 data. Precisely. You can uplay your specific 00:03:03.099 --> 00:03:05.979 brand guidelines into this clean room. You establish 00:03:05.979 --> 00:03:08.900 very rigid custom instructions. You might say, 00:03:09.020 --> 00:03:11.879 always use a formal tone and never use emojis. 00:03:12.080 --> 00:03:14.379 And crucially, those rules stay trapped inside 00:03:14.379 --> 00:03:17.500 that specific room. Yes. When you leave that 00:03:17.500 --> 00:03:20.479 project to ask a random question, the main system 00:03:20.479 --> 00:03:23.379 completely forgets those strict rules. It doesn't 00:03:23.379 --> 00:03:26.080 bleed over. It keeps your main chat perfectly 00:03:26.080 --> 00:03:28.860 clean. I have a vulnerable admission here. I 00:03:28.860 --> 00:03:31.539 still wrestle with prompt drift myself. I keep 00:03:31.539 --> 00:03:33.699 forgetting to use projects and losing my custom 00:03:33.699 --> 00:03:36.599 rules. Beat. It just gets messy so fast. Oh, 00:03:36.680 --> 00:03:39.240 we all do it. You start asking about dinner recipes 00:03:39.240 --> 00:03:41.719 in your work thread, suddenly the AI is confused. 00:03:42.159 --> 00:03:44.819 But inside a project, the system also quietly 00:03:44.819 --> 00:03:48.039 builds a background memory file. It learns user 00:03:48.039 --> 00:03:50.180 details over time. It just happens automatically 00:03:50.180 --> 00:03:52.479 behind the scenes. And then we have artifacts. 00:03:52.680 --> 00:03:54.879 This feels like a huge leap forward in the interface. 00:03:55.159 --> 00:03:57.099 Artifacts are essentially visual mini -apps. 00:03:57.099 --> 00:03:59.120 They are built right in your browser cab. Like 00:03:59.120 --> 00:04:01.500 asking it to build an email generator with clickable 00:04:01.500 --> 00:04:03.419 tone buttons. Exactly. Instead of just giving 00:04:03.419 --> 00:04:06.199 you the text of an email, it writes the underlying 00:04:06.199 --> 00:04:09.129 code. Then it renders the interface right there 00:04:09.129 --> 00:04:11.030 on your screen. You can click around and use 00:04:11.030 --> 00:04:14.030 it immediately. But wait, if it is building software, 00:04:14.469 --> 00:04:17.269 how do artifacts differ from actual programs 00:04:17.269 --> 00:04:20.670 installed on my computer? They are entirely temporary. 00:04:20.790 --> 00:04:23.329 They only live inside your current web browser 00:04:23.329 --> 00:04:26.029 tab. They do not save to your local machine at 00:04:26.029 --> 00:04:28.670 all. The moment you close the tab, the interface 00:04:28.670 --> 00:04:31.170 is gone. Got it. Artifacts live in the browser, 00:04:31.370 --> 00:04:34.509 not on your actual hard drive. Correct. So chat 00:04:34.509 --> 00:04:36.970 is perfect for these one -off tasks. But what 00:04:36.970 --> 00:04:39.149 happens when you need the machine to learn? What 00:04:39.149 --> 00:04:42.149 if you do the exact same data entry task every 00:04:42.149 --> 00:04:45.050 single Monday? That is when chat becomes highly 00:04:45.050 --> 00:04:47.149 inefficient. You don't want to type the same 00:04:47.149 --> 00:04:49.410 prompt every week. We need to transition from 00:04:49.410 --> 00:04:52.529 a casual user to a system architect. We need 00:04:52.529 --> 00:04:54.689 repeatable automation. This brings us to the 00:04:54.689 --> 00:04:57.550 power add -ons. Skills, connectors, and plugins. 00:04:57.790 --> 00:05:00.449 These separate the casuals from the professionals. 00:05:00.930 --> 00:05:03.389 Let's start with skills. I like to use the analogy 00:05:03.389 --> 00:05:05.829 of a physical filing cabinet. That is a perfect 00:05:05.829 --> 00:05:09.269 way to visualize it. The AI only reads the detailed 00:05:09.269 --> 00:05:11.949 step -by -step instructions when the specific 00:05:11.949 --> 00:05:14.350 label is called upon. It keeps the whole system 00:05:14.350 --> 00:05:16.629 moving fast. Right. It does not read the entire 00:05:16.629 --> 00:05:18.629 cabinet every single time you say hello. It just 00:05:18.629 --> 00:05:21.269 grabs the one specific file you request. And 00:05:21.269 --> 00:05:25.009 the mechanism to make a skill is remarkably intuitive. 00:05:25.430 --> 00:05:27.449 You do it naturally right in the chat. You just 00:05:27.449 --> 00:05:29.689 run a perfect prompt until it works. Then you 00:05:29.689 --> 00:05:32.910 literally tell the AI, please package these exact 00:05:32.910 --> 00:05:36.389 steps into a reusable skill. It is that simple. 00:05:36.449 --> 00:05:39.430 It writes its own documentation. Next, we have 00:05:39.430 --> 00:05:42.209 connectors. Connectors give the AI actual read 00:05:42.209 --> 00:05:44.569 and write access to other applications. Let's 00:05:44.569 --> 00:05:46.870 break that down so it can read my unread messages. 00:05:47.269 --> 00:05:50.100 Yes. That is a basic read action. Or it can write 00:05:50.100 --> 00:05:52.800 new tasks directly to your digital to -do list. 00:05:53.040 --> 00:05:55.220 That is a write action. It essentially builds 00:05:55.220 --> 00:05:57.699 a bridge from the AI to your existing tools. 00:05:57.860 --> 00:06:00.220 Wait, so if I have a connector reading my inbox 00:06:00.220 --> 00:06:03.740 and a skill drafting replies, do I have to manually 00:06:03.740 --> 00:06:05.759 trigger them both every time? Yeah. Because that 00:06:05.759 --> 00:06:08.240 sounds exhausting. That is exactly why plugins 00:06:08.240 --> 00:06:11.000 exist. Plugins are bundles. They bundle many 00:06:11.000 --> 00:06:13.100 skills and connectors together for entire job 00:06:13.100 --> 00:06:15.759 roles. You use simple slash commands to activate 00:06:15.759 --> 00:06:17.879 them. By typing forward slash skill creator. 00:06:18.079 --> 00:06:20.439 Exactly. You type that command and bypass typing 00:06:20.439 --> 00:06:23.139 long explanations, the AI just interviews you, 00:06:23.220 --> 00:06:25.199 it asks what you want to achieve, and it builds 00:06:25.199 --> 00:06:27.579 the skill automatically. But where are these 00:06:27.579 --> 00:06:29.860 skills permanently stored so they don't vanish? 00:06:31.199 --> 00:06:32.959 You just said chat forgets everything when you 00:06:32.959 --> 00:06:34.819 close the tab. If you make them in normal chat, 00:06:34.839 --> 00:06:37.339 they do disappear. You must save them into your 00:06:37.339 --> 00:06:40.019 dedicated workspace. They live permanently inside 00:06:40.019 --> 00:06:42.980 the Cowork or Code areas. Skills vanish in regular 00:06:42.980 --> 00:06:45.579 chat. They need to be saved in Cowork or Code. 00:06:45.879 --> 00:06:48.839 Exactly. Since these custom skills need a permanent, 00:06:49.139 --> 00:06:52.180 stable home, it is time to transition. We have 00:06:52.180 --> 00:06:54.899 to enter the second room of the ecosystem. This 00:06:54.899 --> 00:06:57.639 room is designed entirely for long -term memory. 00:06:57.939 --> 00:07:00.399 This is Cowork. If chat is a whiteboard you erase 00:07:00.399 --> 00:07:03.560 every day, Cowork is a dedicated office. It is 00:07:03.560 --> 00:07:05.660 about setting up a workspace that remembers your 00:07:05.660 --> 00:07:07.879 decisions from yesterday. The first requirement 00:07:07.879 --> 00:07:10.720 here is purely structural. You absolutely must 00:07:10.720 --> 00:07:13.800 create dedicated, specific, local folders on 00:07:13.800 --> 00:07:16.019 your computer. Like a folder named Q3 Marketing 00:07:16.019 --> 00:07:18.759 Presentation. Yes. No giant catch -all folders. 00:07:18.899 --> 00:07:21.040 Do not just give it access to your entire documents 00:07:21.040 --> 00:07:24.060 folder. That is a massive mistake. The AI needs 00:07:24.060 --> 00:07:26.959 a clear, isolated boundary to read and write 00:07:26.959 --> 00:07:29.800 files safely. And inside that specific folder, 00:07:29.939 --> 00:07:32.240 there is a very critical file. Let's talk about 00:07:32.240 --> 00:07:34.639 how it actually works. You were talking about 00:07:34.639 --> 00:07:37.139 the Claude .md file. This is essentially the 00:07:37.139 --> 00:07:39.639 memory core for your project. When you sleep 00:07:39.639 --> 00:07:41.500 and shut down your computer, the active session 00:07:41.500 --> 00:07:43.980 ends. But the next morning, the system boots 00:07:43.980 --> 00:07:47.579 up and reads that Claude .md file first. It parses 00:07:47.579 --> 00:07:50.459 the text to rebuild its context window. It remembers 00:07:50.459 --> 00:07:53.000 everything from the day before. Two -sec silence. 00:07:53.279 --> 00:07:55.959 Think about how powerful that is. The context 00:07:55.959 --> 00:07:58.040 is perfectly preserved. It knows exactly where 00:07:58.040 --> 00:08:00.980 you left off. And then we add the schedule feature 00:08:00.980 --> 00:08:05.279 into the mix. This turns the A into a true autonomous 00:08:05.279 --> 00:08:07.920 agent. You can set it to run entirely without 00:08:07.920 --> 00:08:11.660 you. Whoa, Pete. Imagine waking up and the AI 00:08:11.660 --> 00:08:13.660 has already checked your calendar, scanned your 00:08:13.660 --> 00:08:16.439 inbox, and drafted a clean 8 a .m. briefing. 00:08:16.720 --> 00:08:19.100 What's fascinating here is the fundamental shift 00:08:19.100 --> 00:08:21.680 in our daily behavior. You are no longer sitting 00:08:21.680 --> 00:08:24.040 down and doing work to create an output. You 00:08:24.040 --> 00:08:26.819 are simply reviewing the AI's multi -step autonomous 00:08:26.819 --> 00:08:29.740 work. It is a profound change in our human relation 00:08:29.740 --> 00:08:32.179 to software. But I have to play devil's advocate 00:08:32.179 --> 00:08:34.379 here. What about the danger of the AI putting 00:08:34.379 --> 00:08:36.980 files in the wrong place? If it is running while 00:08:36.980 --> 00:08:39.299 I sleep, couldn't it mess up my system? That 00:08:39.299 --> 00:08:41.399 comes right back to the folder structure we just 00:08:41.399 --> 00:08:44.440 discussed. Cowork is strictly restricted to the 00:08:44.440 --> 00:08:46.879 specific folder you assign to it. It physically 00:08:46.879 --> 00:08:49.679 cannot wander around your hard drive. That's 00:08:49.679 --> 00:08:52.360 why isolated folders are crucial. It keeps the 00:08:52.360 --> 00:08:55.220 AI from messing up your desktop. Precisely. Control 00:08:55.220 --> 00:08:57.610 the environment and you control the agent. It 00:08:57.610 --> 00:09:00.509 is entirely safe if you set the boundaries. Mid 00:09:00.509 --> 00:09:03.750 -roll sponsor read. Okay, we have covered chat 00:09:03.750 --> 00:09:07.009 and co -work, but there is a ceiling to dragging 00:09:07.009 --> 00:09:09.330 and dropping files. If you actually need to build 00:09:09.330 --> 00:09:11.529 entirely new tools from scratch, you need more 00:09:11.529 --> 00:09:15.500 access. Which leads us to the third room. We 00:09:15.500 --> 00:09:17.940 are entering the most advanced, highly technical 00:09:17.940 --> 00:09:21.620 space. This is building software with code. Claude 00:09:21.620 --> 00:09:23.759 code is a completely different beast. Here the 00:09:23.759 --> 00:09:26.220 AI is no longer contained in a neat browser window. 00:09:26.600 --> 00:09:28.659 It types directly into your computer's terminal. 00:09:29.120 --> 00:09:31.419 Let's clarify how that works. When you give it 00:09:31.419 --> 00:09:33.720 terminal access, you are bypassing the visual 00:09:33.720 --> 00:09:36.480 interface entirely. It is typing raw commands 00:09:36.480 --> 00:09:38.519 directly into your operating system's brain. 00:09:38.919 --> 00:09:43.070 Yes, it is pure text -based execution. Cloud 00:09:43.070 --> 00:09:45.110 Code can install software dependencies locally. 00:09:45.190 --> 00:09:47.809 It can spin up local servers. It can build complex 00:09:47.809 --> 00:09:50.210 programs from scratch. I mean, it is essentially 00:09:50.210 --> 00:09:52.549 a senior engineer sitting inside your machine. 00:09:52.830 --> 00:09:54.929 But you have to choose the brain for this engineer. 00:09:55.049 --> 00:09:58.039 You have to actively select. the model it uses. 00:09:58.559 --> 00:10:00.820 Model selection is absolutely critical here. 00:10:01.159 --> 00:10:03.559 Models are just the specific neural networks 00:10:03.559 --> 00:10:05.980 processing your request. You have three main 00:10:05.980 --> 00:10:08.320 choices depending on the test. Sonnet 4 .6 is 00:10:08.320 --> 00:10:10.600 the first one. Sonnet 4 .6 is your best overall 00:10:10.600 --> 00:10:13.340 choice. It beautifully balances speed and extremely 00:10:13.340 --> 00:10:16.059 high intelligence. Most of the time, for everyday 00:10:16.059 --> 00:10:19.120 coding, you use this. Then there's Opus 4 .6. 00:10:19.299 --> 00:10:21.139 Why wouldn't I just use the smartest one all 00:10:21.139 --> 00:10:24.480 the time? Because Opus 4 .6 is heavy, it is computationally 00:10:24.480 --> 00:10:27.580 expensive, it is noticeably slow, you only deploy 00:10:27.580 --> 00:10:30.120 Opus for incredibly complex, deeply difficult 00:10:30.120 --> 00:10:32.440 logic problems that nothing else can solve. And 00:10:32.440 --> 00:10:36.500 finally, we have Haiku 4 .5. Haiku 4 .5 is incredibly 00:10:36.500 --> 00:10:39.659 fast and light. You use it for simple, repetitive 00:10:39.659 --> 00:10:42.639 tasks like formatting code. It saves energy and 00:10:42.639 --> 00:10:45.620 runs almost instantly. And beautifully, the system 00:10:45.620 --> 00:10:47.600 allows you to switch between these models mid 00:10:47.600 --> 00:10:50.250 -conversation. Now, because this tool writes 00:10:50.250 --> 00:10:52.970 files directly to your hard drive, we have to 00:10:52.970 --> 00:10:55.809 talk about permissions. Giving an AI access to 00:10:55.809 --> 00:10:58.549 my terminal sounds like a cybersecurity nightmare. 00:10:58.789 --> 00:11:01.370 How is this actually safe? Well, it is a valid 00:11:01.370 --> 00:11:04.210 concern. Beginners absolutely must leave permissions 00:11:04.210 --> 00:11:07.350 toggled on. The system will explicitly ask you 00:11:07.350 --> 00:11:09.909 before it runs any command. It pauses and waits 00:11:09.909 --> 00:11:12.370 for your human approval. It is safe because you 00:11:12.370 --> 00:11:14.789 are the gatekeeper. But experts can turn those 00:11:14.789 --> 00:11:17.470 permissions off for pure unhindered speed. That 00:11:17.470 --> 00:11:19.940 seems like a huge risk of accidental file deletion. 00:11:20.240 --> 00:11:22.299 It is a massive risk. If permissions are off, 00:11:22.360 --> 00:11:24.200 it will just execute its own logic. If it makes 00:11:24.200 --> 00:11:26.639 a mistake or misunderstands a prompt, the file 00:11:26.639 --> 00:11:30.080 is simply gone. So should a non -coder ever turn 00:11:30.080 --> 00:11:32.559 those terminal permissions off? Never. The risk 00:11:32.559 --> 00:11:35.759 is simply too high for the average user. Do not 00:11:35.759 --> 00:11:38.340 touch that toggle. Keep permissions on. The speed 00:11:38.340 --> 00:11:40.039 isn't worth accidentally deleting your whole 00:11:40.039 --> 00:11:42.840 project. Right. And there is one more advanced 00:11:42.840 --> 00:11:45.299 feature here we should touch on. Remote control. 00:11:45.980 --> 00:11:48.200 Checking your computer's progress via your phone 00:11:48.200 --> 00:11:51.039 browser. It sounds amazing in theory. It sounds 00:11:51.039 --> 00:11:53.600 great, but practically it has severe limits. 00:11:54.200 --> 00:11:56.919 Your physical computer terminal must stay open. 00:11:57.179 --> 00:11:59.899 Your laptop cannot go to sleep or lose Wi -Fi. 00:12:00.379 --> 00:12:03.320 There is a strict 10 -minute network timeout. 00:12:03.580 --> 00:12:06.659 And frankly, it requires the expensive $100 a 00:12:06.659 --> 00:12:09.259 month max plan. That feels very restrictive for 00:12:09.259 --> 00:12:11.799 an autonomous future. It is restrictive. For 00:12:11.799 --> 00:12:15.120 real, heavy lifting while you're away, a server 00:12:15.120 --> 00:12:17.720 -based agent is the superior alternative. It 00:12:17.720 --> 00:12:20.860 runs entirely in the cloud 24 -7 without relying 00:12:20.860 --> 00:12:23.879 on your physical laptop. If building local software 00:12:23.879 --> 00:12:26.639 via terminal feels too intense, that is completely 00:12:26.639 --> 00:12:28.879 okay. Not everyone needs to be a developer. There 00:12:28.879 --> 00:12:31.340 are much more familiar places to deploy this 00:12:31.340 --> 00:12:33.940 intelligence. Exactly. We are moving beyond the 00:12:33.940 --> 00:12:36.460 desktop application now. We need to weave this 00:12:36.460 --> 00:12:39.080 AI into the mundane tools you already use every 00:12:39.080 --> 00:12:41.169 single day. Let's start with the mobile application. 00:12:41.470 --> 00:12:44.009 The mobile app is excellent for native file access. 00:12:44.269 --> 00:12:47.110 You can upload photos or documents natively stored 00:12:47.110 --> 00:12:48.990 on your phone while you are commuting on the 00:12:48.990 --> 00:12:51.690 train. It seamlessly syncs all that data back 00:12:51.690 --> 00:12:54.029 to your main co -work workspace. And then there 00:12:54.029 --> 00:12:56.950 is the Chrome extension. This has a feature that 00:12:56.950 --> 00:12:59.610 legitimately blew my mind. You're talking about 00:12:59.610 --> 00:13:02.850 the Teach Claude button. Yes. How does a text 00:13:02.850 --> 00:13:06.009 -based AI even do this? You click it. and the 00:13:06.009 --> 00:13:08.570 machine literally watches your mouse movements. 00:13:09.029 --> 00:13:10.970 It watches exactly where you click on a screen. 00:13:11.129 --> 00:13:13.870 It is mapping the DOM elements. Those are the 00:13:13.870 --> 00:13:16.289 structural building blocks of a web page. It 00:13:16.289 --> 00:13:18.669 takes rapid screenshots, maps those elements, 00:13:18.870 --> 00:13:21.090 and translates your X and Y coordinates into 00:13:21.090 --> 00:13:23.629 an executable script. So it learns how to navigate 00:13:23.629 --> 00:13:27.149 complex internal company websites just by observing 00:13:27.149 --> 00:13:29.929 you do it once. It converts your visual human 00:13:29.929 --> 00:13:32.610 actions into a repeatable automated script. It 00:13:32.610 --> 00:13:35.210 is incredible technology. And finally, we have 00:13:35.210 --> 00:13:37.909 Excel integration. We all use spreadsheets. It 00:13:37.909 --> 00:13:39.850 is the universal language of business. Co -opting 00:13:39.850 --> 00:13:42.529 directly into Microsoft Excel gives the AI very 00:13:42.529 --> 00:13:46.029 special localized powers. Imagine a Tuesday morning. 00:13:46.309 --> 00:13:49.129 You drop in raw messy CSV data. What happens? 00:13:49.450 --> 00:13:52.450 It can physically highlight cells. It can write 00:13:52.450 --> 00:13:56.190 complex VO up formulas for you. It can conditionally 00:13:56.190 --> 00:13:59.210 change row colors based on subtle data trends. 00:13:59.509 --> 00:14:01.850 It can generate simple pie charts of your spending 00:14:01.850 --> 00:14:05.639 habits instantly. But how does this Excel integration 00:14:05.639 --> 00:14:08.759 differ from just asking for a formula in chat? 00:14:09.039 --> 00:14:11.200 Well, in chat you get the text. You have to copy 00:14:11.200 --> 00:14:13.559 the formula, open Excel, find the right cell, 00:14:13.600 --> 00:14:16.299 and paste it yourself. The integration does the 00:14:16.299 --> 00:14:19.159 physical work for you. It manipulates the spreadsheet 00:14:19.159 --> 00:14:22.279 directly via an API. It actually executes the 00:14:22.279 --> 00:14:24.159 math and builds the charts right inside your 00:14:24.159 --> 00:14:26.659 spreadsheet. Exactly. It completely removes the 00:14:26.659 --> 00:14:28.639 friction between getting the answer and applying 00:14:28.639 --> 00:14:31.139 the answer. So what does this all mean? If we 00:14:31.139 --> 00:14:33.720 connect this to the bigger picture, We are witnessing 00:14:33.720 --> 00:14:36.879 a profound evolution. We are building complex 00:14:36.879 --> 00:14:39.879 automated systems now. We are using customized 00:14:39.879 --> 00:14:43.000 skills. We are establishing specific local folders. 00:14:43.200 --> 00:14:45.379 We are deploying scheduled agents to do the heavy 00:14:45.379 --> 00:14:48.039 lifting. It is ultimately about buying back your 00:14:48.039 --> 00:14:51.000 own time. By architecting this digital workforce, 00:14:51.460 --> 00:14:55.080 you are saving hours. every single day. You automate 00:14:55.080 --> 00:14:57.980 the routine algorithmic tasks so you can actually 00:14:57.980 --> 00:15:01.779 focus on deeply human important work. But we 00:15:01.779 --> 00:15:04.179 want to encourage you to just start small. Do 00:15:04.179 --> 00:15:07.399 not try to build a massive complex software project 00:15:07.399 --> 00:15:09.580 today. That will just lead to immediate frustration 00:15:09.580 --> 00:15:12.429 and burnout. Start with just one thing. Create 00:15:12.429 --> 00:15:15.690 one isolated project room for a specific client. 00:15:16.029 --> 00:15:19.590 Or package just one repetitive weekly email task 00:15:19.590 --> 00:15:22.429 into a single skill. Take it one highly intentional 00:15:22.429 --> 00:15:24.450 step at a time. It stacks up quickly. You build 00:15:24.450 --> 00:15:26.370 the foundation and the automation goes from there. 00:15:26.490 --> 00:15:27.990 And I want to leave you with one final thought 00:15:27.990 --> 00:15:30.330 to mull over today as you look at your own workflows. 00:15:30.929 --> 00:15:33.629 Two secs silence. If an AI system can now learn 00:15:33.629 --> 00:15:36.350 a complex multi -step task just by watching where 00:15:36.350 --> 00:15:38.850 your mouse clicks on a screen, how long until 00:15:38.850 --> 00:15:40.960 our job description aren't defined by the specific 00:15:40.960 --> 00:15:43.039 software we know how to use, but by the entirely 00:15:43.039 --> 00:15:45.580 new autonomous systems we can imagine building. 00:15:45.860 --> 00:15:46.779 Out T -Row music.