WEBVTT 00:00:00.000 --> 00:00:02.279 You probably think of Claude as, you know, a 00:00:02.279 --> 00:00:05.639 really smart chatbot, great for summaries, brainstorming 00:00:05.639 --> 00:00:10.259 maybe. But that picture, it's changing a lot. 00:00:10.720 --> 00:00:12.500 Yeah, it's really not just about chatting anymore. 00:00:13.140 --> 00:00:15.839 Picture this. You give it some raw sales numbers, 00:00:15.880 --> 00:00:18.179 maybe just in a text file, and boom, it spits 00:00:18.179 --> 00:00:20.500 out a proper Excel spreadsheet, calculates everything, 00:00:20.620 --> 00:00:24.000 puts in a chart all from one prompt. Yay. And 00:00:24.000 --> 00:00:25.699 that's the shift we're really digging into today. 00:00:26.019 --> 00:00:28.100 From a thing you talk to to something that actually 00:00:28.100 --> 00:00:30.859 does stuff, Welcome to the deep dive. We're going 00:00:30.859 --> 00:00:33.759 to unpack these pretty major updates that are 00:00:33.759 --> 00:00:35.920 pushing Claude right into your workflow, like 00:00:35.920 --> 00:00:39.060 seriously. And if you're building things, managing 00:00:39.060 --> 00:00:41.320 projects, or even just trying to wrangle data 00:00:41.320 --> 00:00:43.740 faster, you want to get a handle on this. We'll 00:00:43.740 --> 00:00:45.679 cover how it tackles real -world scheduling, 00:00:46.159 --> 00:00:48.600 how it can directly create and edit files, these 00:00:48.600 --> 00:00:51.200 new connectors for other apps, and yeah, the 00:00:51.200 --> 00:00:52.979 crucial privacy stuff. There's a deadline involved 00:00:52.979 --> 00:00:55.100 there too. Okay, let's start with that real -world 00:00:55.100 --> 00:00:58.000 integration. Clawdaz, like a super powered personal 00:00:58.000 --> 00:01:00.520 assistant, managing your schedule across different 00:01:00.520 --> 00:01:02.780 phone apps. Yeah. And what's really cool here 00:01:02.780 --> 00:01:05.540 is how it handles multiple steps across different 00:01:05.540 --> 00:01:08.280 tools, calendar, maps, reminders, you name it. 00:01:08.459 --> 00:01:11.239 You make one request, and it sorts out a complex 00:01:11.239 --> 00:01:13.819 task, cuts down on all that app switching we 00:01:13.819 --> 00:01:16.359 constantly do. OK, give me an example, like a 00:01:16.359 --> 00:01:18.700 meeting. Sure. You could just say, schedule a 00:01:18.700 --> 00:01:21.219 4 PM meeting tomorrow at a coffee shop nearby. 00:01:21.689 --> 00:01:24.269 Simple enough, right? But then you add, oh, and 00:01:24.269 --> 00:01:26.849 add a note to bring the project docs. So Quad 00:01:26.849 --> 00:01:29.450 checks your calendar for 4 p .m. If you're booked, 00:01:29.489 --> 00:01:32.790 it might say, hey, how about 4 .30? Then it finds 00:01:32.790 --> 00:01:35.349 coffee shops near you, puts the chosen one in 00:01:35.349 --> 00:01:38.109 the calendar event, adds your note, and even 00:01:38.109 --> 00:01:40.870 sets a 30 -minute reminder on your phone. It's 00:01:40.870 --> 00:01:42.890 juggling multiple things at once. Okay, that's 00:01:42.890 --> 00:01:44.670 pretty slick for a simple meeting. What about 00:01:44.670 --> 00:01:46.849 something more involved, like planning something 00:01:46.849 --> 00:01:48.870 for the weekend? You can definitely scale it 00:01:48.870 --> 00:01:51.700 up. Try this. Plan a picnic with Min this Saturday. 00:01:51.819 --> 00:01:54.900 Am I free between 9 a .m. and noon? Find a park 00:01:54.900 --> 00:01:57.519 nearby that has a big grassy area, send Min the 00:01:57.519 --> 00:02:00.799 invite via email, and create a packing list for 00:02:00.799 --> 00:02:03.640 me in my notes app. Wow, okay. That's checking 00:02:03.640 --> 00:02:06.099 availability, location scouting, communication, 00:02:06.299 --> 00:02:09.300 and task management all from one request. Exactly. 00:02:09.699 --> 00:02:12.060 Calendar, maps, email, notes app. It's coordinating 00:02:12.060 --> 00:02:16.009 across them. So, probing that a bit. How does 00:02:16.009 --> 00:02:18.949 this multi -step capability fundamentally change 00:02:18.949 --> 00:02:21.250 how you interact with the AI? What's the core 00:02:21.250 --> 00:02:24.129 shift? I think fundamentally it elevates the 00:02:24.129 --> 00:02:26.030 AI. It's no longer just fetching information, 00:02:26.210 --> 00:02:28.629 it's actively coordinating tasks across your 00:02:28.629 --> 00:02:31.110 digital life. Yeah, it really transforms it into 00:02:31.110 --> 00:02:35.330 a powerful multi -app personal assistant beat. 00:02:36.409 --> 00:02:39.069 Okay, so if it can manage my schedule and reminders 00:02:39.069 --> 00:02:42.360 that well... What about the actual work associated 00:02:42.360 --> 00:02:44.659 with those meetings? The documents, the data? 00:02:45.240 --> 00:02:47.599 Perfect transition, because that's the next huge 00:02:47.599 --> 00:02:50.360 step. Moving beyond just managing time to actually 00:02:50.360 --> 00:02:52.539 manipulate the work products, we're talking direct 00:02:52.539 --> 00:02:54.960 file creation and editing. Think Word docs, Excel 00:02:54.960 --> 00:02:57.840 sheets, PowerPoint slides, even PDFs right there 00:02:57.840 --> 00:03:00.240 in the chat. Seriously, no more copying and pasting 00:03:00.240 --> 00:03:03.500 stuff back and forth. That's huge. It's not just 00:03:03.500 --> 00:03:06.219 faster. It feels like it could, you know, democratize 00:03:06.219 --> 00:03:08.500 some skills. Like someone who isn't an Excel 00:03:08.500 --> 00:03:10.780 whiz could suddenly generate complex reports. 00:03:10.879 --> 00:03:12.960 That changes things. Totally. Take that Excel 00:03:12.960 --> 00:03:16.139 power. You upload, say, a simple text file, just 00:03:16.139 --> 00:03:18.139 product names, quantity sold. You tell Claude, 00:03:18.240 --> 00:03:21.560 calculate revenue. Product A costs 50 ,000 VND. 00:03:22.039 --> 00:03:25.120 And maybe specify prices for others. And it just... 00:03:24.840 --> 00:03:26.719 Builds the spreadsheet those the whole thing 00:03:26.719 --> 00:03:29.180 it inserts the formula for revenue quantity times 00:03:29.180 --> 00:03:31.659 price Yeah, it calculates the total revenue at 00:03:31.659 --> 00:03:35.539 the bottom and get this It can even put a column 00:03:35.539 --> 00:03:38.659 chart like revenue over time onto a completely 00:03:38.659 --> 00:03:41.659 separate sheet within that same Excel file That's 00:03:41.659 --> 00:03:43.860 structured work without ever opening Excel. Okay. 00:03:44.060 --> 00:03:46.680 What about other formats like word? Similar idea. 00:03:46.960 --> 00:03:48.659 Imagine you have a bunch of messy notes, just 00:03:48.659 --> 00:03:50.439 brain -dumped text about, say, climate change 00:03:50.439 --> 00:03:52.879 impacts in the Mekong Delta. You feed that to 00:03:52.879 --> 00:03:55.020 Claude and ask for a structured essay. It can 00:03:55.020 --> 00:03:57.120 generate a title page, build an automatic table 00:03:57.120 --> 00:03:59.500 of contents, and apply proper heading one, heading 00:03:59.500 --> 00:04:01.599 two styles throughout the document. OK. I'm thinking 00:04:01.599 --> 00:04:03.759 about the hours I've wasted fighting with formatting. 00:04:03.939 --> 00:04:06.960 That sounds amazing. PowerPoint, too. Yep. You 00:04:06.960 --> 00:04:09.280 could give it a longer report document and, say, 00:04:09.780 --> 00:04:12.400 summarize this into a seven -slide presentation 00:04:12.400 --> 00:04:15.939 draft, maybe specify title slide. Goals, tasks, 00:04:16.420 --> 00:04:18.560 results, maybe with a simple chart in there. 00:04:18.959 --> 00:04:22.220 Challenges? Next steps? Thank you. You could 00:04:22.220 --> 00:04:24.699 even suggest a basic design, like a blue and 00:04:24.699 --> 00:04:26.800 white theme. So it's not just content, it's structure 00:04:26.800 --> 00:04:29.379 and basic design as well, and PDFs. Those are 00:04:29.379 --> 00:04:31.279 always tricky. Right. But now, you could point 00:04:31.279 --> 00:04:33.459 it to a specific page in a long PDF, say page 00:04:33.459 --> 00:04:37.470 27 of a 50 page report, and tell it... Extract 00:04:37.470 --> 00:04:40.069 the table called monthly user statistics from 00:04:40.069 --> 00:04:42.889 this page and put that data into a new Excel 00:04:42.889 --> 00:04:45.870 file. It can isolate specific data within a PDF 00:04:45.870 --> 00:04:48.410 and move it. It can even help fill out PDF forms 00:04:48.410 --> 00:04:51.209 now. Whoa, just thinking about that. Imagine 00:04:51.209 --> 00:04:53.350 scaling that. A billion queries where no one 00:04:53.350 --> 00:04:55.329 has to copy, paste, or reformat. The amount of 00:04:55.329 --> 00:04:57.550 friction that removes is massive. Yeah, it's 00:04:57.550 --> 00:04:59.829 a game changer for workflow. So if we boil it 00:04:59.829 --> 00:05:01.930 down, what's the single biggest time saver compared 00:05:01.930 --> 00:05:04.209 to the old way? It seems like skipping all that 00:05:04.209 --> 00:05:06.250 manual formatting and structuring lets you jump 00:05:06.250 --> 00:05:08.889 straight to refining the actual content much, 00:05:08.889 --> 00:05:11.089 much faster. Exactly. You get to the substance 00:05:11.089 --> 00:05:13.829 quicker. All right. So Claude can manage my time, 00:05:14.029 --> 00:05:16.069 create my documents. What about connecting it 00:05:16.069 --> 00:05:18.209 to the other tools I already use every day? That 00:05:18.209 --> 00:05:21.810 brings us to connectors. This is the piece that 00:05:21.810 --> 00:05:24.689 integrates Claude into your wider digital workspace. 00:05:25.389 --> 00:05:28.110 It's built on something Anthropic calls the model 00:05:28.110 --> 00:05:33.160 context protocol, or MCP. MCP Model Context Protocol. 00:05:33.420 --> 00:05:35.459 What does that mean in plain English? Think of 00:05:35.459 --> 00:05:38.180 it like a very specific secure key or a handshake. 00:05:38.959 --> 00:05:41.819 When you give permission, Claude uses MCP to 00:05:41.819 --> 00:05:44.279 ask another service like Google Drive or Slack 00:05:44.279 --> 00:05:46.839 for just the specific piece of information it 00:05:46.839 --> 00:05:49.399 needs for your request. It doesn't get free reign 00:05:49.399 --> 00:05:52.259 over your whole account. It gets temporary, limited 00:05:52.259 --> 00:05:54.579 access for that task based on the permissions 00:05:54.579 --> 00:05:57.360 you set up. OK, so you control the access, and 00:05:57.360 --> 00:05:58.920 there's a place to manage this. Yep, there's 00:05:58.920 --> 00:06:00.839 a connectors directory. It lists the available 00:06:00.839 --> 00:06:03.259 apps, things like Google Drive, Slack, Notion, 00:06:03.620 --> 00:06:06.100 Canva are examples. You connect them there. Makes 00:06:06.100 --> 00:06:08.899 sense. So how would you use this day -to -day? 00:06:09.040 --> 00:06:11.399 Give me some practical examples. OK, let's say 00:06:11.399 --> 00:06:13.819 you use Notion for project management. You could 00:06:13.819 --> 00:06:16.420 ask Claude, check my Q4 marketing plan board 00:06:16.420 --> 00:06:19.040 in Notion, find all the tasks assigned to me 00:06:19.040 --> 00:06:20.959 that are currently marked in progress, and list 00:06:20.959 --> 00:06:23.389 them. You don't have to go filter yourself. Cloud 00:06:23.389 --> 00:06:25.750 uses the connector to fetch that specific info. 00:06:26.149 --> 00:06:28.009 Right. It does the digging. What about cloud 00:06:28.009 --> 00:06:31.189 storage? Google Drive? Sure. You could say, search 00:06:31.189 --> 00:06:34.149 my monthly reports folder in Google Drive. Find 00:06:34.149 --> 00:06:36.569 any documents with revenue in the title from 00:06:36.569 --> 00:06:38.769 the last three months. Read them and give me 00:06:38.769 --> 00:06:41.730 a summary of the key business points. It finds, 00:06:42.149 --> 00:06:44.949 reads, and synthesizes information across multiple 00:06:44.949 --> 00:06:47.550 files. That could save a lot of searching. Slack, 00:06:48.029 --> 00:06:50.639 can it help with catching up? Definitely. You 00:06:50.639 --> 00:06:53.019 could ask, check the hashtag general announcements 00:06:53.019 --> 00:06:55.300 channel in Slack for the last 24 hours. Did I 00:06:55.300 --> 00:06:57.699 miss any important updates? It can scan and flag 00:06:57.699 --> 00:07:00.319 things for you. In Canva, can it actually make 00:07:00.319 --> 00:07:03.439 designs? It can draft them. So you might say, 00:07:03.620 --> 00:07:06.939 generate a draft Instagram post designing Canva 00:07:06.939 --> 00:07:09.439 using my promo template. The tech should say 00:07:09.439 --> 00:07:12.459 30 % off all products. It kicks off the process 00:07:12.459 --> 00:07:15.399 for you. OK, these sound incredibly useful. Is 00:07:15.399 --> 00:07:17.579 there a catch? Are they available to everyone? 00:07:17.839 --> 00:07:20.040 Ah, good question. That's the main limitation 00:07:20.040 --> 00:07:22.579 right now. Most of these connectors are tied 00:07:22.579 --> 00:07:26.759 to the paid plans pro team enterprise. And sometimes 00:07:26.759 --> 00:07:29.519 full functionality might require you to be using 00:07:29.519 --> 00:07:31.899 the desktop app rather than just the web interface. 00:07:32.339 --> 00:07:34.500 So you need to check your plan details. Got it. 00:07:34.540 --> 00:07:37.379 Paid feature, mostly. OK, with all this power 00:07:37.379 --> 00:07:39.660 accessing calendars, creating files, connecting 00:07:39.660 --> 00:07:42.019 to other apps, the conversation naturally turns 00:07:42.019 --> 00:07:44.699 to privacy and data control. That feels more 00:07:44.699 --> 00:07:47.269 critical than ever. Absolutely vital. And Anthropic 00:07:47.269 --> 00:07:49.750 has just updated its Terms of Service and Privacy 00:07:49.750 --> 00:07:52.449 policy, giving users a much clearer choice about 00:07:52.449 --> 00:07:54.829 how their data is used, specifically for training 00:07:54.829 --> 00:07:57.149 future AI models. OK, this sounds important. 00:07:57.189 --> 00:08:00.170 What's the choice exactly? So for users on Free, 00:08:00.430 --> 00:08:03.209 Pro, and Max plans, you now have a direct option. 00:08:03.670 --> 00:08:07.029 You can explicitly opt in or opt out of letting 00:08:07.029 --> 00:08:10.649 Anthropic use your conversations and any code 00:08:10.649 --> 00:08:13.129 you work on with Claude to train their future 00:08:13.129 --> 00:08:16.410 models. Right. So if I opt in, What happens then? 00:08:16.689 --> 00:08:19.129 If you opt in, your data can be used for training 00:08:19.129 --> 00:08:21.750 purposes. Anthropic says they might store this 00:08:21.750 --> 00:08:25.449 data for up to five years. Important note, if 00:08:25.449 --> 00:08:28.310 you delete a specific conversation, that particular 00:08:28.310 --> 00:08:30.769 deleted data won't be used for training going 00:08:30.769 --> 00:08:33.929 forward. OK. And if I opt out? Opting out means 00:08:33.929 --> 00:08:35.929 the previous policy basically stays in effect 00:08:35.929 --> 00:08:38.269 for you. Your data is stored for a much shorter 00:08:38.269 --> 00:08:41.029 period, generally around 30 days, mainly for 00:08:41.029 --> 00:08:43.980 safety and monitoring. And crucially, your conversations 00:08:43.980 --> 00:08:45.799 will not be used to train their models. This 00:08:45.799 --> 00:08:47.840 is the more confidential setting, the one you'd 00:08:47.840 --> 00:08:49.500 likely want if you're handling sensitive business 00:08:49.500 --> 00:08:51.740 or client information. That seems pretty clear. 00:08:52.120 --> 00:08:54.139 Opt -in means they train on your data. Opt -out 00:08:54.139 --> 00:08:56.179 means they don't. But you mentioned a deadline 00:08:56.179 --> 00:08:58.259 earlier. Yes, this is the really critical part, 00:08:58.399 --> 00:09:00.519 especially for existing users. You need to make 00:09:00.519 --> 00:09:03.000 this opt -in or opt -out choice by September 00:09:03.000 --> 00:09:08.360 28, 2025. September 28th, 2025. Why is that date 00:09:08.360 --> 00:09:10.480 so important, particularly for people on paid 00:09:10.480 --> 00:09:12.659 plans who might have sensitive data flying around? 00:09:12.820 --> 00:09:15.419 What's the risk of missing it? The risk is the 00:09:15.419 --> 00:09:18.000 default. If you're an existing user and you don't 00:09:18.000 --> 00:09:20.580 actively make a choice by that September 2025 00:09:20.580 --> 00:09:23.259 deadline, your account will likely default to 00:09:23.259 --> 00:09:26.399 the opt -in setting, which means your data, potentially 00:09:26.399 --> 00:09:28.480 including sensitive business information you've 00:09:28.480 --> 00:09:30.659 discussed with Claude, could automatically start 00:09:30.659 --> 00:09:32.820 being used for model training after that date. 00:09:32.940 --> 00:09:35.980 OK, so inaction means you're opted in. If you 00:09:35.980 --> 00:09:38.700 handle sensitive data, you absolutely need to 00:09:38.700 --> 00:09:41.340 consciously go in and select opt out before September 00:09:41.340 --> 00:09:44.299 28th, 2025. Precisely. You need to be proactive 00:09:44.299 --> 00:09:46.159 if you want to keep that data out of the training 00:09:46.159 --> 00:09:48.279 pool. Got it. OK, let's pull some of these threads 00:09:48.279 --> 00:09:50.759 together now. We've talked scheduling, files, 00:09:51.059 --> 00:09:53.159 connectors, privacy. How does this all look when 00:09:53.159 --> 00:09:56.700 applied to specific jobs or roles, like targeted 00:09:56.700 --> 00:09:59.120 use cases? Yeah, this is where you see Claude 00:09:59.120 --> 00:10:01.460 becoming less of a general tool and more like 00:10:01.460 --> 00:10:04.139 a specialized partner. Take developers, for instance. 00:10:04.980 --> 00:10:07.720 The automation potential for data tasks is huge. 00:10:08.299 --> 00:10:11.340 You could upload a CSV file, maybe userfeedback 00:10:11.340 --> 00:10:14.500 .csv, and ask Claude to write the entire Python 00:10:14.500 --> 00:10:17.500 script to read it, run sentiment analysis, positive, 00:10:17.539 --> 00:10:20.279 negative, neutral on the feedback, save those 00:10:20.279 --> 00:10:23.360 results to a new CSV, and even generate a pie 00:10:23.360 --> 00:10:25.990 chart visualizing the sentiment breakdown. Wow, 00:10:26.110 --> 00:10:28.450 so it's not just suggesting code snippets, it's 00:10:28.450 --> 00:10:31.029 writing the whole workflow script. That skips 00:10:31.029 --> 00:10:33.889 a ton of setup. Although I have to admit, I still 00:10:33.889 --> 00:10:35.950 wrestle with prompt drift myself sometimes when 00:10:35.950 --> 00:10:38.289 I try to chain too many complex steps together 00:10:38.289 --> 00:10:40.190 like that. Oh yeah, prompt drift is definitely 00:10:40.190 --> 00:10:42.490 a thing. Where the AI kind of loses the plot 00:10:42.490 --> 00:10:45.129 halfway through a really long, complicated request. 00:10:45.450 --> 00:10:47.169 It can happen if you stack too many instructions 00:10:47.169 --> 00:10:49.029 at once without breaking them down. Exactly, 00:10:49.110 --> 00:10:50.570 it just sort of wanders off. But back to the 00:10:50.570 --> 00:10:52.370 use cases, what about students or researchers? 00:10:52.830 --> 00:10:56.090 Huge potential there too. Imagine asking Claude 00:10:56.090 --> 00:10:59.250 to find, say, five recent scientific articles 00:10:59.250 --> 00:11:02.830 on CRISPR -Cas9. Then summarize each one into 00:11:02.830 --> 00:11:05.470 three bullet points, include the links, and compile 00:11:05.470 --> 00:11:08.149 all of that into a single, properly structured 00:11:08.149 --> 00:11:11.769 Word document, ready for review. That's automating 00:11:11.769 --> 00:11:14.210 the literature review assembly line, basically, 00:11:14.330 --> 00:11:17.149 and for project managers. Think about combining 00:11:17.149 --> 00:11:19.710 connectors with scheduling. You could tell Claude, 00:11:19.730 --> 00:11:22.129 go to my Trello board, grab all the cards marked 00:11:22.129 --> 00:11:24.980 urgent to do. Then schedule a meeting for tomorrow 00:11:24.980 --> 00:11:27.320 at 10 a .m. in Google Calendar to discuss them 00:11:27.320 --> 00:11:29.960 and paste the list of those Trello cards right 00:11:29.960 --> 00:11:32.120 into the Calendar invites description. That's 00:11:32.120 --> 00:11:34.000 like connecting different work streams automatically, 00:11:34.480 --> 00:11:36.159 stacking those Lego blocks of data, as you said. 00:11:36.360 --> 00:11:38.759 Exactly. So thinking about these specialized 00:11:38.759 --> 00:11:42.039 roles, developers, researchers, PMs, how does 00:11:42.039 --> 00:11:44.399 this level of automation and customization really 00:11:44.399 --> 00:11:46.679 impact their daily work? What's the cognitive 00:11:46.679 --> 00:11:49.679 benefit? Well, it seems like it completely automates 00:11:49.679 --> 00:11:52.679 the tedious, time -consuming setup and structuring 00:11:52.679 --> 00:11:55.980 work, formatting documents, writing boilerplate 00:11:55.980 --> 00:11:59.659 code, hunting for information across apps, freeing 00:11:59.659 --> 00:12:02.419 them up to focus on the actual analysis, strategy, 00:12:02.820 --> 00:12:05.139 or creation. Couldn't agree more. It handles 00:12:05.139 --> 00:12:07.340 the scaffolding so you can build faster. Okay, 00:12:07.440 --> 00:12:10.179 this is all incredibly powerful stuff. But to 00:12:10.179 --> 00:12:12.299 actually use it well, people probably need some 00:12:12.299 --> 00:12:15.580 guidance. Any best practices or tips? Definitely. 00:12:15.820 --> 00:12:18.519 We've got four quick ones. First, and this is 00:12:18.519 --> 00:12:20.700 crucial, always check which features are actually 00:12:20.700 --> 00:12:23.399 available in your specific plan. A lot of the 00:12:23.399 --> 00:12:25.519 really advanced stuff, especially complex file 00:12:25.519 --> 00:12:27.960 handling and many connectors, are often limited 00:12:27.960 --> 00:12:31.000 to the Macs, Team, or Enterprise tiers. Don't 00:12:31.000 --> 00:12:32.580 assume you have everything. Good point. Check 00:12:32.580 --> 00:12:34.559 your subscription level. What's tip two? Tip 00:12:34.559 --> 00:12:36.580 two tackles that tromp drift issue we mentioned. 00:12:36.980 --> 00:12:39.379 The key is to break down complex requests. Instead 00:12:39.379 --> 00:12:41.639 of asking for everything at once, guide Claude 00:12:41.639 --> 00:12:44.279 step by step. Ask it to summarize the data first. 00:12:44.720 --> 00:12:46.620 Then ask it to create an outline based on the 00:12:46.620 --> 00:12:49.559 summary. Then ask it to draft the document section 00:12:49.559 --> 00:12:52.659 by section. Smaller sequential steps improve 00:12:52.659 --> 00:12:55.659 accuracy dramatically. OK, breakdown. Makes sense. 00:12:56.139 --> 00:12:59.419 Tip three. Manage your permissions, especially 00:12:59.419 --> 00:13:01.600 if you start using connectors. You're granting 00:13:01.600 --> 00:13:04.299 cloud access to other apps. Make it a habit to 00:13:04.299 --> 00:13:06.820 periodically go into your cloud settings, review 00:13:06.820 --> 00:13:09.779 which apps are connected, and revoke access for 00:13:09.779 --> 00:13:12.139 any you don't actively need anymore. Just good 00:13:12.139 --> 00:13:14.679 digital hygiene. Right. Keep track of who has 00:13:14.679 --> 00:13:18.389 keys to what. And the last tip. KIPP4 relates 00:13:18.389 --> 00:13:21.070 to Claude's ability to search the web now. While 00:13:21.070 --> 00:13:23.090 that gives it access to current information, 00:13:23.629 --> 00:13:25.570 remember that the web isn't always reliable. 00:13:26.090 --> 00:13:27.950 So if you're using Claude's output for anything 00:13:27.950 --> 00:13:30.710 important, a business decision, a published report, 00:13:31.090 --> 00:13:32.970 critical facts always double check the information, 00:13:33.190 --> 00:13:35.509 especially facts and figures. Verify gets trusted 00:13:35.509 --> 00:13:38.909 sources. Solid advice. Trust but verify, especially 00:13:38.909 --> 00:13:42.309 with web data. So wrapping this all up. What's 00:13:42.309 --> 00:13:44.409 the really big picture here, the core takeaway? 00:13:44.590 --> 00:13:46.149 I think it's this fundamental shift we've been 00:13:46.149 --> 00:13:48.850 talking about. Claude isn't just answering questions 00:13:48.850 --> 00:13:51.370 anymore, it's actively doing the work. When you 00:13:51.370 --> 00:13:53.850 combine that direct file creation with the connector 00:13:53.850 --> 00:13:56.789 ecosystem, it means way less time spent juggling 00:13:56.789 --> 00:13:59.889 browser tabs and apps and much more time available 00:13:59.889 --> 00:14:01.889 for higher level thinking and decision making. 00:14:02.210 --> 00:14:04.710 I agree. It feels like the value you can extract 00:14:04.710 --> 00:14:07.649 from AI like Claude is now directly tied to how 00:14:07.649 --> 00:14:09.750 quickly you can adapt and integrate these newer, 00:14:09.889 --> 00:14:12.379 more active capabilities. into how you actually 00:14:12.379 --> 00:14:15.500 work. So the call to action really is start experimenting, 00:14:15.820 --> 00:14:17.500 try out these integrated tools, see how they 00:14:17.500 --> 00:14:20.360 fit your workflow, but crucially pay close attention 00:14:20.360 --> 00:14:22.879 to those privacy settings and make your choice 00:14:22.879 --> 00:14:26.059 before that September 2025 deadline. See where 00:14:26.059 --> 00:14:27.840 you gain the most leverage, where it saves you 00:14:27.840 --> 00:14:30.980 the most effort. Beat. That's our deep dive for 00:14:30.980 --> 00:14:31.120 today.