Hey guys, the executive assistant I'm building for my daughter: her boss wants her to use Grok. I'm assuming all of the principles still apply in the build. Would you say that's accurate or what do I need to watch out for or do differently than the one I built in Claude Code?

I'd become very dependant and accustom to working with my ai operating system (built from Nate's framework) but I'm no longer in the professional role that I built that OS for. I'm curious what ya'lls thoughts are on replacing now for my personal assistant. Nate was previously teaching a method to build an Executive Assistant but then sorta graduated it to the full blown OS. Should I create a new OS now for my personal assistant since it seems like a more advanced EA. I know there are some business related specific components of the OS but wondering if anyone else has wrestled with this...

Well, I just got shoved into the deep end. “Restructuring” and eliminating departments… so I’m officially laid off and can’t imagine going through that job hunting process again. The ai operating system i’ve been building and used at my job for the past eight months or so has got to be a sellable product. Right?! (I mean the process of building it not my actual system.) I am I am going to build help my daughter build hers for her at her company to get more comfortable with the steps and then hoping to put a price tag on it and offer it to some of my business owner friends. Anyway, just kind of thinking out loud right now in hopes that maybe some of you have been in a similar place and feel like sharing … Well, I’ll keep you posted. Talk soon.

People always ask me which AI tools I actually use, so I went back through the 100+ AI tools I've tested for my business and kept only the ones I come back to every single week. These 7 are the best, and a couple of them sound pretty boring on paper. One runs about 90% of my daily workflow, one replaced tools I was paying for every month, and one keeps my automations running 24/7 even when my laptop is closed.

Hey everyone - Happy Sunday! - What you built - screenshot of your newsletter email or your Claude Code project setup: For my business use case, a LinkeIn post was more practical than a newsletter so that's what I built. Also, I've been operating within the AIOS executive assistant taught by Nate for the past 8 months or so, so I built this in that existing project instead of a new dedicated one. Here's the prompt I started with: "I want to build a LinkedIn post generator automation. you research a topic for [my business name], write the content, generate infographics, format it in HTML or whatever format is best, and send it to me via Gmail for me to preview. Each piece of this automation will require my approval before being handing off to the next. You should decide the best tool to use for each of these steps." The "you decide" part is my take on the recent recommendation to get out of the agents way and let it figure things out (ie, Andrej suggesting we delete all skills 🫤...) - One thing you learned This project reinforced something I'm learning... that the early months of investing time in "OSkar" (My AIOS) have been worth it. 2 of the topics he chose for the post were pulled from issues we had that were only recorded deep within our companies project management tool. - One thing you'd improve - what would you change about your newsletter on the next iteration? Next iteration, I will point OSkar to our companies marketing campaign calendar and have him leverage the strategy. This example I'm sharing was sort of intentionally not practical (there's kinda no story here) but I just wanted to test the mechanics. Here she is: POST: 4 vans. That's how many Sprinters one of last fall's frame recalls covered. Another covered about 366. Here's the 1-minute check that tells you if yours is one of them. Last fall, Mercedes-Benz recalled 2 groups of Sprinters over the frame. One covered 4 vans built over 2 days in September 2023. Frame reinforcements may be missing, which can affect how the body holds up in a frontal crash.