Episode 429: Getting started with LLM Wikis

June 04, 2026

Episode Transcript

Welcome to Episode 429 of the Microsoft Cloud IT Pro Podcast. In this episode, Scott and Ben dig into the concept of LLM wikis, specifically building personal knowledge management vaults using Obsidian, markdown, and AI tooling like Claude Code, GitHub Copilot CLI, and Copilot Cowork. The core idea comes from a gist by Andrej Karpathy and involves creating a structured folder of markdown clippings that an LLM can reason over to extract entities, concepts, and sources, building a searchable, graph-linked knowledge base over time. Scott walks through how he wired up Obsidian Web Clipper and an RSS Dashboard plugin to feed articles into his vault automatically, then had the LLM help build a Python script to automate the ingest workflow and cut down on token usage.

The conversation expands into how Copilot Cowork fits into this workflow as a scheduling harness, with practical examples of using it to pull email from an inbox daily, convert messages to markdown, and generate a prioritized to-do list. Ben shares how he applied the same approach to 428 episodes of podcast transcripts, and both hosts note that token costs can run high fast without some upfront thinking about optimization. Scott closes with a reminder that pulling data into plain markdown sidecars outside of IRM and sensitivity label protections means teams should stay mindful of organizational data policies.

Your support makes this show possible! Please consider becoming a premium member for access to live shows and more. Check out our membership options.

Show Notes

Sponsors

	TrustedTech is a leading Microsoft Cloud Solution Provider (CSP) specializing in Microsoft Cloud services, Microsoft perpetual licensing, and Microsoft Support Services for medium and enterprise-sized businesses. Their robust team of in-house, U.S.-based Microsoft architects and engineers are certified in all 6/6 Microsoft Solutions Partner Designations in the Microsoft Cloud Partner Program. M365 Licensing Consultation M365 Tenant Assessment Copilot Readiness Assessment
	ShareGate is your migration and governance solution for Microsoft 365. ShareGate helps your teams simplify tenant migrations, get Copilot-ready, and take control of Microsoft 365 governance.
	Nasuni is a leading unstructured data platform for enterprises where file data is mission-critical for both people and AI. Nasuni powers the operational file layer where work happens — helping organizations manage, protect, and activate data so teams can work smarter, reduce costs, and operate securely without limits.
	Intelligink — Would you like to become the irreplaceable Microsoft 365 resource for your organization? Let us know!

See full episode transcriptTranscript is autogenerated by AI

