📝 SUMMARY This week's call centered on the evolution from single AI assistants to "chief of staff" multi-agent architectures, with multiple members converging on similar two-tier systems where a coordinator agent delegates to an implementer via shared repositories. Patrick Chouinard detailed his enterprise rollout of 2000+ Claude licenses and the governance patterns required, while others shared strategies for managing model verbosity, measuring real ROI versus vanity metrics, and overcoming organizational resistance to AI coding. Additional discussions covered database migrations for real-time apps, personal assistant tooling, and enterprise adoption tactics. 💡 KEY INSIGHTS The "assistant" model collapses at scale. Patrick described how coordinating many Claude assistants eventually consumes more time than it saves, leading his team to create a two-tier architecture: Claude Cowork acts as "chief of staff" coordinating with Claude Code as "implementer" through a shared local Git ledger, reducing humans to pure decision-makers. Two agents talking directly is the real unlock. Patrick and Paul Miller independently arrived at architectures where coordinator and executor agents communicate and write status to each other without human message relay, freeing the human to act only as a decision-maker. Surface decisions and wins, not just noise. Ty Wells noted that showing only problems creates a demoralizing interface. Effective chief-of-staff agents should highlight progress and successes alongside escalations, not just raw agent output. Set explicit time budgets. Paul Miller emphasized that agent tasks without deadlines can silently balloon from one hour to four, cascading delays. Decisive time constraints prevent runaway context windows. Opus 5 requires verbosity management. Multiple attendees flagged Opus 5 as unusually chatty. Mitigations include Matt Pocock's "wait, what?" skill to detect confusing output and Patrick's discovery that sarcastic, personality-driven prompts naturally produce shorter, clearer responses.

👋 Hey there! Ready to supercharge your dev skills with AI? You're in the right place. Watch the intro video below for a walkthrough of our community and a peek at our AI-enhanced future. 🛠 CLASSROOMS: - Full Stack Development with AI: Where code meets cognition. Sharpen your skills and build AI-- powered apps. - CrewAI: Your squad for all things AI. Share ideas, collaborate on projects, and celebrate successes together. - Code Bugs & Project Issues: Debug like a pro. Get help on tricky bugs and offer your wisdom to others. - Monetize Your AI Dev Skills: From AI code to income: Collaborate, innovate, and monetize your dev skills! - YouTube Tutorial Requests: Please let me know what you want to learn more about when it comes to Fullstack Developement and AI. 📜 RULES: - Promotions are a no-no. Let's keep the focus on learning and growing. - We appreciate quality contributions. Enhance your posts with visuals and use ChatGPT for refining your content. - No talking about politics or religion. Go to X if you want to talk about that. - See something off? Help us maintain the community spirit by reporting any issues to me. 🥇 FIRST STEP: Introduce yourself with a post about your AI journey and what you're working on in the General Discussion group. **Bonus points for sharing a screenshot of your current app!** 🎯 ACTIONS: Be proactive, engage in discussions, and collaborate on group projects. 👩‍💻👨‍💻 Let's code, innovate, and thrive together!

Some of you may find this interview from The Rest is Politics podcast where they discuss AI with Jack Clark. I feel it is really great. https://youtube.com/watch?v=CHcMkIq2yXM&is=D3uU6xZSe8F512WK

Evening all. I just got an email from Cursor Team telling me about the Cursor Router. It apparently 'intelligently' routes your requests to teh most efficent model From the email :- Routing requests With Cursor Router, your team can: - Call the right model for each task, every time. - Optimize routing with three modes: Intelligence, Balance, and Cost. - Cut spend without cutting quality. In early access, teams saved 30-50% using Cursor Router vs. routing all requests to Opus 4.8 Anyone used it or care to comment. Seems good in the blurb but, why would a company push savings of 30-50%. Granted I do like to keep my mola to myself for my own toys.

It definitly should not be a 'come to my channel' or 'Connect to me via this suspiccious url covered by tiny.url' A meaning ful introduction would be nice. quite a few people have done that. Perhaps a little about what you have tried, where you are on your AI journey. Something interesting about yourself. Definitly not 'Heres my product use it' etc.