Does anybody know just how secure the above setup is (on my Daily Mac machine)? Specifically, if I give it access to ONE folder in my Dropbox. • I use Dropbox on my Daily machine... that's what's making me a bit nervous. • My sensitive files are encrypted, but I still wonder what kind of "escaping" Claude Desktop/Cowork could do when I've unencrypted and mounted sensitive volumes also "Cowork runs inside a secure Virtual Machine (VM) on your computer (using the Apple Virtualization Framework on Mac). This means it can safely "mount" your local files to read, edit, and reorganize them without risking your entire machine." Source: https://www.lumetric.ai/resources/claude-web-vs-desktop-vs-code-vs-cowork Thank youuuu!!!

This podcast says yes. I can say I disagree…

I just watched the Jake Van Cleef breakdown, and the biggest thing that stood out to me was not getting overwhelmed and starting small. It clicked because I tend to complicate things and get overwhelmed. My main takeaway was start small. The experiment at the end helped me understand how to think about the system. Going forward, I'm going to start small and utilize the system better.

Hermes can run a cron job without ICM. It can wake up on schedule, read a source, write a report, send a message, and save the run output. It also has its own durable storage: - session history, - persistent memory, - cron definitions and run logs, - skills, - and whatever files it creates in the workspace. That is useful. But it can still leave you with a familiar mess: > a chat somewhere > a cron log somewhere else > a report with no obvious home > and an agent that needs you to explain the project again next week That is where ICM comes in. I use ICM around my Build Market Close signal cron so the **job is not the whole system**. The cron is just the heartbeat. The structure holds the memory: ```text pinned-post-curriculum-signal/ ├── CONTEXT.md ├── signal-register.md ├── reply-drafts.md ├── curriculum-outline.md └── runs/ └── YYYY-MM-DD/ └── signal-review.md ``` Here is what each part does: - **`CONTEXT.md`** tells a fresh agent what source it may read, what counts as meaningful signal, what it may write, and where it must stop for me. - **`runs/YYYY-MM-DD/`** keeps a dated receipt of every review: what the job saw, what changed, and what it deliberately did not do. - **`signal-register.md`** is the one place for real questions, objections, implementation friction, and learner needs. - **`reply-drafts.md`** holds proposed answers for review. Nothing gets posted automatically. - **`curriculum-outline.md`** turns repeated questions into a better lesson sequence instead of letting them disappear into comments. So the cron does the recurring check. But ICM makes the check **usable**. A fresh agent can open the folder and answer: 1. What is this job for? 2. What source is it allowed to use?

We're dropping the weekly onboarding call. Not because onboarding stopped mattering. Because a weekly 30-minute loop started mattering less than we pretended it did. If you just joined, you don't need another recurring meeting on the calendar. You need one clean pass through the room: who we are, where Discord lives, how people actually lean on each other here, and how the competitions work. Then you need to go do the work. So, the call is moving to once a month (First Wednesday of the Month). Same length. Same point. No extra theater. Next one is: Wednesday, October 7th, 2:00–2:30pm EDT https://www.skool.com/live/xTMdy25NCh8 Show up. Introduce yourself. Meet the mods. Meet the other people who just walked in. Then we walk through: - - Getting into Discord - - Finding your way around - - Getting the most out of other members - - How to win the competitions - - Quick questions at the end Thirty minutes. Straight to the point. After that, we'll run it monthly. If you miss one, the next one is a month away, not seven days. That is the point. Onboarding should be a door, not a habit. And as always, thank you for being part of the Clief Notes Community! We appreciate every single one of you.