You showed UP in the "What's In Your Toolbox?" Poll — 127 votes, 163 comments. Claude Code leads with 36 votes, Hermes Agent strong at 13, "Other" custom stacks at 17, plus Pi, OpenClaw, and more. Dozens of unique voices (Ari Evergreen, Mark Santelia, Mike Routen, Mira Bradshaw, Izumo Spedicato, Dustin Wyzard, Bas Rosario, Toby Iverson, Charlie Weeks, Aaron Klein, Nico Veenkamp, Johnny L, Adib Alami, Mitchell Johnson, M Cook, Andrew Carter, Holly Parsons, Robert Infinger, Greg Faysash, Giovanni Garcia, Enrique Araiza, Wojtek Gajewski, Brendan Tucek, Taofeek O. a. and many more). This community isn't just picking tools — you're living ICM. Comments are packed with folder-based context routing, memory layers (Hermes/Cogne), self-improving loops, 60/30/10 discipline, and stage-by-stage optimization. Exactly the interpreted context meta: persistent agents + rule-based workflows + smart AI core. Production-ready agent systems in action. And the winner is... @Izumo Spedicato 🎉 Congrats on your 1-month premium membership. Go build legendary stuff. Thanks again to all that participated. And a special thanks to Jake for this wonderful community.

I Don't talk to Sonnet 5. My model does (Opus). I sit with one Claude. I direct it, I review what it hands back, I take the call when something's ambiguous. That's the seat I'm in. What I don't see directly is what that Claude dispatches to when the work is execution, not judgement. Loop tasks, cron jobs, every UltraCode fan-out. That's a different seat, one level down, and until now it ran on whatever was cheap enough to risk unattended. Sonnet 5 just moved into that seat. Near-Opus reasoning, full context, Sonnet pricing. I didn't upgrade my model. My model's model did. Who's dispatching for you, and did you notice when they got better? //A<3

This has been one question i have always asked and kept trying to understand until recently. I've seen it asked and discussed multiple times here... So i decided to combine, study and comprehend the various perspective of those who have shared how they are using it @Curtis Hays and many others, to come up with a simple way for me to implement. Here is my personal understanding: Say we are four people in the marketing department, and i am the only one who has built an content pipeline using the ICM framework, now i want onboard the other 3 coworkers and you're one of them... lol 😀 We have one master system, the original pipeline i'm using is now hosted on GitHub (with the same agent.md and context.md, rules and stages). Step 1: Getting the System on Your Computer You copy/clone the entire workspace from the internet (GitHub) to your PC. This gives you the same folders I have: 01-ideas 02-drafts 03-formats etc Step 2: Creating Content Open your copy of the workspace. Talk to ai agent while in the folder normally. Example conversations: “Give me ideas for LinkedIn posts about productivity” “Turn idea number 4 into a full draft” “Format this draft for Instagram carousel and Substack” The agent uses the shared system I built, so all our content has the same style and quality. Step 3: Sharing Improvements If you create a better prompt or improve one of the stages: Tell the agent: “I improved the carousel format, make a Pull Request” I (or the content lead) will check it. Once approved, everyone gets the improvement automatically. Step 4: Where Files Live Your ideas and drafts: Stay on your computer (or save final versions to the department Google Drive, which we all have access to). The framework (how we create content): Lives in the shared system (Github). - What You Need to Do Install Git (one time, easy). Clone (copy) the workspace. Use AI agent within the folder workspace.