How are you all handling agent(folder) memory and daily continuity in your ICM setups? I know 'the system is the memory,' but if I'm working on a single workflow over multiple days, where are you storing the agent's learned context so it doesn't lose the thread—without accidentally bloating the active load path? Do you have in the instructions to update the context file when done running your process?

Glad you made it in. Before you go anywhere else, work through the steps below. They will get you set up and ready to start. ✅ Introduce yourself in the comments. Tell us what you do and why you are here. ✅ Watch the Getting Started overview 📚Navigating The Course - Getting Started · Clief Notes ✅ Start with the Foundation course 0.1: Where All Of This Leads - The Foundation · Clief Notes ✅ Fill out your profile so people know who you are ✅ Join the next competition ⭐ Competitions Mega Thread - Getting Started · Clief Notes ⭐ On Competitions (and why I love them) We host a competition every two weeks. These are some of the most powerful places to learn and build here. Also Cash prices (often over $200) for the winners. Learning how to do something is one part of it. The real learning starts when you put it to work. That is what the competitions and the build sessions are for. On top of this they act as a portfolio a place to not just show us but show others (clients, bosses, your best friend) what you have been building and that you really CAN build. In order to win a competition you must be a paying member (It takes me hours to review submissions sometimes days. But if you win ONCE you can pay for a whole year of membership so I think that's only fair!) Watch the videos, then go make something.

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 📋 THE CHALLENGE You are the client this week. No fictional Marcus. No fictional Sarah. No fictional Devon. Pick a real problem in your own life or work. Build the folder-based specialist you wish you had. This is the capstone of Month 2. The challenge flips. Instead of building for someone else, you write your own brief and solve it for yourself. ---- 🎯 THE TWIST The hard part isn't building. The hard part is scoping. Picking the right problem is harder than solving the wrong one. Most people pick problems that are too small or too vague. The skill this week is treating yourself like a real client. Be specific about what's broken. Be specific about what you need. Don't pick "I want to be more productive." Pick "I waste two hours every Sunday night writing the same kind of LinkedIn carousel posts and I need a folder that handles 80% of the draft work so I can focus on the hook and the visuals." That's a real brief. Specific problem. Specific scope. Specific desired output. ---- 🗂️ TWO DELIVERABLES THIS WEEK This is the only week with two pieces: 1️⃣ Your own client brief. 250 words or less. Describe the problem you're solving for yourself. Treat yourself like a real client. What's broken? What have you already tried? What do you need? 2️⃣ The folder system that solves it. Same structure as every week: - 📄 identity.md - 📐 rules.md - 💬 examples.md - 📚 reference/ - 📖 README.md Your brief lives at the top of the repo as brief.md so judges can read it before they look at the folder. ---- 🔥 THE ANGLE THIS WEEK Anyone can follow a brief. Writing your own, then solving it, then shipping it as a usable folder is a portfolio piece that demonstrates judgment, not just execution. This is the skill that separates "AI hobbyist" from "AI builder." Anyone can prompt their way through a problem someone else handed them. Scoping a problem, designing the solution, and shipping it as a system is what real work looks like. 💪

(and a small change to how we run these) Hello everyone!! 👋 First, the honest bit. This one is landing later than Monday, and on purpose. Two things got us here. One, a lot more of you are submitting now. If I am going to really sit with every entry and give it a proper look, a weekend is not enough. This round I went through all of them, watched the videos, opened the repos, the full pass. That takes time and I would rather do it right than rush it. Two, I could feel a few of you running hot. Weekly is a sprint, and burnout was starting to creep in for some. So we are moving to bi-weekly. More room to build, more room to breathe, and the time for me to actually review the work the way it deserves. 🎥 Quick word on the videos. They were a step up this round. Some of the animated walkthroughs and live demos were a genuine pleasure to watch, and yes, I weigh them. A clean demo that shows the thing actually working makes a real difference. However I don't want that to ALWAYS be a requirement. Also you will notice the Heavy hitters that you usually see up here are not currently, some posted late and I decided to let the new entries and first timers also have a chance as well! But certainly, check the original post as every submission has something for you to learn from : 💰 Competition 7 ➖➖➖ 🛠️ A FEW THAT STOOD OUT (in no order, and if you didn't make it, it doesn't mean yours wasn't great) The Pipeline Operator — @Jayden Forshee Runs a whole sales pipeline. Paste a lead and it grades it, writes the outreach, and moves the card itself. The live board where you watch cards move on their own, sat right next to a normal chatbot, was one of the clearest ways anyone has shown what an operator actually is. https://github.com/griffainai/studio-pipeline-operator Board: https://pipeline-operator.vercel.app/board

Hey guys, I'm trying to figure out if Obsidian is worth adding to my stack. Been seeing it everywhere for a while now, everyone's using it as memory for Claude, which makes sense, it's just markdown folders. Thing is, I feel like I've already got my own version: one HQ folder of markdown files Claude reads at the start of every session, memory file, context file per project. Curious what you guys are doing. Anyone running Obsidian over an already decent folder setup? Any value add I'm missing? Cheers