For a month my job was carrying text between chats: copy the plan out of one, paste it into the next, then check whether the second one actually did it. The template I ended up with splits the work this way. - One session at the root plans and dispatches. It's the only one I talk to about priorities. - Each worker (content, design, an assistant) lives in its own folder with its own CLAUDE.md, CONTEXT.md and STATUS.md. - Workers never read each other's files. Every handoff is a brief, written so a cold session can pick it up with no chat history, and every brief lands in one briefs folder. - STATUS.md is the first thing a worker reads at the start of a session and the last thing it writes at the end. That's how I know a dispatch landed without asking. It ships with four hooks: one asks before rm -rf or a force-push, one snapshots high-risk files at the start of the day, one bumps a "Last updated" date when a tracker changes, and one asks before editing a file that's been handed off. It also has a weekly and monthly clean-up routine, so the folders don't silt up. It carries the structure only, none of my brand. You run a builder routine that fills in your voice and visual rules, then dispatch your first brief. The layers follow Jake Van Clief's ICM: what loads every session, what routes, what gets read on demand. Try it yourself: count how many times today you pasted one chat's output into another. Each one is a handoff that could be a file. Question for the comments: what's the handoff you still carry by hand most often? Free, MIT, nothing to sign up for: https://github.com/NFTYoginis/agency-of-one

My sister Hannah and I just finished something we’d never done before: the AI visuals for a live concert, Hello America, on the giant LED wall at the Colosseum at Caesars Palace in Las Vegas. Thirty songs in ten days. A big part of how two beginners pulled that off came from right here. ICM is how I ran it: one folder, one set of notes and one chat per song, more than thirty chats running at once, each one picking up where the last one left off. Thank you, Jake, Matthew and the whole Eduba team for building this and sharing it so openly. And @Matthew Creamer , a special thank you for coming out to the show in person. Showing up at the gala and the show to support us meant more than I can say. Having someone from this community in the room made it real. We captured the whole journey, the good and the messy parts: the tools I built, what broke, about 55,000 credits, and how ICM held it all together. ▶ Watch it here: https://www.youtube.com/watch?v=-HiJLMo3HfQ If it’s useful to you, a like and a subscribe would mean a lot. It helps me keep making these breakdowns for you.

a16z speedrun is one of the biggest accelerators in the world. We submitted our application a bit back on the recommendation of one of our friends. Our EdubaWare software has been in closed testing for a bit (get ready, next week thousands of you will get access to it and see our changes) We received and Email yesterday saying they want to hear more from us and to send them a video in under three minutes that explains: - Your backgrounds and greatest accomplishments, professional or personal - What makes you exceptional, and why you're the team to win this market - What you're building and what problem it solves - Why this is a big, underserved opportunity - What progress you've made so far  Now fitting all that into one video is challenging, but we did our best. I hope this gives you a view into the other side of my life which is my company Eduba!

I kept reanswering the same question at midnight: which model should this conversation run on? So I built the thing that answers it for me. https://github.com/dvogeldev/model-picker A skill for any agent that reads skills. Ask it "which model for X?" and it pulls the live Nous Portal and OpenRouter catalogs, ranks every model on three axes, and gives you one pick plus one cheaper alternate, with current prices and promotions. A promoted flagship can beat an unpromoted one at equal fit. Free tiers count as real picks. Every model gets classified: capability tier (frontier, flagship, value, small), deployment (API, or open weights you can self-host), and use case (long context, hard reasoning, agentic, coding). In pi you get /set-model coding. One command. The standing coding model for the session, thinking level included. A daily timer re-ingests both catalogs at 6:30 AM, so the standing map never goes stale. You stop defaulting to whatever you used last week and start choosing on purpose. Install is two lines. MIT. Your API keys stay in your own password manager. No key lands in a config file. It works in pi, opencode, hermes, and grok. Same skill in every harness. The standing map is a JSON file in your home directory: edit it, override it. Your call which model does which work. Try it, then ask your agent "which model should handle this?" Tell me below what it picked and whether you agreed. That's the part I read the comments for. ========================================================================= Why Nous Portal as the provider Fair question, since the skill also reads OpenRouter. portal.nousresearch.com is Nous Research, the same lab behind Hermes Agent. Three reasons it's my default surface. 1. The catalog is OpenRouter underneath. Same schema, same model IDs, same naming. That's why one picker script parses both catalogs with one parser. 2. It's built for the Hermes environment. Hermes is Nous's own model line, and the same lab runs the inference. One account, one key, one bill. hermes setup --portal and your agent is on it.

Found this cool YouTube shorts that seems to Make any website into APi. Let me know your thoughts. https://youtube.com/shorts/RYqPb9e0RXg?is=m1JTei4kJ6ZjF9b5