Hey guys, I saw Nate’s Skool CLI on the printing press video a few days ago, and was interested in building something similar to help me maximize my learning from this community. Has anyone done it yet? Has any tips on its architecture?

Has anyone tried both the Codex and Claude Code $20 plans? Is there a clear usage difference between them? I don’t want to upgrade my plan just yet, but I’m looking to get the most bang for my buck out there. I’m currently on CC Pro, but I’ve been considering switching to the Codex Plus plan after hearing that it provides more overall usage? Is that true? And is the extra usage worth the switch?

Has anyone tried both the Codex and Claude Code $20 plans? Is there a clear usage difference between them? I don’t want to upgrade my plan just yet, but I’m looking to get the most bang for my buck out there. I’m currently on CC Pro, but I’ve been considering switching to the Codex Plus plan after hearing that it provides more overall usage? Is that true? And is the extra usage worth the switch?

Hey everyone! So I am almost done with the video tutorial for the AI OS and ngl it answered so many questions in my head! I have already onboarded so from now on I am gonna be focusing on improving it's capabilities. As I am not a business owner (yet!) I have almost zero context, no clients, no SOPs, absolutely nothing but I decided to set it up anyway and use it like my right hand for building future business operations. I know where I need to start - automate my content creation to start filling up my socials for the future client outreach, but I was curious what's next? I'd be happy to hear about skills or workflows you guys did inside your own AI-OS! Gotta get some inspiration here! Thanks!

Every single person following AI right now is overwhelmed. Including me. I make videos about this stuff for a living and I still feel the pressure. New model drops. New framework. New feature update. It feels like every single day. But after hearing a ton of you guys bring up "AI overwhelm" week after week, I realized this: → There's a HUGE difference between knowing the "what" and knowing the "how." Staying aware does not mean testing everything. Most new tools and features only need the "what." You see the title. You understand what it does. You move on. The "how" is reserved for the stuff that solves a problem you actually have right now. So when something new drops, I ask myself one question: Does this solve a specific pain point I'm currently dealing with? If yes, I test it in a real scenario. I test it against something that actually matters to me. If no, I save the link. I mentally file it away. And I keep walking. Because here's the thing. Your north star is probably very different from mine. Part of my job is to experiment, form opinions, and share what I think is useful. So naturally I test a lot of stuff. But if your north star is building a business or getting better at your craft, then every shiny new tool might just be a distraction. The number one mistake I see people make is they try to learn everything. They watch every video. They test every tool. They jump to the next thing before the last thing even had a chance to work. And if I've contributed to your overwhelm with my daily uploads, I apologize. hehe. But a lot of people think that this ties directly into how you measure your day. Productivity is not how many hours you worked. It's how many meaningful outputs you created that actually moved the needle towards your north star. Someone can work 12 hours one day and feel insanely productive, but they were just watching tutorials and playing around with new tools. Meanwhile someone else sits down for 5 hours, ships the one thing that actually matters, and makes more progress.