Curious how you all gather all the sources of information coming out on new agentic frameworks, concepts, AI news, youtube and podcast videos, blog posts etc? Are you building a scraper that ingests all this into your own knowledge wiki? Are you using the ICM approach to synthesize the raw sources?

best skills for youtube transcript scraping? go!

Working with AI is like orchestrating your task with a group of Savants. Clief notes enables you to break the cycle by providing you with a repeatable, evergreen methodology to take control of your orchestra. When trying to wrap my head around Jake's concepts it's helpful for me to focus on the future. And what is that future? That future is being able to focus my energies on creating new synergies with others by handing off the daily monotonous tasks that we all have been accustomed to. It's a future where the Savants handle the repetitive — the endless data crunching, the routine research, the formatting, the follow-ups, the thousand small decisions that used to quietly eat away at our days. They never tire, they never lose the tempo, and they execute flawlessly every single time you hand them the score. You meanwhile, step back into the role of the conductor. No longer buried in the sheet music, frantically trying to play every instrument yourself. Instead, you direct with intention — pointing toward the rising crescendo of a fresh idea, the elegant bridge between teams, or that bold improvisation that only a human with vision and heart can truly bring. Clief Notes becomes your baton. Not merely a tool, but a disciplined practice that turns these brilliant yet literal-minded Savants into a reliable, harmonious orchestra that amplifies you rather than overwhelms you. The real liberation isn't that the tasks vanish entirely. It's that they finally stop owning you. You reclaim your attention, your creativity, and your capacity to dream bigger and connect more deeply with others. Work stops feeling like an endless solo performance under pressure and starts feeling like leading a masterful ensemble toward something far greater than any one player could achieve alone. That's the quiet revolution Jake is pointing toward: not replacing humans, but finally giving us the space to be fully, powerfully human again. Side note: Yesterday during the high tea with Jake he made a comment "In a world full of answers it's the questions that become valuable". Which got me thinking so what the heck these are my ramblings. What are your thoughts?

can we turn claude code into an agent similar to Hermes? has anyone tried? similar memory management? cron scheduling, and persistent long running agents?

Last night I briefed two things. A plugin for a professional video editor. A Mac app for a dashboard I'd been sketching for weeks. Both real. Both specced. Neither had a single line of code written. I wrote the briefs. I kicked off the dispatch layer. I went to sleep. This morning there were two working products. The math on it: - 5 Opus sessions acting as executor advisors - 5 Sonnet sessions doing the mechanical build work - 0 extra spend on top of my Anthropic subscription - 0 new chat windows opened by me The orchestrator session I use as my advisor seat handed each spec to its own background worker. Each worker got its own branch, its own clean context, its own budget line. The Opus workers held the judgment. The Sonnet workers did the keystrokes. They handed off to each other. I slept. The lever people keep missing Most people think "power" in AI means a bigger model or a longer context window. The real lever is distribution. One tight brief can be executed by ten workers in parallel. Ten workers, each with a clean low-token budget, outperform one conversation carrying a bloated context every time. It is not close. The brief is the compression. The brief is the intelligence. Why it costs nothing extra The workers ran on Claude. Claude is covered by my subscription plan. Opus and Sonnet are both on the same plan. No metered API spend. No per-call billing. No "agentic loop surcharge". Ten workers in parallel cost exactly the same amount as sitting in one chat window and typing all day. Same bill. Ten times the output. The system around the AI is what did the work. The principle Stop prompting. Start briefing. A brief is a contract. It has acceptance criteria, files in scope, the one condition that makes the worker stop and surface to you, and the exact thing you want to be sitting on top of in the morning. Every worker starts cold. Every worker reads that same doc. The doc is the system. Prompts fight your context window. Briefs replace it.