WEBVTT 1 00:00:03.439 --> 00:00:06.000 - Welcome to episode 429 2 00:00:06.000 --> 00:00:09.119 - of the Microsoft Cloud IT Pro podcast recorded 3 00:00:09.119 --> 00:00:11.779 - live on 05/29/2026. 4 00:00:12.080 --> 00:00:14.375 - This is a show about Microsoft three sixty 5 00:00:14.375 --> 00:00:16.454 - five and Azure from the perspective of IT 6 00:00:16.454 --> 00:00:18.695 - pros and end users, where we discuss a 7 00:00:18.695 --> 00:00:21.175 - topic or recent news and how it relates 8 00:00:21.175 --> 00:00:21.835 - to you. 9 00:00:22.214 --> 00:00:24.375 - In this episode, Ben and Scott dig into 10 00:00:24.375 --> 00:00:27.114 - the concept of LLM wikis, specifically 11 00:00:27.414 --> 00:00:27.914 - building 12 00:00:28.289 --> 00:00:30.949 - personal knowledge management vault using Obsidian, 13 00:00:31.250 --> 00:00:34.609 - markdown, and AI tooling like Cloud Code, GitHub 14 00:00:34.609 --> 00:00:37.429 - Copilot CLI, and Copilot Cowork. 15 00:00:37.890 --> 00:00:40.369 - Scott walks through how he wired up Obsidian 16 00:00:40.369 --> 00:00:43.434 - Web Clipper and an RSS dashboard plugin to 17 00:00:43.434 --> 00:00:45.614 - feed articles into his vault automatically, 18 00:00:45.994 --> 00:00:48.155 - then had the LLM help build a Python 19 00:00:48.155 --> 00:00:50.715 - script to automate the ingestion workflow and cut 20 00:00:50.715 --> 00:00:51.934 - down on token usage. 21 00:00:52.314 --> 00:00:55.274 - Then he expands into how Copilot Cowork fits 22 00:00:55.274 --> 00:00:58.010 - into this workflow as a scheduling harness with 23 00:00:58.010 --> 00:01:00.570 - practical examples of using it to pull email 24 00:01:00.570 --> 00:01:03.550 - from an inbox daily, convert messages to markdown, 25 00:01:03.770 --> 00:01:06.569 - and generate a prioritized to do list. Let's 26 00:01:06.569 --> 00:01:08.829 - dive into the world of LLM wikis. 27 00:01:11.049 --> 00:01:13.185 - I have a theory. Windows? No. I mean, 28 00:01:13.185 --> 00:01:14.905 - yes. I run too much stuff. Yes. But 29 00:01:15.024 --> 00:01:17.185 - no. Well, I think we all run too 30 00:01:17.185 --> 00:01:20.304 - much stuff. I've noticed lately that and I 31 00:01:20.304 --> 00:01:21.905 - think I talked about this a couple weeks 32 00:01:21.905 --> 00:01:25.185 - ago, the whole I've got cotypist on my 33 00:01:25.185 --> 00:01:26.965 - Mac doing type ahead prediction 34 00:01:27.344 --> 00:01:29.950 - with with a locally downloaded model. 35 00:01:30.409 --> 00:01:31.150 - I've got 36 00:01:31.530 --> 00:01:32.269 - Type Whisper 37 00:01:32.569 --> 00:01:34.650 - running in the background with a model loaded 38 00:01:34.650 --> 00:01:36.670 - in case I just wanna do text dictation. 39 00:01:36.810 --> 00:01:38.489 - Like, I I I I was thinking about 40 00:01:38.489 --> 00:01:40.590 - it the other day. At any given time, 41 00:01:41.290 --> 00:01:45.054 - local model running, I probably have at least 42 00:01:45.054 --> 00:01:47.375 - four instances of the same model or a 43 00:01:47.375 --> 00:01:50.094 - similar model all loaded up because these apps 44 00:01:50.094 --> 00:01:52.494 - don't have, like, a common cache interface. Like, 45 00:01:52.494 --> 00:01:54.655 - they don't use, like, hugging face cache or 46 00:01:54.655 --> 00:01:56.575 - things like that. They all download, like, locally 47 00:01:56.575 --> 00:01:58.354 - into their packages and their directories. 48 00:01:58.719 --> 00:01:59.459 - So at least 49 00:01:59.920 --> 00:02:00.879 - for me, I think a lot of the 50 00:02:00.879 --> 00:02:02.979 - things that I'm running into lately are actually 51 00:02:03.200 --> 00:02:06.479 - resource contention. Like, I haven't materially changed my 52 00:02:06.479 --> 00:02:06.979 - workloads 53 00:02:07.280 --> 00:02:09.120 - or my workflows, but I have a bunch 54 00:02:09.120 --> 00:02:10.560 - of the bunch more of these apps running 55 00:02:10.560 --> 00:02:12.080 - in the background that I didn't have before. 56 00:02:12.080 --> 00:02:13.120 - I was trying to do a little bit 57 00:02:13.120 --> 00:02:15.465 - of an audit, and it's not driving, like, 58 00:02:15.525 --> 00:02:18.584 - crazy memory pressure, crazy CPU pressure. 59 00:02:18.965 --> 00:02:21.044 - But, like, when some of these models load 60 00:02:21.044 --> 00:02:22.805 - and unload, like, you've got, like, I don't 61 00:02:22.805 --> 00:02:25.284 - know, like, Gemma four sitting there ready to 62 00:02:25.284 --> 00:02:27.300 - go. It's like, oh, hey. I had four 63 00:02:27.300 --> 00:02:29.460 - gigs of RAM that just got evicted for 64 00:02:29.460 --> 00:02:31.219 - this thing over here, and then it's gotta 65 00:02:31.219 --> 00:02:33.780 - reload rapidly for this like, it I don't 66 00:02:33.780 --> 00:02:35.699 - know. That that would be my guess is 67 00:02:35.699 --> 00:02:38.594 - we're all running, like, so much, like, local 68 00:02:38.915 --> 00:02:40.435 - AI slops that we don't even know it. 69 00:02:40.435 --> 00:02:42.034 - So little of it we can control. Like, 70 00:02:42.034 --> 00:02:43.634 - I don't remember if we talked about this 71 00:02:43.634 --> 00:02:45.715 - or when this came out, but Google Chrome 72 00:02:45.715 --> 00:02:48.215 - now downloading, what, a four gig 73 00:02:48.514 --> 00:02:51.090 - LLM model in the background as part of 74 00:02:51.090 --> 00:02:53.569 - the browser? The Gemma model in the background. 75 00:02:53.569 --> 00:02:55.729 - Yep. Yep. So that same model is the 76 00:02:55.729 --> 00:02:57.729 - same model that I'm using in Cotypeist, which 77 00:02:57.729 --> 00:02:58.229 - is 78 00:02:58.530 --> 00:03:00.770 - similar to what I'm so so, like, I've 79 00:03:00.770 --> 00:03:02.310 - got this app called Type Whisper. 80 00:03:02.865 --> 00:03:05.504 - Anyhoo. So Type Whisper is one of the 81 00:03:05.504 --> 00:03:09.284 - dictation apps. But rather than using, like, Whisperflow 82 00:03:09.504 --> 00:03:10.485 - or Super Whisper, 83 00:03:10.865 --> 00:03:11.365 - everything 84 00:03:11.745 --> 00:03:14.305 - processed locally on device, you can choose, like, 85 00:03:14.305 --> 00:03:16.224 - hey. I I wanna use Parakeet. But the 86 00:03:16.224 --> 00:03:18.164 - cool thing it does is it does 87 00:03:18.680 --> 00:03:20.620 - live processing, like live transcription, 88 00:03:21.000 --> 00:03:22.680 - and then it does post processing as well, 89 00:03:22.680 --> 00:03:24.039 - which is nice. So you can do that 90 00:03:24.039 --> 00:03:26.280 - thing where you're just saying, hey. I'd like 91 00:03:26.280 --> 00:03:27.879 - to make a list. Number one is this. 92 00:03:27.879 --> 00:03:29.560 - Number two is this. Number three is this. 93 00:03:29.560 --> 00:03:31.159 - And, normally, that would just be a big 94 00:03:31.159 --> 00:03:33.875 - flat wall of text going across. But if 95 00:03:33.875 --> 00:03:36.034 - you post process it and it gets smarter, 96 00:03:36.034 --> 00:03:38.194 - it actually renders, like, one, two, three, and 97 00:03:38.194 --> 00:03:40.675 - four into a list, and that's the text 98 00:03:40.675 --> 00:03:42.375 - that is expressed that you just dictated. 99 00:03:42.675 --> 00:03:43.875 - But I was thinking about that one the 100 00:03:43.875 --> 00:03:45.155 - other day. I was like, oh, this is 101 00:03:45.155 --> 00:03:46.835 - getting slower and slower. And I went and 102 00:03:46.835 --> 00:03:48.549 - looked, and I turned on, like, the pre 103 00:03:48.549 --> 00:03:49.049 - integration, 104 00:03:49.509 --> 00:03:51.370 - the Run It thing, the post integration. 105 00:03:51.989 --> 00:03:53.430 - So that one had to get kicked to 106 00:03:53.430 --> 00:03:55.370 - the curb. It was nice, but 107 00:03:55.669 --> 00:03:58.389 - it was it was slowing things down for 108 00:03:58.389 --> 00:03:59.449 - sure. Yeah. 109 00:04:00.150 --> 00:04:01.370 - All these things. 110 00:04:01.745 --> 00:04:03.824 - You know what other things well, nope. I 111 00:04:03.824 --> 00:04:05.504 - won't go down that rabbit hole. We can 112 00:04:05.504 --> 00:04:08.144 - talk about other things. But speaking of more 113 00:04:08.144 --> 00:04:10.064 - things we're running, you and I both started 114 00:04:10.064 --> 00:04:11.824 - playing with something within the last I don't 115 00:04:11.824 --> 00:04:13.905 - know when you started. I started, like, a 116 00:04:13.905 --> 00:04:15.044 - week and a half ago 117 00:04:15.349 --> 00:04:17.430 - playing with more things to run on our 118 00:04:17.430 --> 00:04:17.930 - computers. 119 00:04:18.230 --> 00:04:20.310 - Yes. And this is not maybe we should 120 00:04:20.310 --> 00:04:22.790 - preface this. This is not specifically, I would 121 00:04:22.790 --> 00:04:24.730 - say, Microsoft or March 122 00:04:24.870 --> 00:04:27.589 - Microsoft three sixty five or Azure episode. However, 123 00:04:27.589 --> 00:04:30.514 - it incorporates into our work with Microsoft three 124 00:04:30.514 --> 00:04:32.274 - sixty five and Azure and how we're starting 125 00:04:32.274 --> 00:04:33.955 - to track some of our resources. I have 126 00:04:33.955 --> 00:04:35.074 - a tie in I have a tie in 127 00:04:35.074 --> 00:04:36.834 - for you there. I'm actually gonna yeah. Do 128 00:04:36.834 --> 00:04:38.115 - you have a tie in for me? Yep. 129 00:04:38.115 --> 00:04:40.355 - Okay. So if you're listening and you're like, 130 00:04:40.355 --> 00:04:41.875 - there's not gonna be a tie in, Scott 131 00:04:41.875 --> 00:04:43.139 - has a tie in. I don't know when 132 00:04:43.139 --> 00:04:45.060 - it's gonna drop. So you better listen to 133 00:04:45.060 --> 00:04:45.959 - the whole episode 134 00:04:46.259 --> 00:04:48.019 - to figure out the tie in. Stick around. 135 00:04:48.019 --> 00:04:49.480 - Okay. I've been playing around 136 00:04:50.500 --> 00:04:53.540 - and been watching all these just videos fly 137 00:04:53.540 --> 00:04:55.480 - by and articles fly by 138 00:04:55.884 --> 00:04:57.024 - around the concept 139 00:04:57.724 --> 00:04:58.944 - of LLM wikis 140 00:04:59.324 --> 00:04:59.824 - and 141 00:05:00.125 --> 00:05:00.625 - leveraging 142 00:05:01.245 --> 00:05:01.745 - LLMs 143 00:05:02.524 --> 00:05:03.024 - to 144 00:05:03.724 --> 00:05:06.625 - manage a wiki resource for you. And, specifically, 145 00:05:06.685 --> 00:05:08.550 - like, I've been doing this with Obsidian Vaults. 146 00:05:08.629 --> 00:05:11.189 - So Obsidian Vaults work very nicely here. They're 147 00:05:11.189 --> 00:05:14.629 - marked down plain text. LLMs process plain text 148 00:05:14.629 --> 00:05:17.110 - pretty darn well. They understand markdown pretty well. 149 00:05:17.110 --> 00:05:19.669 - It's kinda, like, a a de facto standard 150 00:05:19.669 --> 00:05:21.509 - for authoring these things. Right? All the skills, 151 00:05:21.509 --> 00:05:23.625 - agents, you write everything. Everything you do is 152 00:05:23.625 --> 00:05:24.365 - in markdown. 153 00:05:24.904 --> 00:05:27.404 - So an LLM Wiki, if 154 00:05:27.944 --> 00:05:30.585 - you have a compendium of knowledge that you 155 00:05:30.585 --> 00:05:32.504 - wanna put together, and that could be around 156 00:05:32.504 --> 00:05:34.824 - anything. It could be maybe around a topic 157 00:05:34.824 --> 00:05:35.725 - that you're researching. 158 00:05:36.319 --> 00:05:38.720 - So I don't know. Let's say you want 159 00:05:38.720 --> 00:05:39.220 - to 160 00:05:40.240 --> 00:05:42.079 - in M 365 Land, do you want to 161 00:05:42.079 --> 00:05:44.819 - go explore the current single the current licensing 162 00:05:44.879 --> 00:05:48.000 - constructs and compare this e SKU to this 163 00:05:48.000 --> 00:05:50.180 - business premium SKU or to this add on? 164 00:05:50.240 --> 00:05:52.644 - You could go and take, like, all those 165 00:05:52.644 --> 00:05:55.785 - pricing pages and all the documentation around that, 166 00:05:56.084 --> 00:05:58.644 - and you could put it in just a 167 00:05:58.644 --> 00:06:01.524 - big dumping ground of markdown, just a raw 168 00:06:01.524 --> 00:06:04.824 - source. And then you can have an LLM 169 00:06:05.365 --> 00:06:06.985 - reason across that data 170 00:06:07.370 --> 00:06:10.430 - and extract information around it. So understand 171 00:06:11.289 --> 00:06:12.970 - what was the source data that came with 172 00:06:12.970 --> 00:06:15.849 - it, maybe what are the general concepts around 173 00:06:15.849 --> 00:06:16.750 - it, entities, 174 00:06:17.370 --> 00:06:18.349 - all these different 175 00:06:18.810 --> 00:06:20.829 - sorts of things that are out there. 176 00:06:21.194 --> 00:06:24.814 - So Andrew Kapathy, who's kinda, like, one of 177 00:06:25.354 --> 00:06:28.235 - the original or or original researchers over at 178 00:06:28.235 --> 00:06:28.735 - OpenAI, 179 00:06:29.274 --> 00:06:31.115 - I believe he's also the person who coined 180 00:06:31.115 --> 00:06:33.594 - the term vibe coding. So he's kinda pretty 181 00:06:33.594 --> 00:06:34.495 - close to 182 00:06:35.050 --> 00:06:36.490 - it. He's been in this space for a 183 00:06:36.490 --> 00:06:37.930 - little bit? Been in this space for a 184 00:06:37.930 --> 00:06:40.030 - little bit. Was recently hired by Anthropic 185 00:06:40.650 --> 00:06:41.150 - post 186 00:06:41.850 --> 00:06:43.610 - getting out there and putting some of these 187 00:06:43.610 --> 00:06:46.330 - things out. But I'll have a link in 188 00:06:46.330 --> 00:06:49.285 - the show notes for everybody to 189 00:06:50.064 --> 00:06:50.805 - a gist 190 00:06:51.264 --> 00:06:52.725 - that he posted. 191 00:06:53.345 --> 00:06:53.845 - And 192 00:06:54.705 --> 00:06:55.845 - and this gist 193 00:06:56.384 --> 00:06:58.324 - is just an LLM Wiki. 194 00:06:58.785 --> 00:07:00.545 - So you go and kinda read through this 195 00:07:00.545 --> 00:07:04.129 - thing, and it's just llm-wiki.md. 196 00:07:04.430 --> 00:07:04.930 - And 197 00:07:05.310 --> 00:07:06.610 - the core idea 198 00:07:06.990 --> 00:07:08.750 - of this whole thing, like I said, is 199 00:07:08.750 --> 00:07:11.089 - you kinda have a big dumping ground. 200 00:07:11.389 --> 00:07:13.230 - You could think about it as maybe, like, 201 00:07:13.230 --> 00:07:15.550 - a folder that you called raw or you 202 00:07:15.550 --> 00:07:16.689 - called ingest, 203 00:07:17.334 --> 00:07:18.394 - you called it clippings, 204 00:07:18.854 --> 00:07:19.914 - something like that. 205 00:07:20.214 --> 00:07:22.394 - And what you do is you keep putting 206 00:07:22.935 --> 00:07:25.274 - articles in there, reference materials, 207 00:07:25.654 --> 00:07:27.754 - but you put it in as markdown. 208 00:07:28.055 --> 00:07:30.074 - So this whole thing just becomes 209 00:07:30.580 --> 00:07:32.819 - a big bank of markdown that's sitting out 210 00:07:32.819 --> 00:07:34.040 - there. And 211 00:07:34.580 --> 00:07:37.319 - you direct the LLM that anytime 212 00:07:37.860 --> 00:07:41.480 - a new thing shows up in my raw 213 00:07:41.699 --> 00:07:42.199 - directory 214 00:07:42.964 --> 00:07:45.764 - to reason over it and then extract that 215 00:07:45.764 --> 00:07:49.764 - information, extract entities, extract core concepts, tell me 216 00:07:49.764 --> 00:07:51.524 - what the source of it is, and put 217 00:07:51.524 --> 00:07:52.264 - it all together. 218 00:07:52.644 --> 00:07:54.724 - And this is the nice thing about something 219 00:07:54.724 --> 00:07:57.685 - like Obsidian. So Obsidian, a personal knowledge management 220 00:07:57.685 --> 00:07:58.504 - tool, PKM, 221 00:07:59.100 --> 00:07:59.839 - But Obsidian 222 00:08:00.459 --> 00:08:00.959 - does 223 00:08:01.500 --> 00:08:03.740 - Wiki style links, so you can have all 224 00:08:03.740 --> 00:08:05.680 - these things start to relate to each other. 225 00:08:05.979 --> 00:08:08.540 - And then you get the kinda graph based 226 00:08:08.540 --> 00:08:11.019 - views that that come along with that as 227 00:08:11.019 --> 00:08:11.519 - well. 228 00:08:11.995 --> 00:08:14.235 - So it takes almost nothing to wire it 229 00:08:14.235 --> 00:08:16.714 - up, first of all, to get started. So 230 00:08:16.714 --> 00:08:18.555 - it's pretty much go out and take this 231 00:08:18.555 --> 00:08:19.055 - gist, 232 00:08:19.435 --> 00:08:22.175 - and, yes, you need to have access to 233 00:08:22.714 --> 00:08:25.919 - some kind of LLM interface. Now that LLM 234 00:08:25.919 --> 00:08:26.419 - interface 235 00:08:26.800 --> 00:08:29.120 - could be hang with me here. Could be 236 00:08:29.120 --> 00:08:32.639 - quad code, could be Gemini CLI. Well, actually, 237 00:08:32.639 --> 00:08:34.639 - Gemini do CLI just went away. Anti anti 238 00:08:34.639 --> 00:08:37.220 - gravity, but there's also anti gravity CLI. 239 00:08:37.605 --> 00:08:40.904 - It could be GitHub Copilot CLI, codex, 240 00:08:41.445 --> 00:08:44.565 - whatever that is. Or if you have access 241 00:08:44.565 --> 00:08:47.784 - to, I don't know, say, Copilot Cowork 242 00:08:48.164 --> 00:08:50.644 - and in in and the Frontier agent because 243 00:08:50.644 --> 00:08:52.024 - you're in the Frontier program, 244 00:08:52.460 --> 00:08:54.460 - you can also run an LLM Wiki inside 245 00:08:54.460 --> 00:08:56.940 - of Copilot Coburg. Have you tried this? I'm 246 00:08:56.940 --> 00:08:59.019 - curious to see. Did and it works? Oh, 247 00:08:59.019 --> 00:09:01.100 - yeah. It opens up a whole interesting world 248 00:09:01.100 --> 00:09:02.940 - of possibilities here. Hold on. Stick with me. 249 00:09:02.940 --> 00:09:04.080 - Now you have me curious. 250 00:09:05.875 --> 00:09:08.855 - If you're managing file storage today, you've probably 251 00:09:08.915 --> 00:09:11.555 - felt the pressure. Refresh cycles are harder to 252 00:09:11.555 --> 00:09:14.995 - plan, costs and complexity are increasing, especially as 253 00:09:14.995 --> 00:09:17.095 - file workloads scale across regions. 254 00:09:17.529 --> 00:09:20.889 - That's why Microsoft customers trust Nasuni. As an 255 00:09:20.889 --> 00:09:22.350 - Azure certified software, 256 00:09:22.730 --> 00:09:25.769 - Nasuni provides a global file system designed for 257 00:09:25.769 --> 00:09:29.690 - enterprise scale environments, keeping file data secure, governed, 258 00:09:29.690 --> 00:09:33.105 - and accessible across Azure environments without added infrastructure 259 00:09:33.584 --> 00:09:34.084 - complexity. 260 00:09:34.384 --> 00:09:37.584 - It's the foundation to keep your unstructured data 261 00:09:37.584 --> 00:09:40.865 - stable even as your infrastructure evolves. To see 262 00:09:40.865 --> 00:09:42.865 - how much you could save while keeping your 263 00:09:42.865 --> 00:09:48.450 - initiatives on track, visit nasuni.com/tco. 264 00:09:48.450 --> 00:09:53.110 - That's nasuni.com/tco. 265 00:09:54.129 --> 00:09:55.889 - So let's talk about wiring all this up. 266 00:09:55.889 --> 00:09:59.190 - So so you basically go out the and 267 00:09:59.330 --> 00:10:01.534 - I've done a couple of these now, like, 268 00:10:01.534 --> 00:10:03.294 - and been kinda playing around. And you've been 269 00:10:03.294 --> 00:10:05.334 - playing around with one to build, like, a 270 00:10:05.615 --> 00:10:07.694 - basically, an Obsidian Vault for us around the 271 00:10:07.694 --> 00:10:09.714 - podcast. We can go back and say podcast 272 00:10:09.934 --> 00:10:12.414 - stuff in. It's fascinating. When did we talk 273 00:10:12.414 --> 00:10:14.894 - about this? On what date this happened? How 274 00:10:14.894 --> 00:10:16.740 - many times did we have this guest on? 275 00:10:16.899 --> 00:10:18.419 - And now you've got all that information in 276 00:10:18.419 --> 00:10:20.019 - text in one place. Show me all the 277 00:10:20.019 --> 00:10:22.519 - episodes where we talked about a specific topic. 278 00:10:22.580 --> 00:10:25.059 - Like, it's been really interesting. Go show me 279 00:10:25.059 --> 00:10:27.299 - what topics. We've pulled analytics into it. Go 280 00:10:27.299 --> 00:10:28.360 - show me what topics 281 00:10:28.754 --> 00:10:29.575 - tied into 282 00:10:30.115 --> 00:10:32.274 - analytics. Yeah. All the things. Go take this 283 00:10:32.274 --> 00:10:35.794 - gist, and you can literally copy and paste 284 00:10:35.794 --> 00:10:36.995 - it. I don't know if this is how 285 00:10:36.995 --> 00:10:38.595 - you started with the one that you worked 286 00:10:38.595 --> 00:10:40.195 - on. I'm curious how you started, and I'll 287 00:10:40.195 --> 00:10:41.794 - tell you how I started. So I took 288 00:10:41.794 --> 00:10:45.089 - this gist, and I copied and pasted it 289 00:10:45.230 --> 00:10:47.389 - straight into a CLI. I took it and 290 00:10:47.389 --> 00:10:49.950 - put it right into actually, you know what 291 00:10:49.950 --> 00:10:51.789 - I did? Because I wanted to do this, 292 00:10:51.789 --> 00:10:54.110 - like, a freeway that anybody could get started 293 00:10:54.110 --> 00:10:56.529 - with. So I did it in cloud code, 294 00:10:56.534 --> 00:10:58.454 - but I did it in cloud code tied 295 00:10:58.454 --> 00:10:58.954 - to 296 00:10:59.334 --> 00:10:59.834 - OpenRouter 297 00:11:00.454 --> 00:11:02.694 - and the free models in OpenRouter. So I 298 00:11:02.694 --> 00:11:06.375 - wasn't using a paid anthropic or cloud plan. 299 00:11:06.375 --> 00:11:08.855 - I wasn't using, like, pay per token. I 300 00:11:08.855 --> 00:11:10.540 - did all this stuff for free. You could 301 00:11:10.540 --> 00:11:12.220 - do it free for free with anti gravity 302 00:11:12.220 --> 00:11:13.660 - and things like that. It gets a little 303 00:11:13.660 --> 00:11:15.500 - harder to do free later, like, once the 304 00:11:15.500 --> 00:11:17.100 - vaults get a little bit bigger, but you 305 00:11:17.100 --> 00:11:19.100 - can totally start out Really hard to do 306 00:11:19.100 --> 00:11:20.779 - free later. But you can start out for 307 00:11:20.779 --> 00:11:22.879 - free. So you take this gist 308 00:11:23.225 --> 00:11:26.345 - and you put it into your LLM interface, 309 00:11:26.345 --> 00:11:27.945 - in this case, let me say, like, Claude 310 00:11:27.945 --> 00:11:30.764 - code. Just paste it straight into the terminal 311 00:11:30.985 --> 00:11:33.004 - and add a line at the end 312 00:11:33.465 --> 00:11:36.125 - that says, I want you to turn this 313 00:11:36.389 --> 00:11:36.889 - into 314 00:11:37.830 --> 00:11:40.790 - a context file for this vault, or, like, 315 00:11:40.790 --> 00:11:43.269 - I want you to create the second brain 316 00:11:43.269 --> 00:11:44.570 - for Scott that manages 317 00:11:45.029 --> 00:11:46.870 - everything he finds on the Internet wants to 318 00:11:46.870 --> 00:11:48.070 - read about later. Right? So you give it 319 00:11:48.070 --> 00:11:49.794 - a little bit of context. That's it. You 320 00:11:49.794 --> 00:11:51.235 - just put in that one little sentence at 321 00:11:51.235 --> 00:11:53.975 - the end, fire it off. It will create 322 00:11:54.595 --> 00:11:56.834 - a Claude in the case of Claude, it 323 00:11:56.834 --> 00:11:58.595 - will create a claude dot MD. You did 324 00:11:58.595 --> 00:12:00.914 - this in GitHub Copilot. It'll create you, like, 325 00:12:00.914 --> 00:12:04.059 - a Copilot instructions dot MD. I recommend doing 326 00:12:04.059 --> 00:12:05.899 - a claud dot MD as a context file, 327 00:12:05.899 --> 00:12:07.580 - and then you can just pull it from, 328 00:12:07.580 --> 00:12:10.339 - like, LLM to LLM because all the various 329 00:12:10.700 --> 00:12:13.339 - or, I guess, from agent to harness to 330 00:12:13.339 --> 00:12:15.019 - harness. Because you can take a claud dot 331 00:12:15.019 --> 00:12:18.095 - MD and use it in claud. You can 332 00:12:18.095 --> 00:12:19.455 - take a clog dot m d and use 333 00:12:19.455 --> 00:12:21.535 - it in anti gravity CLI. You can take 334 00:12:21.535 --> 00:12:23.855 - it using GitHub Copilot CI. So so that 335 00:12:23.855 --> 00:12:26.095 - context file becomes very portable. So you do 336 00:12:26.095 --> 00:12:27.634 - that, and that's where you 337 00:12:28.014 --> 00:12:31.215 - start. And then it's gonna create your, in 338 00:12:31.215 --> 00:12:32.970 - my case, a clog dot m d. 339 00:12:33.370 --> 00:12:36.009 - And in my Cloud dot md, I said, 340 00:12:36.009 --> 00:12:37.689 - okay. I'm gonna go do a little bit 341 00:12:37.689 --> 00:12:40.169 - of light iteration here on some of the 342 00:12:40.169 --> 00:12:40.669 - instructions 343 00:12:41.129 --> 00:12:43.049 - that that I want this thing to have, 344 00:12:43.049 --> 00:12:45.389 - right, and have for its context. 345 00:12:45.929 --> 00:12:48.475 - So that was I've got a root folder 346 00:12:48.495 --> 00:12:49.315 - called clippings. 347 00:12:49.774 --> 00:12:51.855 - I believe in the original gist, it's called, 348 00:12:51.855 --> 00:12:53.294 - like, raw. I don't know. It didn't sit 349 00:12:53.294 --> 00:12:54.335 - well with me. I was like, yeah. I'm 350 00:12:54.335 --> 00:12:56.414 - gonna put Obsidian clippings in here, like Obsidian 351 00:12:56.414 --> 00:12:58.335 - web clipper, so I call mine clippings. And 352 00:12:58.335 --> 00:13:00.434 - then I added a couple different Wiki directories, 353 00:13:00.654 --> 00:13:03.389 - so it automatically does one for it does, 354 00:13:03.389 --> 00:13:05.250 - like, Wiki slash sources, 355 00:13:06.029 --> 00:13:07.809 - entities, Wiki slash concepts. 356 00:13:08.429 --> 00:13:11.070 - I wanted Wiki slash people because I knew 357 00:13:11.070 --> 00:13:12.509 - I was gonna be putting things in there 358 00:13:12.509 --> 00:13:14.029 - about, like, the podcast and you and I, 359 00:13:14.029 --> 00:13:15.870 - so I wanted it to extract, like, Ben 360 00:13:15.870 --> 00:13:17.649 - and Scott or Ben and Scott together, 361 00:13:18.404 --> 00:13:20.264 - kinds of things. And then 362 00:13:20.725 --> 00:13:22.644 - all you do is go out and start 363 00:13:22.644 --> 00:13:25.044 - putting some markdown in that in my case, 364 00:13:25.044 --> 00:13:27.284 - my clippings directory. So the way I did 365 00:13:27.284 --> 00:13:30.830 - that is with Obsidian Web Clipper. So Obsidian 366 00:13:30.830 --> 00:13:32.910 - Web Clipper is available on every platform. It's 367 00:13:32.910 --> 00:13:35.149 - there on iOS and Android, so you can 368 00:13:35.149 --> 00:13:37.410 - use it on your mobile. It's there 369 00:13:38.430 --> 00:13:40.210 - on Edge and Chrome and Safari. 370 00:13:40.670 --> 00:13:43.245 - So any kind of thing that you end 371 00:13:43.245 --> 00:13:45.164 - up looking at on the web, all of 372 00:13:45.164 --> 00:13:47.964 - a sudden becomes a resource that you can 373 00:13:47.964 --> 00:13:49.644 - take and you could say, hey. I wanna 374 00:13:49.644 --> 00:13:51.904 - reason over this later in my Wiki. So 375 00:13:52.365 --> 00:13:54.445 - maybe you start small. Go grab, like, five 376 00:13:54.445 --> 00:13:57.120 - articles that you're interested in and put them 377 00:13:57.120 --> 00:13:59.700 - in there. And then all you do is, 378 00:14:00.399 --> 00:14:03.840 - say, ingest my clippings or ingest my raw 379 00:14:03.840 --> 00:14:06.320 - stuff, depending on how you set up that 380 00:14:06.320 --> 00:14:09.440 - directory and how you framed out your ingest 381 00:14:09.440 --> 00:14:11.894 - flow. And then it'll go, and it'll just 382 00:14:11.975 --> 00:14:14.295 - build this stuff out. I went and iterated 383 00:14:14.295 --> 00:14:16.654 - over mine a little bit. So I I 384 00:14:16.774 --> 00:14:17.835 - because I was using 385 00:14:18.295 --> 00:14:21.014 - Obsidian Web Clipper uses a template when it 386 00:14:21.014 --> 00:14:23.675 - loads data in, so I wanted 387 00:14:24.360 --> 00:14:27.320 - all my reasoned over data to also follow 388 00:14:27.320 --> 00:14:29.720 - a similar template. So it had a title, 389 00:14:29.720 --> 00:14:31.980 - a publish date, a create a date, tags, 390 00:14:32.600 --> 00:14:35.480 - reference resources, things like that. So I actually 391 00:14:35.480 --> 00:14:38.815 - created a template dot m d file, and 392 00:14:38.815 --> 00:14:40.575 - then I went back and I modified my 393 00:14:40.575 --> 00:14:43.055 - cloud context. And I said, okay. Hey. When 394 00:14:43.055 --> 00:14:44.195 - you ingest things, 395 00:14:44.495 --> 00:14:46.035 - make sure that the outputs 396 00:14:46.495 --> 00:14:48.675 - use this template. Super easy. Right? 397 00:14:49.295 --> 00:14:52.169 - So and you just start right there. 398 00:14:52.570 --> 00:14:53.070 - And 399 00:14:54.089 --> 00:14:55.769 - you start to get this little bit of, 400 00:14:55.769 --> 00:14:57.149 - like, this is interesting. 401 00:14:57.769 --> 00:14:59.289 - And then you start wondering what else you 402 00:14:59.289 --> 00:15:01.450 - can do with it. But it runs away 403 00:15:01.450 --> 00:15:03.230 - from you very fast because 404 00:15:04.089 --> 00:15:07.115 - you're ingesting text and maybe not just a 405 00:15:07.115 --> 00:15:09.675 - couple lines of text, but let's take that 406 00:15:09.675 --> 00:15:12.315 - m $3.65 pricing example. Right? I I wanna 407 00:15:12.315 --> 00:15:14.554 - build something that can go reason over that. 408 00:15:14.554 --> 00:15:16.894 - You're going and grabbing every pricing page, potentially 409 00:15:16.955 --> 00:15:19.274 - the images off those pages and doing, like, 410 00:15:19.274 --> 00:15:21.809 - OCR and computer vision over them. So it's 411 00:15:22.049 --> 00:15:24.850 - pages and hundreds of kilobytes of text that 412 00:15:24.850 --> 00:15:27.009 - you're putting in, which is heavy on the 413 00:15:27.009 --> 00:15:30.370 - token side, both on input and output. Yes. 414 00:15:30.370 --> 00:15:32.129 - So this is where something like maybe like 415 00:15:32.129 --> 00:15:33.830 - OpenRouter and a free solution 416 00:15:34.289 --> 00:15:35.889 - starts to run away from you a little 417 00:15:35.889 --> 00:15:38.625 - bit. So I did OpenRouter. I got by 418 00:15:38.625 --> 00:15:41.504 - with maybe, like, my first 10 clippings in 419 00:15:41.504 --> 00:15:43.584 - doing this. And when I ran out of 420 00:15:43.584 --> 00:15:44.944 - stuff in OpenRouter, I was like, well, I 421 00:15:44.944 --> 00:15:46.304 - just wanna see, like, how far I can 422 00:15:46.304 --> 00:15:48.065 - push this free thing. So I went over 423 00:15:48.065 --> 00:15:51.949 - to Anti Gravity, which was recently released, and 424 00:15:51.949 --> 00:15:54.750 - that uses Gemini and Gemini Flash under the 425 00:15:54.750 --> 00:15:57.230 - hood. Let me tell you, anti gravity burns 426 00:15:57.230 --> 00:15:59.070 - some tokens. I think I burned through all 427 00:15:59.070 --> 00:16:00.830 - my tokens in anti gravity, like, on my 428 00:16:00.990 --> 00:16:02.610 - after, like, my first two ingests, 429 00:16:02.990 --> 00:16:05.054 - and it burned them for, like, six days. 430 00:16:05.134 --> 00:16:06.735 - You have no more usage for the next 431 00:16:06.735 --> 00:16:07.394 - six days. 432 00:16:08.014 --> 00:16:10.195 - But what you do there is 433 00:16:10.654 --> 00:16:11.154 - LLMs, 434 00:16:11.855 --> 00:16:14.894 - they really like to overthink things. Right? And 435 00:16:14.894 --> 00:16:16.894 - so they'll start to do things like, you'll 436 00:16:16.894 --> 00:16:19.480 - notice these patterns when, in my case, I 437 00:16:19.480 --> 00:16:21.179 - was saying ingest my clippings. 438 00:16:21.559 --> 00:16:23.819 - I noticed every single time, no matter 439 00:16:24.199 --> 00:16:27.319 - which harness I was using or which model 440 00:16:27.319 --> 00:16:29.319 - I was using, all of them were doing 441 00:16:29.319 --> 00:16:31.934 - similar things. They would say, like, oh, well, 442 00:16:31.934 --> 00:16:33.955 - I need to go figure out how to 443 00:16:34.495 --> 00:16:37.535 - list your ingest directory. So every single one 444 00:16:37.535 --> 00:16:40.415 - was saying, thinking thinking thinking. Okay. I'm gonna 445 00:16:40.415 --> 00:16:42.735 - list your your ingest directory. So I'm gonna 446 00:16:42.735 --> 00:16:45.730 - go do, like, an lsstar.md 447 00:16:45.730 --> 00:16:48.289 - kinda thing. You can automate all that stuff. 448 00:16:48.289 --> 00:16:49.649 - You don't have to have the LLM do 449 00:16:49.649 --> 00:16:51.769 - it. So the trick is you come back 450 00:16:51.889 --> 00:16:53.330 - or you or you don't have to harness 451 00:16:53.330 --> 00:16:54.529 - and the model do it. So you come 452 00:16:54.529 --> 00:16:56.384 - back and you say, hey. I've got this 453 00:16:56.625 --> 00:16:58.705 - context file now, and we've come up with 454 00:16:58.705 --> 00:17:00.865 - a workflow. How can I automate this workflow? 455 00:17:00.865 --> 00:17:02.965 - Can we make parts of this workflow scriptable? 456 00:17:03.105 --> 00:17:04.244 - Just ask the question. 457 00:17:04.704 --> 00:17:06.625 - And in my case, like, the one that 458 00:17:06.625 --> 00:17:08.065 - I've been really living in, I called it 459 00:17:08.065 --> 00:17:09.664 - my brain bank. I said, hey. This is 460 00:17:09.664 --> 00:17:10.805 - Scott's second brain. 461 00:17:11.190 --> 00:17:13.269 - So it created me a Python script called 462 00:17:13.269 --> 00:17:14.470 - brain dot p y. 463 00:17:15.029 --> 00:17:17.750 - And off brain dot p y, it created 464 00:17:17.750 --> 00:17:18.970 - a number of subarguments. 465 00:17:19.509 --> 00:17:22.069 - So it took my ingest flow, and after, 466 00:17:22.069 --> 00:17:23.750 - like, three ingests and it had all the 467 00:17:23.750 --> 00:17:25.494 - context, and it kinda knew what it was 468 00:17:25.494 --> 00:17:27.654 - doing repeatedly, it built me a brain dot 469 00:17:27.654 --> 00:17:28.394 - p y, 470 00:17:29.015 --> 00:17:29.515 - slash 471 00:17:29.974 --> 00:17:33.095 - ingest or, like, dash ingest command. And then 472 00:17:33.095 --> 00:17:35.255 - I said, oh, hey. You're doing this. Why 473 00:17:35.255 --> 00:17:37.450 - don't you build me, like, a like a 474 00:17:37.450 --> 00:17:39.690 - linting command to make sure that you're always 475 00:17:39.690 --> 00:17:41.130 - matching up to my template? Because I used 476 00:17:41.130 --> 00:17:43.289 - to use spinning a lot of tokens trying 477 00:17:43.289 --> 00:17:44.970 - to go back and read that template dot 478 00:17:44.970 --> 00:17:46.809 - MD and then get it back rear. So 479 00:17:46.809 --> 00:17:48.990 - it made me brain dot p y lint, 480 00:17:49.204 --> 00:17:51.144 - made me brain dot p y organize, 481 00:17:51.525 --> 00:17:53.384 - made me brain dot p y, 482 00:17:55.204 --> 00:17:58.484 - clean up any old clippings, maybe, like, organize 483 00:17:58.484 --> 00:17:59.464 - them into subfolders, 484 00:18:00.005 --> 00:18:01.785 - things like that, link them back to sources. 485 00:18:01.924 --> 00:18:03.924 - So over time, I've been on this journey 486 00:18:03.924 --> 00:18:05.980 - of saying, hey. All the stuff that you're 487 00:18:05.980 --> 00:18:08.299 - doing that I see you're repeating yourself doing, 488 00:18:08.299 --> 00:18:10.619 - but it's you as, like, the LLM thinking 489 00:18:10.619 --> 00:18:12.460 - about it, just go slam that in my 490 00:18:12.460 --> 00:18:14.140 - script. Just keep putting it in there, putting 491 00:18:14.140 --> 00:18:15.579 - it in there, putting it in there. So 492 00:18:15.579 --> 00:18:17.339 - then you're not burning all the tokens. Like, 493 00:18:17.339 --> 00:18:19.475 - it doesn't have to and then you tell 494 00:18:19.475 --> 00:18:21.715 - it, go update my context file. So if 495 00:18:21.715 --> 00:18:23.955 - I look at how I started from, let's 496 00:18:23.955 --> 00:18:27.174 - say, like, my ingest flow in my claw.md, 497 00:18:27.555 --> 00:18:28.055 - originally, 498 00:18:28.674 --> 00:18:29.575 - that was 499 00:18:30.355 --> 00:18:31.575 - something like 500 00:18:32.140 --> 00:18:32.640 - go 501 00:18:33.420 --> 00:18:36.220 - it said, hey. Your vault structure for clippings, 502 00:18:36.220 --> 00:18:38.859 - things like that. So my operations for ingest 503 00:18:38.859 --> 00:18:42.000 - was, like, step one, go list this directory. 504 00:18:42.460 --> 00:18:44.960 - Now step one has turned into research. 505 00:18:45.259 --> 00:18:47.200 - Run Python three scripts 506 00:18:47.545 --> 00:18:49.565 - brain dot p y scan ingest, 507 00:18:50.105 --> 00:18:50.765 - and then 508 00:18:51.625 --> 00:18:54.345 - take that output and then go check this. 509 00:18:54.345 --> 00:18:56.664 - Go run brain dot p y again, get 510 00:18:56.664 --> 00:18:59.144 - this list output, compare those two things. So 511 00:18:59.144 --> 00:19:01.170 - that way, it doesn't have to, you know, 512 00:19:01.250 --> 00:19:04.210 - start immediately every single time enumerating a whole 513 00:19:04.210 --> 00:19:05.990 - directory and running over it 514 00:19:06.529 --> 00:19:08.130 - and being very heavy. So you can start 515 00:19:08.130 --> 00:19:10.289 - to very quickly, like, drive it down into, 516 00:19:10.289 --> 00:19:12.850 - like, scriptability and less and that was the 517 00:19:12.850 --> 00:19:14.369 - part that I kind of enjoyed. Right? Like, 518 00:19:14.369 --> 00:19:16.210 - IT pro hat. Like, hey. Let's go get 519 00:19:16.210 --> 00:19:17.914 - this going. I think you were doing some 520 00:19:17.914 --> 00:19:20.394 - PowerShell scripts and things on your side, 521 00:19:20.875 --> 00:19:23.275 - on the Windows side. But you just kinda 522 00:19:23.275 --> 00:19:24.714 - keep going down that path, going down that 523 00:19:24.714 --> 00:19:26.815 - path, going down that path. And then 524 00:19:27.595 --> 00:19:29.934 - because you're doing this all in an Obsidian 525 00:19:30.075 --> 00:19:32.130 - markdown style, now you go and open it 526 00:19:32.130 --> 00:19:35.170 - up in Obsidian. Just go open your project 527 00:19:35.170 --> 00:19:37.190 - directory and what you're doing in there, 528 00:19:37.650 --> 00:19:39.190 - and you'll get access to 529 00:19:39.570 --> 00:19:42.630 - all the features of Obsidian. So that includes 530 00:19:43.170 --> 00:19:46.315 - tagging. It includes searching. It includes the PKM 531 00:19:46.454 --> 00:19:47.674 - with the knowledge graph. 532 00:19:48.054 --> 00:19:48.554 - Obsidian's 533 00:19:48.934 --> 00:19:51.654 - like a canonical markdown editor. It's really darn 534 00:19:51.654 --> 00:19:53.414 - good at it. You and I had been 535 00:19:53.414 --> 00:19:55.575 - chatting about one of the ways we do 536 00:19:55.575 --> 00:19:57.414 - research for the podcast is by following a 537 00:19:57.414 --> 00:19:59.619 - bunch of RSS feeds. What's the easiest way 538 00:19:59.619 --> 00:20:01.940 - to ingest the RSS feed? Well, I've been 539 00:20:01.940 --> 00:20:05.059 - going through, like, Feedly or Reader and opening 540 00:20:05.059 --> 00:20:06.660 - it in a website and then hitting the 541 00:20:06.660 --> 00:20:09.140 - Obsidian web clipper and doing things like that. 542 00:20:09.140 --> 00:20:11.700 - There's this really cool plugin for Obsidian called 543 00:20:11.700 --> 00:20:13.894 - RSS dashboard where you can just follow an 544 00:20:13.894 --> 00:20:16.714 - RSS feed. And as you follow, it's 545 00:20:17.095 --> 00:20:19.575 - it and now because it's an Obsidian vault 546 00:20:19.575 --> 00:20:21.174 - and it's just marked down, and I can 547 00:20:21.174 --> 00:20:22.234 - have it in my OneDrive 548 00:20:22.535 --> 00:20:23.974 - or you can have it in your Google 549 00:20:23.974 --> 00:20:24.875 - Drive or whatever, 550 00:20:25.210 --> 00:20:27.769 - It's actually kinda like Feedly, and that suddenly 551 00:20:27.769 --> 00:20:29.769 - it's a cloud sync service. Right? It's following 552 00:20:29.769 --> 00:20:31.070 - you around in your configuration. 553 00:20:31.610 --> 00:20:34.490 - But RSS dashboard is really cool because every 554 00:20:34.490 --> 00:20:37.930 - feed article that comes through, you can just 555 00:20:37.930 --> 00:20:40.464 - click a red or an unread button to 556 00:20:40.464 --> 00:20:42.005 - to flag it or get rid of it. 557 00:20:42.144 --> 00:20:44.224 - But if you click save on it, it 558 00:20:44.224 --> 00:20:47.345 - has a really nifty templating system. So I 559 00:20:47.345 --> 00:20:49.345 - was able to take my template dot m 560 00:20:49.345 --> 00:20:51.184 - d, which, again, was just based on an 561 00:20:51.184 --> 00:20:54.240 - Obsidian web clipper kinda default template. But I 562 00:20:54.240 --> 00:20:56.160 - was able to make that my template for 563 00:20:56.160 --> 00:20:57.140 - RSS dashboard 564 00:20:57.599 --> 00:20:59.839 - and have it every time I saved an 565 00:20:59.839 --> 00:21:01.059 - article from RSS, 566 00:21:01.519 --> 00:21:04.079 - it saves it as markdown over in my 567 00:21:04.079 --> 00:21:07.039 - clippings directory automatically. Right? Like like like, yes, 568 00:21:07.039 --> 00:21:08.579 - I have to click save on the article, 569 00:21:09.045 --> 00:21:10.805 - but it gives me this kind of, like, 570 00:21:10.805 --> 00:21:12.025 - one stop shop 571 00:21:12.325 --> 00:21:15.445 - ingest flow to get those things kind kinda 572 00:21:15.445 --> 00:21:15.945 - through. 573 00:21:16.325 --> 00:21:20.565 - So really interesting way to go and kind 574 00:21:20.565 --> 00:21:22.345 - of reason over personal data, 575 00:21:22.725 --> 00:21:24.644 - really any kind of project that you're doing. 576 00:21:24.644 --> 00:21:26.779 - I I would recommend constraining this stuff. Think 577 00:21:26.779 --> 00:21:28.539 - about it maybe like, if you're coming from, 578 00:21:28.539 --> 00:21:29.039 - like, 579 00:21:29.340 --> 00:21:31.500 - if you're coming from Claude Land, maybe think 580 00:21:31.500 --> 00:21:33.820 - about it as, like, project based. Or if 581 00:21:33.820 --> 00:21:35.580 - you're coming from, like, the cowork side of 582 00:21:35.580 --> 00:21:36.160 - the house, 583 00:21:36.539 --> 00:21:39.019 - maybe you use, like, notebooks in cowork, things 584 00:21:39.019 --> 00:21:41.144 - like that. Like, let me group these documents 585 00:21:41.144 --> 00:21:42.664 - together so that I can go do some 586 00:21:42.664 --> 00:21:45.224 - research on them kinda thing. I do find 587 00:21:45.224 --> 00:21:46.984 - that, like, I I I think that they 588 00:21:46.984 --> 00:21:49.164 - do a lot better when it's kind of 589 00:21:49.544 --> 00:21:52.184 - same knowledge area to reason over rather than 590 00:21:52.184 --> 00:21:54.284 - having a whole bunch of different things there. 591 00:21:54.519 --> 00:21:56.440 - Because, again, you could see eventually, you get 592 00:21:56.440 --> 00:21:58.940 - back to, like, really heavy context windows and 593 00:21:59.160 --> 00:22:01.480 - and things like that that happen along the 594 00:22:01.480 --> 00:22:04.519 - way. But so let's talk about now hey. 595 00:22:04.519 --> 00:22:06.440 - Great. You did this in our RSS feed. 596 00:22:06.440 --> 00:22:08.634 - Or, alright. You told me that, like, I 597 00:22:08.634 --> 00:22:10.075 - could dig an article from the web, and 598 00:22:10.075 --> 00:22:12.015 - I can clip it in here. Sure. Whatever. 599 00:22:12.474 --> 00:22:13.454 - Copilot cowork. 600 00:22:13.835 --> 00:22:15.054 - And Copilot cowork, 601 00:22:15.595 --> 00:22:18.394 - the Frontier agent. So the Frontier agent that's 602 00:22:18.394 --> 00:22:21.194 - out there has custom skills. So you can 603 00:22:21.194 --> 00:22:21.660 - take 604 00:22:22.059 --> 00:22:23.039 - the very same 605 00:22:23.420 --> 00:22:24.480 - kind of flow 606 00:22:24.859 --> 00:22:25.359 - around 607 00:22:25.980 --> 00:22:26.960 - having a context, 608 00:22:27.420 --> 00:22:29.099 - in this case, like, the claw.md. 609 00:22:29.099 --> 00:22:31.099 - You can actually take everything that's in your 610 00:22:31.099 --> 00:22:32.059 - claw.md 611 00:22:32.059 --> 00:22:34.059 - and put it in a skill.md 612 00:22:34.059 --> 00:22:36.464 - inside Cowork. And you go, oh, well, that's 613 00:22:36.464 --> 00:22:38.305 - not helpful. Like, you're all you're doing is 614 00:22:38.305 --> 00:22:39.825 - telling me that I'm just using co work 615 00:22:39.825 --> 00:22:41.924 - to process my clippings and things like that. 616 00:22:42.144 --> 00:22:44.705 - I actually recommend going a step further. Create 617 00:22:44.705 --> 00:22:45.845 - yourself skills 618 00:22:46.144 --> 00:22:47.765 - that do things like 619 00:22:48.179 --> 00:22:50.839 - take take the emails in my inbox 620 00:22:51.539 --> 00:22:52.039 - and 621 00:22:52.500 --> 00:22:55.299 - save them into my ingest directory as markdown, 622 00:22:55.299 --> 00:22:57.139 - and it'll take all your emails for that 623 00:22:57.139 --> 00:22:59.700 - day. Like, I've I've somebody on my team 624 00:22:59.700 --> 00:23:01.835 - did this, and it's super cool. He has 625 00:23:01.835 --> 00:23:03.214 - it so Cowork 626 00:23:03.515 --> 00:23:06.634 - looks at his inbox every day. It takes 627 00:23:06.634 --> 00:23:08.255 - all the items in his inbox, 628 00:23:08.714 --> 00:23:10.714 - and it turns them into markdown. And then 629 00:23:10.714 --> 00:23:12.555 - once they've been turned into markdown, they just 630 00:23:12.555 --> 00:23:14.315 - get marked as read and archived because now 631 00:23:14.315 --> 00:23:16.394 - they're sitting over in markdown, right, just in 632 00:23:16.394 --> 00:23:17.214 - in his OneDrive. 633 00:23:17.730 --> 00:23:20.609 - And then he runs an LLM Wiki style 634 00:23:20.609 --> 00:23:22.630 - kinda thing on top of it to 635 00:23:23.009 --> 00:23:25.089 - extract what are his priorities for the day. 636 00:23:25.089 --> 00:23:26.690 - Maybe he got an email from me or 637 00:23:26.690 --> 00:23:28.450 - he got an email from a coworker or 638 00:23:28.450 --> 00:23:31.329 - he's got specific projects that he flagged, things 639 00:23:31.329 --> 00:23:34.005 - like that. And then he has this set 640 00:23:34.005 --> 00:23:36.325 - of skills that iterate over it, and I've 641 00:23:36.325 --> 00:23:38.244 - been playing with this too. It actually works 642 00:23:38.244 --> 00:23:39.224 - really darn well. 643 00:23:39.605 --> 00:23:41.224 - You can take those things, 644 00:23:41.605 --> 00:23:44.804 - reason over them, create your own personal knowledge 645 00:23:44.804 --> 00:23:47.730 - management vault just inside of your OneDrive for 646 00:23:47.730 --> 00:23:51.410 - business. Obsidian's free. You're effectively getting cloud sync 647 00:23:51.410 --> 00:23:53.090 - because you got markdowns. So if you're in, 648 00:23:53.090 --> 00:23:54.610 - like, you're in, like, oh, hey. I need 649 00:23:54.610 --> 00:23:56.450 - to get to this on my work phone 650 00:23:56.450 --> 00:23:58.450 - or things like that, run Obsidian on your 651 00:23:58.450 --> 00:24:00.210 - work phone. Just point it at your One 652 00:24:00.210 --> 00:24:01.785 - OneDrive directory. It's okay. 653 00:24:02.184 --> 00:24:04.105 - It it'll all work. And then you get 654 00:24:04.105 --> 00:24:07.545 - to start thinking about, like, richer functionality within 655 00:24:07.545 --> 00:24:09.465 - Obsidian. So this was the thing that unlocked 656 00:24:09.465 --> 00:24:11.644 - it for me in the Copilot Cowork scenario 657 00:24:11.945 --> 00:24:14.769 - was not just, like, reason over what happened 658 00:24:14.769 --> 00:24:17.329 - today and maybe give me a, like, a 659 00:24:17.329 --> 00:24:19.329 - table. Like, tell me, like, the top three 660 00:24:19.329 --> 00:24:21.430 - people who emailed me or things like that. 661 00:24:21.890 --> 00:24:24.230 - But Obsidian has plugins 662 00:24:24.849 --> 00:24:25.349 - and 663 00:24:26.130 --> 00:24:29.109 - Wiki style markdown for things like task lists. 664 00:24:29.355 --> 00:24:31.674 - So you can actually have it, like, take 665 00:24:31.914 --> 00:24:34.075 - if you got 50 emails last night and 666 00:24:34.075 --> 00:24:35.375 - you walk in the morning, 667 00:24:35.914 --> 00:24:38.095 - you can have it take those 50 emails, 668 00:24:38.154 --> 00:24:39.914 - reason over them, do whatever it needs to 669 00:24:39.914 --> 00:24:41.595 - do, and create, like, your to do list 670 00:24:41.595 --> 00:24:43.115 - for the day. And then you actually get, 671 00:24:43.115 --> 00:24:45.119 - like, a clickable to do list, not in 672 00:24:45.119 --> 00:24:47.359 - Planner or anything like that. Like, you can 673 00:24:47.359 --> 00:24:49.279 - just put it in Obsidian and have it 674 00:24:49.279 --> 00:24:51.859 - there and ready to go, and it's very, 675 00:24:52.079 --> 00:24:54.740 - very portable. And because Copilot Cowork 676 00:24:55.200 --> 00:24:57.519 - has access to, like, your team's messages and 677 00:24:57.519 --> 00:24:59.714 - your inbox and all these things, You can 678 00:24:59.714 --> 00:25:01.795 - have it, like, mark your email as read 679 00:25:01.795 --> 00:25:04.194 - and archive it. You can have it organize 680 00:25:04.194 --> 00:25:05.954 - your email for it as it's doing this 681 00:25:05.954 --> 00:25:08.115 - extraction and pushing things out. You might have 682 00:25:08.115 --> 00:25:09.795 - it like, in my case, I get a 683 00:25:09.795 --> 00:25:11.494 - lot of, like, junk mail and newsletters. 684 00:25:12.029 --> 00:25:13.789 - So no matter how hard I try and 685 00:25:13.789 --> 00:25:15.789 - filter those things out, some always make it 686 00:25:15.789 --> 00:25:18.029 - into my inbox or my inbox other things 687 00:25:18.029 --> 00:25:20.289 - like that. So I can have that flow 688 00:25:20.430 --> 00:25:21.890 - come back and 689 00:25:22.269 --> 00:25:24.674 - clean that up as well. Right? Like, say, 690 00:25:24.674 --> 00:25:27.475 - hey. It notices there's a newsletter there. I 691 00:25:27.475 --> 00:25:29.394 - don't have to worry about creating a custom 692 00:25:29.394 --> 00:25:31.975 - rule for it anymore. I've just got Cowork 693 00:25:32.115 --> 00:25:34.375 - dumping that stuff off to a newsletter directory. 694 00:25:34.674 --> 00:25:37.150 - And then part of my ingest flow, because 695 00:25:37.150 --> 00:25:39.470 - it's still ingesting those things into my Wiki, 696 00:25:39.470 --> 00:25:41.309 - is telling me what newsletters I got that 697 00:25:41.309 --> 00:25:42.990 - day just in case there was something there 698 00:25:42.990 --> 00:25:45.150 - that I wanted to read or or things 699 00:25:45.150 --> 00:25:47.710 - like that. So you can absolutely take this 700 00:25:47.710 --> 00:25:48.210 - concept 701 00:25:48.509 --> 00:25:50.369 - and pull it over to 702 00:25:50.670 --> 00:25:53.255 - the world of things like Copilot, Cowork, 703 00:25:53.875 --> 00:25:56.434 - and all of that. Or if you wanted 704 00:25:56.434 --> 00:25:58.595 - to yeah. I've seen a couple folks do 705 00:25:58.595 --> 00:25:59.654 - this with 706 00:26:00.275 --> 00:26:03.174 - just something like GitHub Copilot and WorkIQ 707 00:26:04.115 --> 00:26:04.615 - or 708 00:26:04.940 --> 00:26:05.440 - Copilot 709 00:26:06.140 --> 00:26:06.640 - CLI, 710 00:26:07.660 --> 00:26:10.140 - Claude with the, like, the WorkIQ MCP and 711 00:26:10.140 --> 00:26:11.660 - things like that as well. The problem with 712 00:26:11.660 --> 00:26:14.140 - the WorkIQ MCP is I've had way better 713 00:26:14.140 --> 00:26:16.940 - luck with, like, Copilot coworkers saying, actually, like, 714 00:26:16.940 --> 00:26:19.494 - move this message from here to here. WorkIQ 715 00:26:19.634 --> 00:26:22.595 - is, like, glorified graph reader. So you end 716 00:26:22.595 --> 00:26:24.674 - up in some weird throttling scenarios and other 717 00:26:24.674 --> 00:26:28.195 - things that CoPilot CoWorks seems to generally skirt 718 00:26:28.195 --> 00:26:28.695 - around. 719 00:26:30.674 --> 00:26:33.475 - You're out of time. CoPilot needs to be 720 00:26:33.475 --> 00:26:36.650 - deployed ASAP, but is your tenant really ready 721 00:26:36.650 --> 00:26:39.789 - for it? Years of data, permissions, and users 722 00:26:39.930 --> 00:26:42.509 - lurk in its shadows, ready to be exposed 723 00:26:42.570 --> 00:26:43.390 - by AI. 724 00:26:43.690 --> 00:26:46.490 - Sharegate Protect sees it all, so you can 725 00:26:46.490 --> 00:26:49.545 - find the exposure risks, fix them fast, and 726 00:26:49.545 --> 00:26:51.244 - deploy AI with confidence. 727 00:26:51.545 --> 00:26:52.045 - Microsoft 728 00:26:52.424 --> 00:26:55.625 - three sixty five governance. We got this. Learn 729 00:26:55.625 --> 00:26:59.884 - more at sharegate.com/governance. 730 00:27:03.089 --> 00:27:05.649 - Have you tried it the other way where 731 00:27:05.649 --> 00:27:07.730 - once you have your Obsidian Vault and you're 732 00:27:07.730 --> 00:27:09.190 - syncing it down with OneDrive, 733 00:27:09.809 --> 00:27:10.869 - you save articles 734 00:27:11.490 --> 00:27:13.829 - into your raw folder in OneDrive 735 00:27:14.654 --> 00:27:18.095 - and have Copilot Cowork actually ingest all the 736 00:27:18.095 --> 00:27:19.615 - stuff you're saving locally 737 00:27:19.934 --> 00:27:21.634 - Yeah. And then just use 738 00:27:21.934 --> 00:27:24.894 - so you use Copilot Cowork for everything. Yes. 739 00:27:24.894 --> 00:27:27.430 - Use Copilot Cowork as the harness. As the 740 00:27:27.430 --> 00:27:29.990 - LLM, the harness. Yep. Where I said, hey. 741 00:27:29.990 --> 00:27:31.349 - When we started in the beginning, I said, 742 00:27:31.349 --> 00:27:32.950 - hey. I was doing this in Claude with 743 00:27:32.950 --> 00:27:35.670 - open router. Replace Claude and open router with 744 00:27:35.670 --> 00:27:36.730 - CoPilot CoWork, 745 00:27:37.430 --> 00:27:39.944 - the Frontier agent. And then you just switch 746 00:27:39.944 --> 00:27:42.424 - from doing everything in the CLI to going 747 00:27:42.424 --> 00:27:44.125 - into Cowork and starting 748 00:27:44.744 --> 00:27:45.244 - conversations 749 00:27:46.105 --> 00:27:48.345 - in Cowork in the browser for all the 750 00:27:48.345 --> 00:27:49.484 - ingesting and 751 00:27:49.865 --> 00:27:53.049 - processing that raw data. Yes to starting. But 752 00:27:53.049 --> 00:27:53.849 - once you're like 753 00:27:54.570 --> 00:27:56.490 - let's do, like, the crawl, walk, run thing. 754 00:27:56.490 --> 00:27:58.490 - So I think crawl is us walking in 755 00:27:58.490 --> 00:28:00.089 - there and typing all the time and kicking 756 00:28:00.089 --> 00:28:02.430 - these things off. Once you have a refined 757 00:28:02.650 --> 00:28:05.565 - workflow, Copilot Cowork lets you schedule this stuff. 758 00:28:05.644 --> 00:28:07.825 - And if you're structuring it in a way 759 00:28:08.125 --> 00:28:10.684 - where you're being principled, like in my case, 760 00:28:10.684 --> 00:28:12.144 - with my local 761 00:28:12.524 --> 00:28:14.444 - vault here that I was using for, like, 762 00:28:14.444 --> 00:28:17.345 - ingesting RSS feed articles and things like that. 763 00:28:17.484 --> 00:28:18.784 - So in that one, 764 00:28:19.085 --> 00:28:20.144 - I'm sitting in, 765 00:28:21.539 --> 00:28:23.880 - I'm sitting in a world of that workflow. 766 00:28:24.180 --> 00:28:26.019 - That's really like an on demand thing. Right? 767 00:28:26.019 --> 00:28:27.619 - Like, I don't always have clippings in there. 768 00:28:27.619 --> 00:28:29.059 - I don't need it to be looking once 769 00:28:29.059 --> 00:28:31.059 - an hour or anything like that. Emails are 770 00:28:31.059 --> 00:28:33.059 - coming in all day. So I can have 771 00:28:33.059 --> 00:28:33.960 - that skill 772 00:28:34.340 --> 00:28:37.080 - run every hour and do that ingest 773 00:28:37.394 --> 00:28:39.335 - hourly. So I don't even have to live 774 00:28:39.715 --> 00:28:41.394 - in Outlook. I can just go live in 775 00:28:41.394 --> 00:28:44.115 - Obsidian. It's kinda kinda kinda nice. The other 776 00:28:44.115 --> 00:28:45.015 - thing too is 777 00:28:45.315 --> 00:28:48.035 - I talked about the concept of, like, taking 778 00:28:48.035 --> 00:28:50.035 - some of the heavier operations and going and 779 00:28:50.035 --> 00:28:52.190 - putting those in scripts and things like that, 780 00:28:52.250 --> 00:28:53.849 - you can still do that in co work 781 00:28:53.849 --> 00:28:56.269 - because co work can execute local flows. 782 00:28:57.210 --> 00:28:58.990 - Or the other approach that you could take 783 00:28:59.049 --> 00:28:59.789 - would be 784 00:29:00.490 --> 00:29:02.649 - to really think about maybe rather than, like, 785 00:29:02.649 --> 00:29:03.789 - scripts and functions 786 00:29:04.250 --> 00:29:05.950 - to just skills and functions. 787 00:29:06.265 --> 00:29:08.664 - So having kind of the building blocks sitting 788 00:29:08.664 --> 00:29:10.365 - inside of composable skills 789 00:29:10.664 --> 00:29:13.625 - that then you can stack per scheduled task 790 00:29:13.625 --> 00:29:15.304 - or whatever you wanna do on on on 791 00:29:15.304 --> 00:29:17.785 - the CoWork side. Interesting. There was another question 792 00:29:17.785 --> 00:29:19.919 - I was gonna ask about this, and I 793 00:29:19.919 --> 00:29:22.339 - can't remember what it was. Adjusting, scheduling, 794 00:29:22.960 --> 00:29:23.460 - oh, 795 00:29:23.919 --> 00:29:24.900 - have you compared 796 00:29:25.599 --> 00:29:27.359 - so this has always been a debate too, 797 00:29:27.359 --> 00:29:28.339 - right, is how 798 00:29:28.960 --> 00:29:32.555 - Copilot does in terms of responses versus something 799 00:29:32.555 --> 00:29:34.494 - like Claude or 800 00:29:34.875 --> 00:29:36.875 - any of those. Have you compared the LLM 801 00:29:36.875 --> 00:29:38.955 - that gets built or the Wiki that gets 802 00:29:38.955 --> 00:29:40.875 - built by Cowork versus a Wiki that gets 803 00:29:40.875 --> 00:29:41.775 - built by Claude 804 00:29:42.075 --> 00:29:42.975 - just to see 805 00:29:43.355 --> 00:29:44.494 - side by side 806 00:29:45.230 --> 00:29:46.910 - how I know CoWork is different because a 807 00:29:46.910 --> 00:29:48.430 - lot of it I don't know that there's 808 00:29:48.430 --> 00:29:50.690 - as many system prompts injected into 809 00:29:51.070 --> 00:29:51.570 - CoWork 810 00:29:51.950 --> 00:29:54.269 - given that things like DLP don't even work 811 00:29:54.269 --> 00:29:57.230 - in it versus the normal Copilot. I feel 812 00:29:57.230 --> 00:29:59.730 - like the system prompts are are still there. 813 00:30:00.164 --> 00:30:01.085 - You do have 814 00:30:01.525 --> 00:30:03.065 - depending on your tenant configuration, 815 00:30:03.845 --> 00:30:06.085 - you do have model selection or at least 816 00:30:06.085 --> 00:30:08.184 - model I would call it model selection light. 817 00:30:08.404 --> 00:30:10.164 - Like, in my case, I can choose a 818 00:30:10.164 --> 00:30:11.545 - couple variants of GPT 819 00:30:12.725 --> 00:30:13.545 - and a couple 820 00:30:13.845 --> 00:30:14.985 - anthropic models. 821 00:30:15.420 --> 00:30:17.740 - You do get much richer model selection when 822 00:30:17.740 --> 00:30:18.880 - you're over on a CLI 823 00:30:19.259 --> 00:30:22.059 - or, like, a GitHub Copilot chat kind of 824 00:30:22.059 --> 00:30:22.559 - experience. 825 00:30:23.100 --> 00:30:24.880 - But the nice thing is 826 00:30:25.180 --> 00:30:27.740 - you're talking one vault that just lives out 827 00:30:27.820 --> 00:30:29.740 - or a series of vaults. It's all just 828 00:30:29.740 --> 00:30:31.595 - text, right, that that lives out here in 829 00:30:31.595 --> 00:30:33.934 - a side card. So you're not restricted 830 00:30:34.234 --> 00:30:34.734 - to 831 00:30:35.194 --> 00:30:39.054 - just Copilot co work or just GitHub Copilot 832 00:30:39.115 --> 00:30:41.115 - CLI. You could augment this. Yeah. You can 833 00:30:41.115 --> 00:30:43.274 - augment this and kind of go in. So, 834 00:30:43.274 --> 00:30:44.954 - like, for me, I tend to live in 835 00:30:44.954 --> 00:30:45.534 - the terminal. 836 00:30:46.049 --> 00:30:49.330 - So I'm not going in, like, during the 837 00:30:49.330 --> 00:30:52.769 - day. I don't actually, like, worry about going 838 00:30:52.769 --> 00:30:55.009 - into cowork and to ever typing a question 839 00:30:55.009 --> 00:30:57.650 - in a cowork. Cowork's a harness for me 840 00:30:57.650 --> 00:30:59.954 - to go and run skills, do the extraction, 841 00:31:00.515 --> 00:31:03.514 - kinda Right. Compound value and compound knowledge over 842 00:31:03.514 --> 00:31:05.634 - the course of a day, a week, a 843 00:31:05.634 --> 00:31:07.174 - month, things like that. 844 00:31:07.474 --> 00:31:09.075 - But when I'm going in and I'm going 845 00:31:09.075 --> 00:31:09.575 - across 846 00:31:10.034 --> 00:31:12.214 - and I'm saying, hey. Look at this stuff. 847 00:31:12.319 --> 00:31:14.500 - I'm typically doing that through 848 00:31:14.960 --> 00:31:18.259 - the CLI or, like, just just, like, GitHub 849 00:31:18.319 --> 00:31:21.599 - Copilot chat, things like that. Now the other 850 00:31:21.599 --> 00:31:24.099 - interesting thing that I found here is 851 00:31:24.595 --> 00:31:27.475 - it starts to make the data that you 852 00:31:27.475 --> 00:31:27.975 - extract 853 00:31:28.355 --> 00:31:29.654 - a little bit more deterministic. 854 00:31:30.515 --> 00:31:31.015 - So 855 00:31:31.634 --> 00:31:34.115 - it's a weird black box when you go 856 00:31:34.115 --> 00:31:34.934 - into Copilot 857 00:31:35.394 --> 00:31:37.920 - or you go into co Copilot cowork, and 858 00:31:37.920 --> 00:31:39.680 - you say, take a look at all my 859 00:31:39.680 --> 00:31:40.820 - emails from today 860 00:31:41.200 --> 00:31:41.700 - and 861 00:31:42.080 --> 00:31:45.360 - extract StackRank my top three priorities. Right? You 862 00:31:45.360 --> 00:31:47.360 - never know. Is it actually gonna search all 863 00:31:47.360 --> 00:31:48.960 - my emails for the day? What is what 864 00:31:48.960 --> 00:31:50.480 - does it consider an email for a day? 865 00:31:50.480 --> 00:31:52.000 - Is it only looking at my inbox? Is 866 00:31:52.000 --> 00:31:53.724 - it looking at my inbox plus my inbox 867 00:31:54.184 --> 00:31:56.345 - other? In my case, I run inbox inbox 868 00:31:56.345 --> 00:31:58.585 - other, and I do the Scott Hanselman inbox 869 00:31:58.585 --> 00:32:00.744 - cc things. I got I really got three 870 00:32:00.744 --> 00:32:02.744 - inboxes. Right? So I never know, like, what 871 00:32:02.744 --> 00:32:04.984 - it's looking at and what it's doing. But 872 00:32:04.984 --> 00:32:07.305 - by extracting the data and pulling it out 873 00:32:07.305 --> 00:32:09.559 - and sidecarring it, when I say go look 874 00:32:09.559 --> 00:32:12.039 - at today, today is a very real thing. 875 00:32:12.039 --> 00:32:14.680 - It's a discrete set of data that sits 876 00:32:14.680 --> 00:32:16.940 - out there and is available. 877 00:32:17.559 --> 00:32:20.599 - And and I found that accuracy has kind 878 00:32:20.599 --> 00:32:23.394 - of improved there. I have, like, far more 879 00:32:23.694 --> 00:32:25.394 - confidence that it 880 00:32:25.855 --> 00:32:27.375 - can can do what it needs to do. 881 00:32:27.375 --> 00:32:28.835 - Have you run into 882 00:32:29.454 --> 00:32:29.954 - anything, 883 00:32:30.575 --> 00:32:32.974 - like, using co work to your point earlier 884 00:32:32.974 --> 00:32:34.654 - about it can be expensive? Sorry. I think 885 00:32:34.654 --> 00:32:35.460 - I have a meeting up. 886 00:32:41.220 --> 00:32:43.460 - This episode is brought to you by Trusted 887 00:32:43.460 --> 00:32:46.500 - Tech. If you're managing Microsoft three sixty five, 888 00:32:46.500 --> 00:32:48.759 - you already know licensing isn't simple. 889 00:32:49.144 --> 00:32:51.224 - E three versus e five, the brand new 890 00:32:51.224 --> 00:32:52.204 - e seven licenses, 891 00:32:52.585 --> 00:32:55.704 - Copilot security bundles, and with price changes coming 892 00:32:55.704 --> 00:32:56.664 - in July 893 00:32:56.664 --> 00:32:59.944 - 2026, the stakes are getting higher. Trusted Tech 894 00:32:59.944 --> 00:33:02.524 - helps IT leaders make sense of their Microsoft 895 00:33:02.585 --> 00:33:05.150 - three sixty five environment with a free licensing 896 00:33:05.210 --> 00:33:05.710 - consultation. 897 00:33:06.250 --> 00:33:09.049 - Their engineers analyze what you're licensed for and 898 00:33:09.049 --> 00:33:11.450 - what you're actually using and where you can 899 00:33:11.450 --> 00:33:13.549 - optimize, whether that means consolidating 900 00:33:13.929 --> 00:33:17.529 - security tools, preparing for Copilot, or eliminating wasted 901 00:33:17.529 --> 00:33:19.975 - spend. Plus, they offer proactive 902 00:33:20.434 --> 00:33:23.154 - and reactive support, which has been awarded yet 903 00:33:23.154 --> 00:33:25.975 - another solution partner designation from Microsoft 904 00:33:26.595 --> 00:33:28.055 - for support services. 905 00:33:28.434 --> 00:33:30.855 - If you want a clear, data backed plan 906 00:33:30.914 --> 00:33:33.154 - that has helped over 7,500 907 00:33:33.154 --> 00:33:33.654 - subscribing 908 00:33:34.170 --> 00:33:34.670 - customers 909 00:33:35.369 --> 00:33:37.818 - save up to 20% on Microsoft three sixty 910 00:33:37.818 --> 00:33:38.830 - five before your next renewal, 911 00:33:39.609 --> 00:33:46.250 - visit trustedtech.team/mscloudprom365 912 00:33:46.250 --> 00:33:48.454 - and schedule your free consultation 913 00:33:48.755 --> 00:33:49.255 - today. 914 00:33:54.355 --> 00:33:56.355 - Okay. I have a meeting at four. Where 915 00:33:56.355 --> 00:33:58.194 - you run into some of that quotas and 916 00:33:58.194 --> 00:33:59.954 - stuff? Like, I did mine. I did the 917 00:33:59.954 --> 00:34:03.240 - podcast. It was granted, it was 400 and, 918 00:34:03.240 --> 00:34:04.859 - what, 28 episodes. 919 00:34:05.480 --> 00:34:07.099 - I had all the transcripts, 920 00:34:07.480 --> 00:34:09.980 - so it was some big text documents, like 921 00:34:10.039 --> 00:34:11.880 - thirty minutes of talking turns into a lot 922 00:34:11.880 --> 00:34:14.139 - of text. And I was using 923 00:34:14.715 --> 00:34:16.735 - Claude, and I was doing the 924 00:34:17.755 --> 00:34:18.735 - Claude Max 925 00:34:19.275 --> 00:34:21.755 - five x. So this is the $100 a 926 00:34:21.755 --> 00:34:23.914 - month plan on Claude, and you get, like, 927 00:34:23.914 --> 00:34:26.414 - a five hour quota. When I started ingesting 928 00:34:26.555 --> 00:34:27.614 - podcast episodes, 929 00:34:28.089 --> 00:34:30.650 - and even I experienced this even. I tried 930 00:34:30.650 --> 00:34:32.010 - to put a bunch of stuff in Python, 931 00:34:32.010 --> 00:34:33.609 - do as much as I could still burn 932 00:34:33.609 --> 00:34:35.789 - through my five hours of quota in, like, 933 00:34:35.849 --> 00:34:36.670 - twelve minutes. 934 00:34:36.969 --> 00:34:39.130 - It was crazy how quick I burned through 935 00:34:39.130 --> 00:34:39.630 - tokens. 936 00:34:40.089 --> 00:34:40.569 - Did you 937 00:34:41.275 --> 00:34:43.755 - how much did you test cohort to see 938 00:34:43.755 --> 00:34:45.714 - if during the ingest or have you noticed 939 00:34:45.914 --> 00:34:47.295 - do you start getting 940 00:34:47.755 --> 00:34:50.235 - throttled or limited where it's like, okay. Go 941 00:34:50.235 --> 00:34:52.954 - use something else to your point for that 942 00:34:52.954 --> 00:34:55.210 - initial if you're gonna ingest a bunch of 943 00:34:55.210 --> 00:34:57.130 - stuff, or do you have to start being 944 00:34:57.130 --> 00:34:59.210 - careful about how often or how much you're 945 00:34:59.210 --> 00:35:00.510 - ingesting yet? 946 00:35:00.970 --> 00:35:02.890 - I can imagine it might you might start 947 00:35:02.890 --> 00:35:05.050 - getting limits eventually. Yes. You do have to 948 00:35:05.050 --> 00:35:06.910 - be careful. So so I think the 949 00:35:07.235 --> 00:35:09.795 - interesting thing here and the callout that I 950 00:35:09.795 --> 00:35:11.655 - keep coming back to is 951 00:35:11.994 --> 00:35:14.914 - and you're nailing it, is the context windows 952 00:35:14.914 --> 00:35:17.315 - and the token usage, both on inputs and 953 00:35:17.315 --> 00:35:19.255 - output, does get very heavy. 954 00:35:19.635 --> 00:35:20.135 - So 955 00:35:20.755 --> 00:35:22.295 - I I think this is someplace 956 00:35:23.130 --> 00:35:25.849 - where I would be inclined to think that 957 00:35:25.849 --> 00:35:27.609 - folks in our community would be able to 958 00:35:27.609 --> 00:35:30.170 - wrangle this pretty well given kind of their 959 00:35:30.170 --> 00:35:31.150 - backgrounds as 960 00:35:31.529 --> 00:35:32.029 - developers, 961 00:35:32.569 --> 00:35:36.125 - IT pros, more experienced end users. You have 962 00:35:36.125 --> 00:35:38.464 - to think a little bit like that scriptwriter 963 00:35:38.925 --> 00:35:39.905 - or that programmer. 964 00:35:40.284 --> 00:35:42.065 - So your job isn't just 965 00:35:42.364 --> 00:35:44.284 - to have a big context window that you're 966 00:35:44.284 --> 00:35:46.684 - firing off every single time. It's kinda like 967 00:35:46.684 --> 00:35:47.824 - ruthless optimization. 968 00:35:48.125 --> 00:35:49.484 - Get this down to here. Get this down 969 00:35:49.484 --> 00:35:50.980 - to here. Get this down to here. So 970 00:35:50.980 --> 00:35:52.920 - so what I realized was 971 00:35:53.380 --> 00:35:55.460 - when I went and did this on my 972 00:35:55.460 --> 00:35:58.019 - own, just kinda same thing over in, like, 973 00:35:58.019 --> 00:36:00.579 - Claude with open router, blah blah blah, and 974 00:36:00.579 --> 00:36:01.940 - I too had to switch over to my 975 00:36:01.940 --> 00:36:04.119 - paid Claude plan. Don't get me wrong. Like, 976 00:36:04.235 --> 00:36:05.675 - it it it didn't get me all the 977 00:36:05.675 --> 00:36:06.735 - way there. It's expensive. 978 00:36:07.275 --> 00:36:08.554 - I think one of the reasons it didn't 979 00:36:08.554 --> 00:36:10.094 - get me all there all the way there 980 00:36:10.235 --> 00:36:12.155 - because I didn't think about, like, a programmer 981 00:36:12.155 --> 00:36:12.974 - from the start. 982 00:36:13.355 --> 00:36:15.195 - And I I just kind of approached as, 983 00:36:15.195 --> 00:36:18.550 - like, the spirit of what mister Kabathea put 984 00:36:18.550 --> 00:36:20.150 - out there of, hey. Here's an LL on 985 00:36:20.150 --> 00:36:21.670 - Wiki, and you give it a simple set 986 00:36:21.670 --> 00:36:22.409 - of instructions, 987 00:36:22.869 --> 00:36:25.030 - which I I recognize a lot of these 988 00:36:25.030 --> 00:36:26.949 - folks who are putting these things out there. 989 00:36:26.949 --> 00:36:28.710 - They do live in a world of unlimited 990 00:36:28.710 --> 00:36:31.589 - tokens. Right? They work at Anthropic, and they 991 00:36:31.589 --> 00:36:33.074 - work at OpenAI 992 00:36:33.614 --> 00:36:35.375 - and things like that, and not all of 993 00:36:35.375 --> 00:36:36.434 - us have that luxury. 994 00:36:37.054 --> 00:36:38.974 - So you do have to kinda think about 995 00:36:38.974 --> 00:36:41.614 - that and start to refine things. I have 996 00:36:41.614 --> 00:36:42.114 - noticed 997 00:36:42.494 --> 00:36:44.755 - I I will say so I I mentioned 998 00:36:44.815 --> 00:36:46.755 - I've built a couple of these now. 999 00:36:47.769 --> 00:36:49.929 - So the first one, I really went down 1000 00:36:49.929 --> 00:36:52.909 - that refine refine path. Now I have this 1001 00:36:53.210 --> 00:36:54.429 - really solid 1002 00:36:54.889 --> 00:36:57.929 - templated thing that already has the scripts from 1003 00:36:57.929 --> 00:36:59.949 - day zero. So when it starts, 1004 00:37:00.364 --> 00:37:03.025 - it's already starting in a more optimized state 1005 00:37:03.164 --> 00:37:05.484 - rather than having to start from scratch every 1006 00:37:05.484 --> 00:37:07.484 - single time. So you kinda carry that knowledge 1007 00:37:07.484 --> 00:37:09.984 - forward, and that helped me a whole bunch 1008 00:37:10.045 --> 00:37:13.005 - when I was thinking about the Copilot Cowork 1009 00:37:13.005 --> 00:37:15.179 - side of it. And then it really started 1010 00:37:15.179 --> 00:37:16.619 - to click for me when I saw one 1011 00:37:16.619 --> 00:37:17.360 - of my coworkers 1012 00:37:17.900 --> 00:37:20.559 - who was in the mixed modality of Copilot 1013 00:37:20.619 --> 00:37:21.119 - Cowork 1014 00:37:21.579 --> 00:37:23.440 - for things like email extraction, 1015 00:37:23.739 --> 00:37:25.179 - but then they were on they were still 1016 00:37:25.179 --> 00:37:27.545 - on the CLI and doing, like, native Obsidian 1017 00:37:27.545 --> 00:37:29.465 - Web Clipper things and all that stuff. Right? 1018 00:37:29.465 --> 00:37:32.285 - Like, they were kinda using multiple tools 1019 00:37:32.585 --> 00:37:34.364 - all to have the data coalesced 1020 00:37:34.825 --> 00:37:35.325 - into 1021 00:37:35.864 --> 00:37:36.925 - a single source. 1022 00:37:37.465 --> 00:37:38.585 - And, effectively, like 1023 00:37:39.320 --> 00:37:41.880 - I mean, Obsidian's markdown, you can make it 1024 00:37:41.880 --> 00:37:44.619 - look pretty, all those things. It has checkboxes 1025 00:37:44.920 --> 00:37:47.239 - and tables, and you can put images in. 1026 00:37:47.239 --> 00:37:50.119 - Like, is it as rich text as something 1027 00:37:50.119 --> 00:37:53.474 - like OneNote is? Absolutely not. But when you 1028 00:37:53.474 --> 00:37:55.795 - start to get this flexibility of having, like, 1029 00:37:55.795 --> 00:37:58.934 - multiple ingest points, multiple output points, 1030 00:37:59.554 --> 00:38:01.394 - and kind of the capabilities that come with 1031 00:38:01.394 --> 00:38:02.694 - the plugins in Obsidian, 1032 00:38:03.154 --> 00:38:04.214 - all for free, 1033 00:38:04.769 --> 00:38:07.890 - it kinda just works. Right? It's a very 1034 00:38:08.130 --> 00:38:10.230 - it's it's a very cool system. 1035 00:38:10.610 --> 00:38:12.050 - And once you start to go down this 1036 00:38:12.050 --> 00:38:14.530 - path, like, for me, I, like, I'm one 1037 00:38:14.530 --> 00:38:16.130 - of those people, like, I hate to admit 1038 00:38:16.130 --> 00:38:18.255 - it, but I can live in email. Right? 1039 00:38:18.255 --> 00:38:20.655 - It's pretty easy to get 50 emails overnight, 1040 00:38:20.655 --> 00:38:22.094 - then you just get stuck in it. You're 1041 00:38:22.094 --> 00:38:24.574 - like, I don't really live in email as 1042 00:38:24.574 --> 00:38:25.315 - much anymore. 1043 00:38:25.775 --> 00:38:28.014 - Email has just turned into I've got this 1044 00:38:28.014 --> 00:38:30.039 - other thing over here that's taking a look 1045 00:38:30.039 --> 00:38:31.480 - at it. I had to refine it. I 1046 00:38:31.480 --> 00:38:33.719 - had to take some time put time into 1047 00:38:33.719 --> 00:38:35.179 - automating that process and 1048 00:38:35.480 --> 00:38:38.039 - automating myself out of that job of living 1049 00:38:38.039 --> 00:38:38.779 - in email, 1050 00:38:39.239 --> 00:38:40.139 - but it 1051 00:38:40.519 --> 00:38:42.394 - it helps on the other side. And I 1052 00:38:42.394 --> 00:38:43.994 - think, like like, the thing that really, like, 1053 00:38:43.994 --> 00:38:45.295 - kicked my butt was 1054 00:38:45.755 --> 00:38:48.335 - this team teammate of mine who, 1055 00:38:49.594 --> 00:38:51.275 - he lives in the chaos that I live 1056 00:38:51.275 --> 00:38:51.775 - in 1057 00:38:52.074 --> 00:38:54.414 - and the rest of our team lives in. 1058 00:38:54.714 --> 00:38:56.335 - And he has this 1059 00:38:56.635 --> 00:38:57.614 - super awesome 1060 00:38:58.130 --> 00:38:59.809 - I hesitate to call it a demo because 1061 00:38:59.809 --> 00:39:01.730 - he showed his real workflow for how he 1062 00:39:01.730 --> 00:39:03.170 - manages all this stuff. He put it all 1063 00:39:03.170 --> 00:39:04.690 - in a Git repo for us so we 1064 00:39:04.690 --> 00:39:05.910 - could just pick up skills 1065 00:39:06.690 --> 00:39:09.090 - and run with them. And he's one of 1066 00:39:09.090 --> 00:39:12.070 - the first people that I'd seen who successfully, 1067 00:39:12.530 --> 00:39:12.945 - like, 1068 00:39:13.344 --> 00:39:13.844 - navigated 1069 00:39:14.144 --> 00:39:15.204 - inbox zero 1070 00:39:15.505 --> 00:39:16.164 - at Microsoft 1071 00:39:16.945 --> 00:39:19.105 - without feeling like he was missing out on 1072 00:39:19.105 --> 00:39:21.425 - something or feeling like you're not just doing, 1073 00:39:21.425 --> 00:39:22.164 - like, the 1074 00:39:22.625 --> 00:39:25.344 - control a, delete, or control a, archive, and 1075 00:39:25.344 --> 00:39:27.204 - I'll hope they email me again tomorrow 1076 00:39:27.739 --> 00:39:28.639 - kind of thing. 1077 00:39:29.019 --> 00:39:30.460 - It it was also very interesting to me 1078 00:39:30.460 --> 00:39:31.599 - to see the way that 1079 00:39:31.980 --> 00:39:35.179 - this individual managed tasks in Obsidian, like, how 1080 00:39:35.179 --> 00:39:37.260 - they weren't trying, like, a forcing function of, 1081 00:39:37.260 --> 00:39:38.859 - like I've seen a lot of people use, 1082 00:39:38.859 --> 00:39:41.515 - like, Copilot cowork and and integrate it with 1083 00:39:41.515 --> 00:39:43.515 - Planner and things like that. They put together 1084 00:39:43.515 --> 00:39:45.994 - their Kanban boards, and I I feel like 1085 00:39:45.994 --> 00:39:47.755 - the process runs away from you. It gets 1086 00:39:47.755 --> 00:39:49.755 - a little too fancy at some point. I 1087 00:39:49.755 --> 00:39:50.414 - I think 1088 00:39:50.795 --> 00:39:53.114 - we're much better served when stuff becomes nice, 1089 00:39:53.114 --> 00:39:55.199 - simple. Like, here's a to do list. I've 1090 00:39:55.199 --> 00:39:57.280 - got a checkbox. I check that thing off, 1091 00:39:57.280 --> 00:39:59.139 - and it gets a strike through it. 1092 00:39:59.519 --> 00:40:01.519 - And you get to feel good about that. 1093 00:40:01.519 --> 00:40:03.679 - Like like, there's a little there's a little 1094 00:40:03.679 --> 00:40:04.659 - rush of endorphins, 1095 00:40:04.960 --> 00:40:07.380 - right, when you when you check that checkbox 1096 00:40:07.519 --> 00:40:08.500 - and have that 1097 00:40:08.835 --> 00:40:11.394 - sense of accomplishment that's out there. And because 1098 00:40:11.394 --> 00:40:13.474 - this stuff is all text, you can do 1099 00:40:13.474 --> 00:40:16.514 - things because, again, LLM Wiki style Obsidian, you 1100 00:40:16.514 --> 00:40:18.135 - don't even have to check the checkbox. 1101 00:40:19.315 --> 00:40:21.554 - I would imagine I haven't done this, but 1102 00:40:21.554 --> 00:40:23.670 - I think this would be totally doable. Like, 1103 00:40:23.670 --> 00:40:25.670 - I could go into GitHub Copilot CLI, and 1104 00:40:25.670 --> 00:40:26.489 - I could say, 1105 00:40:27.030 --> 00:40:28.569 - my my task for today 1106 00:40:29.510 --> 00:40:31.510 - to email Jack is done. Can you just 1107 00:40:31.510 --> 00:40:32.710 - check that off for me? And I would 1108 00:40:32.710 --> 00:40:34.230 - go check it off for me. Right? I 1109 00:40:34.230 --> 00:40:34.969 - don't have to 1110 00:40:35.269 --> 00:40:37.925 - worry about actually even opening a vault or 1111 00:40:37.925 --> 00:40:39.545 - looking at anything and 1112 00:40:39.925 --> 00:40:40.984 - running that way. 1113 00:40:41.605 --> 00:40:43.925 - Like, the the elephant in the room, which 1114 00:40:43.925 --> 00:40:45.925 - I don't think anybody could address at this 1115 00:40:45.925 --> 00:40:46.425 - point, 1116 00:40:46.724 --> 00:40:49.625 - and, I mean, it it is there, is 1117 00:40:50.239 --> 00:40:52.960 - your like, this stuff's all plain text. Right? 1118 00:40:52.960 --> 00:40:55.199 - You are extracting it out and and kinda 1119 00:40:55.199 --> 00:40:56.339 - putting it down to your, 1120 00:40:56.880 --> 00:40:59.679 - your OneDrive and things like that. So stuff 1121 00:40:59.679 --> 00:41:00.179 - like 1122 00:41:00.639 --> 00:41:01.859 - IRM and MIP 1123 00:41:02.184 --> 00:41:04.204 - really don't apply to markdown files. 1124 00:41:04.505 --> 00:41:06.844 - So it certainly, like, don't break, 1125 00:41:07.304 --> 00:41:08.684 - like, organizational constraints 1126 00:41:09.065 --> 00:41:11.385 - or things like that. Pay attention to sensitivity 1127 00:41:11.385 --> 00:41:13.704 - labels and all that stuff. Those types of 1128 00:41:13.704 --> 00:41:16.250 - things? Well, Cowork doesn't pay attention to sensitivity 1129 00:41:16.250 --> 00:41:18.090 - labels, so why should I? No. It does. 1130 00:41:18.090 --> 00:41:20.409 - It can't read any MIP file. It's kinda 1131 00:41:20.409 --> 00:41:23.130 - useless. So Yeah. If you're actually encrypting it. 1132 00:41:23.130 --> 00:41:24.570 - Yeah. No. I'm gonna have to play with 1133 00:41:24.570 --> 00:41:26.010 - this too because I'm doing all my meeting 1134 00:41:26.090 --> 00:41:27.675 - I'm doing this with meeting notes, and I 1135 00:41:27.675 --> 00:41:29.355 - created a Wiki for meeting notes. So, like, 1136 00:41:29.355 --> 00:41:31.195 - meeting notes out of people, so I have, 1137 00:41:31.195 --> 00:41:33.994 - like, people and topic and all of that 1138 00:41:33.994 --> 00:41:36.074 - meeting notes. It would be really interesting to 1139 00:41:36.074 --> 00:41:37.914 - take this into Cowork and actually, like, now 1140 00:41:37.914 --> 00:41:41.055 - I can correlate meeting notes with emails, with 1141 00:41:41.195 --> 00:41:43.215 - all of that. How about just meeting notes, 1142 00:41:43.409 --> 00:41:45.730 - but meeting notes with transcripts? So go create 1143 00:41:45.730 --> 00:41:48.230 - yourself a skill, load it into co work, 1144 00:41:48.289 --> 00:41:50.069 - have it extract your meetings transcripts 1145 00:41:50.769 --> 00:41:53.250 - from the prior day, ingest them in, and 1146 00:41:53.250 --> 00:41:54.769 - then go run this over them. Right? Like 1147 00:41:54.769 --> 00:41:56.449 - like, that's just a super Yeah. I see. 1148 00:41:56.449 --> 00:41:58.074 - I'm already doing that part of it. Now 1149 00:41:58.074 --> 00:41:59.535 - we just have to tie in the emails. 1150 00:41:59.755 --> 00:42:02.494 - So it is. This it's it is definitely 1151 00:42:02.795 --> 00:42:05.135 - interesting to start tying all this together. 1152 00:42:05.434 --> 00:42:07.195 - Again, those are the two I've done is 1153 00:42:07.195 --> 00:42:08.815 - emails. I did the podcast. 1154 00:42:09.114 --> 00:42:10.795 - I've started to do just references, but I'm 1155 00:42:10.795 --> 00:42:12.699 - gonna go play with blog posts and figure 1156 00:42:12.699 --> 00:42:14.140 - out how to incorporate some of that other 1157 00:42:14.140 --> 00:42:16.380 - stuff in with Cowork. But I just gotta 1158 00:42:16.380 --> 00:42:18.699 - chat that my other meetings started. World of 1159 00:42:18.699 --> 00:42:21.260 - possibilities here. Absolutely. So I'll put a bunch 1160 00:42:21.260 --> 00:42:23.280 - of links in the show notes to kinda 1161 00:42:23.660 --> 00:42:25.724 - the original gist and things that came out 1162 00:42:25.724 --> 00:42:27.804 - here. Yeah. There's some good YouTube videos out 1163 00:42:27.804 --> 00:42:29.324 - there we can post in the show notes 1164 00:42:29.324 --> 00:42:29.824 - too, 1165 00:42:30.284 --> 00:42:32.204 - walking through how different people have done this 1166 00:42:32.204 --> 00:42:33.724 - and showing how some of it's set up 1167 00:42:33.724 --> 00:42:35.484 - too. I haven't seen a lot of people 1168 00:42:35.484 --> 00:42:36.464 - who have done 1169 00:42:36.764 --> 00:42:39.030 - Copilot Cowork. There's a lot of Claude. There's 1170 00:42:39.030 --> 00:42:40.489 - a lot of good reference implementations. 1171 00:42:41.510 --> 00:42:44.150 - Yeah. Claude's out there. Super easy to, like, 1172 00:42:44.150 --> 00:42:47.269 - Google, Bing, DuckDuckGo, Kagi, whatever your search engine 1173 00:42:47.269 --> 00:42:47.769 - choices. 1174 00:42:48.309 --> 00:42:50.469 - I will put out some examples for those 1175 00:42:50.469 --> 00:42:52.090 - who are in the Microsoft ecosystem. 1176 00:42:52.390 --> 00:42:53.605 - So So there's a pretty good one out 1177 00:42:53.605 --> 00:42:54.885 - here that I'll put in. It's called the 1178 00:42:54.885 --> 00:42:58.805 - GitHub Copilot Wiki, an AI powered second brain 1179 00:42:58.805 --> 00:42:59.305 - template. 1180 00:42:59.605 --> 00:43:01.785 - So it that's it's kinda like a forkable 1181 00:43:01.845 --> 00:43:04.724 - template that you can start with. So it 1182 00:43:04.724 --> 00:43:06.599 - already has the wiki structure. 1183 00:43:07.139 --> 00:43:09.320 - It has a template dot m d. 1184 00:43:10.260 --> 00:43:12.579 - It has a lot of these constructs, right, 1185 00:43:12.579 --> 00:43:14.339 - that I talked about here, and it can 1186 00:43:14.339 --> 00:43:16.900 - just kinda, like, bootstrap you if you didn't 1187 00:43:16.900 --> 00:43:17.380 - want to 1188 00:43:18.579 --> 00:43:20.715 - if you didn't wanna start start for yourself 1189 00:43:24.235 --> 00:43:25.994 - links a template too. So we'll drop those 1190 00:43:25.994 --> 00:43:28.315 - in the show notes. Cool. Perfect. Well, thanks, 1191 00:43:28.315 --> 00:43:30.875 - Scott. Yeah. Enjoy your weekend, and I'm gonna 1192 00:43:30.875 --> 00:43:32.795 - go jump on my next meeting. Perfect. Me 1193 00:43:32.795 --> 00:43:33.295 - too. 1194 00:43:34.155 --> 00:43:36.235 - Life life is on. Alright. Thanks, Ben. Alright. 1195 00:43:36.235 --> 00:43:37.730 - We'll talk to you next time. Yep. Bye 1196 00:43:37.730 --> 00:43:38.469 - bye, Scott. 1197 00:43:40.449 --> 00:43:42.690 - If you enjoyed the podcast, go leave us 1198 00:43:42.690 --> 00:43:44.929 - a five star rating in iTunes. It helps 1199 00:43:44.929 --> 00:43:46.609 - to get the word out so more IT 1200 00:43:46.609 --> 00:43:48.769 - pros can learn about Office three sixty five 1201 00:43:48.769 --> 00:43:49.429 - and Azure. 1202 00:43:49.969 --> 00:43:51.650 - If you have any questions you want us 1203 00:43:51.650 --> 00:43:53.864 - to address on the show or feedback about 1204 00:43:53.864 --> 00:43:56.184 - the show, feel free to reach out via 1205 00:43:56.184 --> 00:43:58.364 - our website, Twitter, or Facebook. 1206 00:43:58.664 --> 00:44:00.505 - Thanks again for listening, and have a great 1207 00:44:00.505 --> 00:44:01.005 - day.

Digital Dispatch Podcast Podcast Artwork Image

Microsoft Cloud IT Pro Podcast

Ben Stegink, Scott Hoag

On the MS Cloud IT Pro Podcast, Scott and Ben discuss the Microsoft Cloud with a focus on IT Pros. They'll discuss the latest in Microsoft 365 and Office 365 News, Azure news and talk about their experiences with managing the Microsoft Cloud as well as interview industry experts on various cloud technology. They'll cover things such as SharePoint, Exchange, Microsoft Teams, PowerShell, Azure, Azure AD, Security, Networking, Storage, and the many other technologies and products that have made their way into the Microsoft 365 suite and Azure. To stay up-to-date on the latest in Microsoft Cloud news and gain some valuable knowledge as you deploy it within your own organization, make sure to tune in every week! Find out more at msclouditpropodcast.com.

Contact Show