WEBVTT 00:00:00.000 --> 00:00:02.960 You know, most people are stuck using AI as a 00:00:02.960 --> 00:00:05.759 simple chat box. You just kind of copy and paste 00:00:05.759 --> 00:00:08.060 text back and forth constantly. Yeah, you ask 00:00:08.060 --> 00:00:10.859 one single question and you get one simple answer. 00:00:11.099 --> 00:00:15.259 It feels incredibly limiting. And honestly, it's 00:00:15.259 --> 00:00:17.539 quite tiring to manage. Well, today we're moving 00:00:17.539 --> 00:00:19.640 way past that single chat box. We're going to 00:00:19.640 --> 00:00:22.699 manage a full automated AI team instead. They 00:00:22.699 --> 00:00:25.519 actually work directly inside your computer folders 00:00:25.519 --> 00:00:28.519 alongside you. Exactly. So welcome to another 00:00:28.519 --> 00:00:31.339 deep dive for you, the learner. We're exploring 00:00:31.339 --> 00:00:33.740 the seven layers of Claude co -work today. We 00:00:33.740 --> 00:00:36.320 start from basic setup and reach full automation 00:00:36.320 --> 00:00:38.840 eventually. It really feels exactly like building 00:00:38.840 --> 00:00:41.759 a new house from scratch. You build a solid floor, 00:00:42.020 --> 00:00:44.920 then your walls, and finally a roof. We're basically 00:00:44.920 --> 00:00:47.079 building your entire AI house together today. 00:00:47.280 --> 00:00:50.060 But before we build anything, we absolutely need 00:00:50.060 --> 00:00:52.600 a blueprint. Let's examine the permanent brain 00:00:52.600 --> 00:00:55.119 of your new workspace. Right, because most people 00:00:55.119 --> 00:00:58.240 simply copy text into a browser tab today. When 00:00:58.240 --> 00:01:01.380 you close that tab, the AI forgets absolutely 00:01:01.380 --> 00:01:03.420 everything. The underlying context window just 00:01:03.420 --> 00:01:06.239 gets wiped completely clean every time. Exactly. 00:01:06.700 --> 00:01:09.400 Claude Cowork fundamentally changes this extremely 00:01:09.400 --> 00:01:12.340 frustrating process. But you absolutely need 00:01:12.340 --> 00:01:15.120 the desktop app for this to work. You navigate 00:01:15.120 --> 00:01:18.019 directly over to the Cowork tab on your screen. 00:01:18.159 --> 00:01:20.659 You have to allow the AI to see your files. It 00:01:20.659 --> 00:01:22.719 actually touches the local files on your machine 00:01:22.719 --> 00:01:24.680 directly. So it doesn't just talk about your 00:01:24.680 --> 00:01:28.040 work theoretically. It actually executes the 00:01:28.040 --> 00:01:30.560 work right inside your local folders. Yeah, and 00:01:30.560 --> 00:01:32.400 that brings us to the most important foundation 00:01:32.400 --> 00:01:36.299 layer. You need to create a keloy -day .md file 00:01:36.299 --> 00:01:39.219 right away. This file anchors the underlying 00:01:39.219 --> 00:01:42.000 context window of the model. It acts as a permanent 00:01:42.000 --> 00:01:45.280 system prompt for your workspace. So the AI constantly 00:01:45.280 --> 00:01:47.599 reads this file in the background, invisibly, 00:01:48.079 --> 00:01:50.319 because long conversations usually make an AI 00:01:50.319 --> 00:01:52.280 forget its original purpose. Yeah, we call that 00:01:52.280 --> 00:01:54.719 specific problem prompt drift in the industry. 00:01:54.900 --> 00:01:56.939 It loses the thread after too many back and forth 00:01:56.939 --> 00:01:59.560 messages. I still wrestle with prompt drift myself. 00:02:01.160 --> 00:02:03.599 It's incredibly frustrating when the tone suddenly 00:02:03.599 --> 00:02:06.939 changes mid -project. Right, completely. So this 00:02:06.939 --> 00:02:09.580 file keeps the AI completely focused forever. 00:02:09.939 --> 00:02:12.039 Like, imagine starting a brand new handmade candle 00:02:12.039 --> 00:02:14.740 business. You want to sell exactly 100 candles 00:02:14.740 --> 00:02:17.590 a month. And your tone should always be professional, 00:02:17.830 --> 00:02:20.889 but very friendly. You also prefer writing really 00:02:20.889 --> 00:02:24.150 short, clear emails to customers. I might even 00:02:24.150 --> 00:02:27.129 add that I completely hate using emojis. And 00:02:27.129 --> 00:02:29.370 I'd tell it to always check my math, too. The 00:02:29.370 --> 00:02:32.030 point is, you never have to repeat your background 00:02:32.030 --> 00:02:35.129 information again. The more rules you establish 00:02:35.129 --> 00:02:38.270 now, the less you fix later. This persistent 00:02:38.270 --> 00:02:40.710 memory. is the big secret most people totally 00:02:40.710 --> 00:02:43.789 miss. Definitely. But a memory is useless if 00:02:43.789 --> 00:02:46.849 the workspace itself is totally chaotic. That 00:02:46.849 --> 00:02:49.370 introduces the massive challenge of file organization 00:02:49.370 --> 00:02:51.830 and structure. Instead of manually clicking to 00:02:51.830 --> 00:02:55.110 create folders, you just ask. Right. The AI is 00:02:55.110 --> 00:02:57.310 actually better at organizing complex folders 00:02:57.310 --> 00:03:00.129 than we are. It understands software ontology 00:03:00.129 --> 00:03:02.409 and optimal file structures deeply. But what 00:03:02.409 --> 00:03:04.710 if my existing filing system is highly specific? 00:03:04.909 --> 00:03:07.400 Won't an AI just, you know... Scramble everything 00:03:07.400 --> 00:03:09.599 up. Well, no, it actually reads your file names 00:03:09.599 --> 00:03:11.979 to understand your logic first. Yeah. It analyzes 00:03:11.979 --> 00:03:14.360 the existing patterns before suggesting any new 00:03:14.360 --> 00:03:16.979 changes. So it might suggest a dedicated customer 00:03:16.979 --> 00:03:19.360 feedback folder for you. Yeah, or it could suggest 00:03:19.360 --> 00:03:21.479 an inventory spreadsheet for your daily stock. 00:03:21.599 --> 00:03:23.620 And you just agree and the folders appear inside 00:03:23.620 --> 00:03:25.060 your directory. You don't have to right click 00:03:25.060 --> 00:03:27.120 or name anything yourself. It can even organize 00:03:27.120 --> 00:03:30.280 an old folder that is a total mess. It reads 00:03:30.280 --> 00:03:32.539 the scattered file names and perfectly groups 00:03:32.539 --> 00:03:34.919 them. Which saves so much time compared to dragging 00:03:34.919 --> 00:03:38.009 files by hand. But I know you might have a little 00:03:38.009 --> 00:03:41.050 anxiety here. How do we stop the AI from forgetting 00:03:41.050 --> 00:03:44.930 these rules tomorrow? The CLIUDMD file acts as 00:03:44.930 --> 00:03:47.509 a permanent automatic memory for your folder. 00:03:47.830 --> 00:03:50.009 Okay, so we have a perfect memory and great digital 00:03:50.009 --> 00:03:53.169 organization now. How do we ensure the work doesn't 00:03:53.169 --> 00:03:55.629 sound completely robotic? Right, because most 00:03:55.629 --> 00:03:58.349 people get a generic draft and spend hours fixing 00:03:58.349 --> 00:04:01.009 it. We obviously want to avoid that exact trap 00:04:01.009 --> 00:04:03.849 entirely. This requires fundamentally shifting 00:04:03.849 --> 00:04:07.610 how you assign a specific role. Tell the AI it 00:04:07.610 --> 00:04:09.870 is your senior business manager immediately. 00:04:10.530 --> 00:04:13.009 Yeah, role -playing shifts the probability distribution 00:04:13.009 --> 00:04:15.789 of the text generation. It stops sounding like 00:04:15.789 --> 00:04:18.649 a generic robot instantly. That's the real secret. 00:04:18.759 --> 00:04:21.680 Let's look at replying to a tough customer complaint. 00:04:22.800 --> 00:04:25.100 You find the complaint inside your newly organized 00:04:25.100 --> 00:04:28.199 feedback folder. You simply tell the AI to offer 00:04:28.199 --> 00:04:32.000 a 10 % discount. It apologizes perfectly and 00:04:32.000 --> 00:04:34.899 automatically saves the brand new reply. It saves 00:04:34.899 --> 00:04:37.240 the document directly into your local outbox 00:04:37.240 --> 00:04:40.620 folder. Exactly. There is absolutely no manual 00:04:40.620 --> 00:04:43.259 copy and pasting required anymore. And the professional 00:04:43.259 --> 00:04:45.420 consistency just builds up naturally over time. 00:04:45.639 --> 00:04:48.199 If you used a specific legal phrase yesterday, 00:04:48.459 --> 00:04:50.420 it remembers perfectly. Everything looks like 00:04:50.420 --> 00:04:52.620 it came from the exact same human being. So we 00:04:52.620 --> 00:04:54.639 have accurate text that actually sounds like 00:04:54.639 --> 00:04:58.139 our brand now. But doing this one file at a time 00:04:58.139 --> 00:05:01.160 remains a huge bottleneck. Right. How do we scale 00:05:01.160 --> 00:05:03.680 this operation without losing that distinct quality? 00:05:03.720 --> 00:05:05.720 Well, this requires fundamentally rethinking 00:05:05.720 --> 00:05:07.920 how an artificial intelligence processes work. 00:05:08.500 --> 00:05:11.199 Usually an AI model does only one thing at a 00:05:11.199 --> 00:05:13.540 time. But Claude Cowork lets you run multiple 00:05:13.540 --> 00:05:16.459 complex operations simultaneously instead. Exactly. 00:05:16.779 --> 00:05:18.959 Let's define that AI term for our listeners clearly. 00:05:19.480 --> 00:05:21.779 Some agents are mini AI workers that handle small 00:05:21.779 --> 00:05:24.240 pieces of a larger task. Perfect definition. 00:05:24.509 --> 00:05:27.329 When you assign a big task, it breaks it into 00:05:27.329 --> 00:05:30.529 smaller pieces. It deploys an independent mini 00:05:30.529 --> 00:05:34.029 -AI for each individual piece. This completely 00:05:34.029 --> 00:05:36.329 changes the bottleneck of waiting for sequential 00:05:36.329 --> 00:05:39.420 tasks. Normally, AI is a single chef trying to 00:05:39.420 --> 00:05:42.000 cook everything sequentially. But sub -agents 00:05:42.000 --> 00:05:44.860 are like hiring five sous chefs to work perfectly 00:05:44.860 --> 00:05:47.399 simultaneously. Let's say you're planning a three 00:05:47.399 --> 00:05:50.500 -day trip to Tokyo. Right, so Agent 1 vigorously 00:05:50.500 --> 00:05:52.699 researches the best local food options. Right, 00:05:52.959 --> 00:05:55.839 and Agent 2 looks up the best historical museums. 00:05:56.279 --> 00:05:59.160 Well, Agent 3... plans out your complex public 00:05:59.160 --> 00:06:01.819 transport routes perfectly. They all work simultaneously 00:06:01.819 --> 00:06:04.100 to get the massive job done fast. You actually 00:06:04.100 --> 00:06:06.720 see small transparent boxes appearing on your 00:06:06.720 --> 00:06:08.839 screen. Each box represents a completely different 00:06:08.839 --> 00:06:11.259 working agent thinking live. Yeah, you see one 00:06:11.259 --> 00:06:13.699 agent actively searching the web for fresh information. 00:06:14.019 --> 00:06:16.639 Another agent is simultaneously drafting a formatted 00:06:16.639 --> 00:06:19.620 file on your computer. So one task no longer 00:06:19.620 --> 00:06:22.899 blocks the next task from starting. Whoa! Imagine 00:06:22.899 --> 00:06:24.860 scaling to five or six smart assistants running 00:06:24.860 --> 00:06:27.769 parallel at once. two -sex silence. But does 00:06:27.769 --> 00:06:30.449 doing tasks all at once lower the overall quality? 00:06:30.750 --> 00:06:33.810 No, subagents act independently, maintaining 00:06:33.810 --> 00:06:36.689 total focus on their specific tasks. Okay, so 00:06:36.689 --> 00:06:39.329 we have multiple digital chefs cooking in our 00:06:39.329 --> 00:06:42.329 local kitchen. What happens if a subagent starts 00:06:42.329 --> 00:06:45.009 going down the wrong path? Yeah, sometimes an 00:06:45.009 --> 00:06:47.290 eager assistant might research the wrong thing 00:06:47.290 --> 00:06:50.240 entirely. In most traditional tools, you have 00:06:50.240 --> 00:06:53.420 to hit stop and start over. Which obviously wastes 00:06:53.420 --> 00:06:56.079 processing tokens and absolutely ruins your daily 00:06:56.079 --> 00:06:59.620 momentum. Exactly. But here, you use the steering 00:06:59.620 --> 00:07:02.319 bubble to correct its path smoothly. Meaning 00:07:02.319 --> 00:07:05.100 you can easily talk to agents while they're actively 00:07:05.100 --> 00:07:07.319 working. Right. You never have to start the entire 00:07:07.319 --> 00:07:10.300 complex task over again. It's exactly like cooking 00:07:10.300 --> 00:07:12.199 with a friend in real life. You just look over 00:07:12.199 --> 00:07:15.019 and politely say, hey. Less sold. Yeah. So if 00:07:15.019 --> 00:07:18.279 an agent starts looking for very expensive luxury 00:07:18.279 --> 00:07:20.920 hotels, you click the floating bubble and ask 00:07:20.920 --> 00:07:23.079 for cheap ones instead. And you don't need to 00:07:23.079 --> 00:07:25.399 write a long, overly polite letter. Just give 00:07:25.399 --> 00:07:28.259 a very quick note to change the research parameters. 00:07:28.439 --> 00:07:30.740 So the agent hears you and adjusts its active 00:07:30.740 --> 00:07:32.620 workflow immediately. Right. I always tell new 00:07:32.620 --> 00:07:34.620 users to look right under the hood. Because you 00:07:34.620 --> 00:07:36.660 can click and see exactly what they are typing 00:07:36.660 --> 00:07:39.160 internally. And understanding how they think 00:07:39.160 --> 00:07:41.620 helps you give much better instructions tomorrow. 00:07:41.790 --> 00:07:45.089 This system shows you everything and never hides 00:07:45.089 --> 00:07:47.769 the actual work. That transparency helps you 00:07:47.769 --> 00:07:50.370 become a significantly better boss to your digital 00:07:50.370 --> 00:07:52.850 team. Absolutely. But these agents are currently 00:07:52.850 --> 00:07:56.670 trapped inside your local file system. What happens 00:07:56.670 --> 00:07:58.790 if they need ingredients from the outside world? 00:07:59.000 --> 00:08:01.759 Like checking your real -world schedule or reading 00:08:01.759 --> 00:08:04.540 an external database. We finally bring those 00:08:04.540 --> 00:08:07.339 external tools in by using specialized plugins. 00:08:07.519 --> 00:08:09.480 Wait, let's define that exact concept for our 00:08:09.480 --> 00:08:12.180 listeners clearly. Plugins are digital bridges 00:08:12.180 --> 00:08:15.300 connecting your AI to outside tools like Gmail. 00:08:15.699 --> 00:08:18.600 Exactly. There are over 35 different reliable 00:08:18.600 --> 00:08:21.240 plugins you can use today. You simply type a 00:08:21.240 --> 00:08:24.000 backslash to easily access that integration menu. 00:08:24.199 --> 00:08:26.600 So you can quickly connect Google Calendar and 00:08:26.600 --> 00:08:28.920 your business Gmail account. Yeah, and then the 00:08:28.920 --> 00:08:31.319 AI can logically see when you're actually busy. 00:08:31.639 --> 00:08:34.259 It can help you find time for a very important 00:08:34.259 --> 00:08:36.960 client meeting. It can even aggressively remind 00:08:36.960 --> 00:08:40.019 you of an upcoming strict deadline. I use this 00:08:40.019 --> 00:08:42.720 heavily for my own weekly podcast planning. Oh 00:08:42.720 --> 00:08:45.429 nice! Yeah, you prompt the AI to critically check 00:08:45.429 --> 00:08:47.669 your tasks folder first. And it looks at your 00:08:47.669 --> 00:08:49.529 connected calendar for the upcoming work week. 00:08:49.649 --> 00:08:52.289 Then it writes a comprehensive summary and automatically 00:08:52.289 --> 00:08:54.690 emails it to you. Which saves you from constantly 00:08:54.690 --> 00:08:56.929 jumping between three different browser tabs. 00:08:57.629 --> 00:09:00.289 Everything happens smoothly inside one single 00:09:00.289 --> 00:09:03.309 unified desktop screen. Hmm. But are we forced 00:09:03.309 --> 00:09:05.750 to connect all our personal apps at once? No, 00:09:05.789 --> 00:09:08.570 you manually pick and install only the specific 00:09:08.570 --> 00:09:12.409 plugins you want. Got it. Midroll sponsor, Read 00:09:12.409 --> 00:09:15.090 Placeholder. So we've connected outside tools 00:09:15.090 --> 00:09:18.669 and guided our dynamic digital team. How do we 00:09:18.669 --> 00:09:20.850 finally step back and let the system run itself? 00:09:21.190 --> 00:09:23.409 This brings us directly to the holy grail of 00:09:23.409 --> 00:09:26.330 total automation. This officially turns you from 00:09:26.330 --> 00:09:29.590 an AI worker into a real boss. You can easily 00:09:29.590 --> 00:09:31.730 create a ghost worker for your scheduled tasks. 00:09:31.929 --> 00:09:34.090 Yeah, this ghost worker runs quietly in the background 00:09:34.090 --> 00:09:36.690 all the time. It is extremely hardworking and 00:09:36.690 --> 00:09:39.289 very quiet. Like, imagine waking up to find a 00:09:39.289 --> 00:09:41.809 finished data report in your email. Exactly, 00:09:41.870 --> 00:09:43.690 and you didn't have to click a single button 00:09:43.690 --> 00:09:45.549 to generate it. You don't have to remind the 00:09:45.549 --> 00:09:48.250 AI to work every morning. You just set a daily 00:09:48.250 --> 00:09:51.690 or weekly execution schedule once. And the AI 00:09:51.690 --> 00:09:54.090 automatically tackles the boring, repetitive 00:09:54.090 --> 00:09:56.750 tasks without your supervision. You don't even 00:09:56.750 --> 00:09:59.409 need to open your laptop screen anymore. It handles 00:09:59.409 --> 00:10:02.210 the mundane tasks that drain your energy every 00:10:02.210 --> 00:10:05.710 day, which completely frees your brain for significantly 00:10:05.710 --> 00:10:08.909 more important strategic thinking. Having a reliable 00:10:08.909 --> 00:10:11.309 system that runs automatically makes your life 00:10:11.309 --> 00:10:13.669 much easier. You never need to worry about forgetting 00:10:13.669 --> 00:10:16.429 a weekly analytics report. Because the AI already 00:10:16.429 --> 00:10:19.129 generated exactly at the specific time you picked. 00:10:19.409 --> 00:10:21.769 Right. But we know automation can feel a little 00:10:21.769 --> 00:10:24.529 scary at first. Yeah, I can see listeners worrying 00:10:24.529 --> 00:10:27.549 about an unsupervised robot writing emails. That 00:10:27.549 --> 00:10:29.470 sounds like a massive corporate liability at 00:10:29.470 --> 00:10:32.009 first glance. Can the ghost worker accidentally 00:10:32.009 --> 00:10:35.509 send bad emails directly to clients? Draft mode 00:10:35.509 --> 00:10:38.250 holds messages safely until you manually approve 00:10:38.250 --> 00:10:40.730 and send them. So the AI does the hard parts 00:10:40.730 --> 00:10:43.990 like reading and complex writing, but then it 00:10:43.990 --> 00:10:46.490 safely leaves the finished email in your drafts 00:10:46.490 --> 00:10:48.909 folder. Exactly. Instead of sending it right 00:10:48.909 --> 00:10:51.090 away, it patiently waits for human approval. 00:10:51.669 --> 00:10:54.250 You only need 10 seconds to quickly review and 00:10:54.250 --> 00:10:58.409 hit send. It literally saves 90 % of your valuable 00:10:58.409 --> 00:11:00.919 daily time. And it also keeps your professional 00:11:00.919 --> 00:11:05.559 work 100 % accurate always. So true. Let's look 00:11:05.559 --> 00:11:07.899 at a few extra tips for advanced power users. 00:11:08.059 --> 00:11:10.019 Right. These are hidden workflow features that 00:11:10.019 --> 00:11:13.399 make a really big difference. You can run multiple 00:11:13.399 --> 00:11:16.299 entirely different project sessions at once securely. 00:11:16.700 --> 00:11:19.460 Keep your home finances totally separate from 00:11:19.460 --> 00:11:21.220 your corporate work projects. They basically 00:11:21.220 --> 00:11:23.720 act like completely different locked rooms in 00:11:23.720 --> 00:11:26.460 a big office building. Exactly. They absolutely 00:11:26.460 --> 00:11:29.279 do not mix up or share any sensitive project 00:11:29.279 --> 00:11:31.600 information. You can easily switch between them 00:11:31.600 --> 00:11:33.860 on the left side menu. You can also use self 00:11:33.860 --> 00:11:36.159 -checking agents for much better output quality. 00:11:36.360 --> 00:11:38.620 Yeah, I often ask the digital agents to strictly 00:11:38.620 --> 00:11:41.600 cross -check each other. Agent 1 writes the text 00:11:41.600 --> 00:11:43.799 for your new technical article perfectly. Right, 00:11:43.940 --> 00:11:46.960 Agent 2 reads it and vigorously searches for 00:11:46.960 --> 00:11:50.090 any logical mistakes. It is exactly like having 00:11:50.090 --> 00:11:52.429 a professional editor and writer collaborating 00:11:52.429 --> 00:11:55.970 seamlessly. This makes the final published quality 00:11:55.970 --> 00:11:59.029 significantly higher than standard prompting. 00:11:59.690 --> 00:12:02.190 We have definitely covered a massive amount of 00:12:02.190 --> 00:12:04.669 technical ground today. We truly evolved from 00:12:04.669 --> 00:12:07.470 treating AI as a static Internet search engine. 00:12:08.090 --> 00:12:11.090 We successfully manage a dynamic parallel processing 00:12:11.090 --> 00:12:13.679 digital team instead. They literally live right 00:12:13.679 --> 00:12:15.700 inside your actual computer folders now. Yeah, 00:12:15.840 --> 00:12:18.179 they confidently connect to your calendar and 00:12:18.179 --> 00:12:20.620 successfully draft emails on a schedule. Please 00:12:20.620 --> 00:12:22.539 don't get overwhelmed by all of these advanced 00:12:22.539 --> 00:12:25.240 architectural layers. Just start with layer one 00:12:25.240 --> 00:12:27.659 to keep things very simple initially. Exactly. 00:12:27.740 --> 00:12:29.860 Just open your computer and make a brand new 00:12:29.860 --> 00:12:33.019 local project folder. Create your first Claude 00:12:33.019 --> 00:12:36.360 ID MD file. To clearly see the immediate difference, 00:12:36.679 --> 00:12:39.259 you will visibly see how much smarter the AI 00:12:39.259 --> 00:12:41.539 actually becomes. Absolutely. Imagine what happens 00:12:41.539 --> 00:12:43.620 to your daily workflow going forward from here. 00:12:43.940 --> 00:12:46.799 Your simple desktop folder finally stops being 00:12:46.799 --> 00:12:49.740 a static digital file graveyard. Right. Documents 00:12:49.740 --> 00:12:52.399 don't just go there to silently sit and die forever. 00:12:52.700 --> 00:12:55.879 It becomes a living, self -updating dynamic database 00:12:55.879 --> 00:12:59.519 that constantly grows smarter. It updates automatically 00:12:59.519 --> 00:13:01.980 every single time you receive a new client email. 00:13:02.960 --> 00:13:05.669 Beat. Something to mull over. It really is. Thank 00:13:05.669 --> 00:13:07.509 you for joining us on this deep dive. We will 00:13:07.509 --> 00:13:09.350 definitely see you next time. Out to your own 00:13:09.350 --> 00:13:09.690 music.