User
Write something
Pinned
START HERE
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.
START HERE
Pinned
40,000 People....I have only this to say
We just broke 40k Members, in less then 4 months... To say I am honored and blown away is an understatement. I feel like yesterday @Matthew Creamer quit his job to sleep on my floor and bust out 15 hour days to build out content, structure and anything else I thought you all would need to make this community worth it. But at the end of the day there is only one thing for me to say. THANKYOU None of this, and I mean NONE of this would be remotely worth it if it wasn't for you all. To list and tag everyone that have contributed so much valuable not just to this community but to me would be nearly impossible. Thank you to every single one of you. Thank you for commenting and helping out on posts Thank you for sharing the wins you have gotten both at home and professionally. Thank you for believing in me and what I am building septically those of you who have been around since the beginning (you know who you are). I cannot tell you how happy my heart is to get in front of you all and teach, talk, ask questions and even learn a lot myself. It is a dream come true to become someone that people can learn from; to share my thoughts and have those very thoughts change the way people live their lives and do their work. It's only the beginning too, I can't wait to see what the rest of the year has in store, and I promise to keep building, working and recording for you all. From the very very very bottom of my heart.....Thankyou! Thankyou to every single one of you reading this and for being part of such an amazing community.
40,000 People....I have only this to say
Pinned
🎆 THE LAST SALE EVER — HELP US GET TO VEGAS 🎆
🎯 WE READ ALL OF YOUR RESPONSES. HERE'S WHAT'S NEXT (AND A BIG ASK) A couple weeks ago we asked you what you wanted Clief Notes to become. You showed up. You wrote real, thoughtful answers, some of you wrote essays. We read every single one. Twice. So before anything else: thank you. This post is us answering you. 💬 YOU TOLD US. HERE'S WHAT WE'RE BUILDING. You said you want a clearer path from learning ICM to actually getting paid for it. → It's coming. A real learning-to-earning track, plus a talent platform we're building to connect you with people who want to hire what you can do. Heads up: the talent platform will be Premium and VIP only, one more reason to lock in below. You said competitions without feedback don't help you grow. → Fixed. Going forward, every single entrant gets tailored feedback on their build, not just the winner. We're moving to two competitions a month so we can do it right. And both monthly winners get a 30-minute call with me. You said the best builds get buried in the feed. → We're building a tagged library so you can actually find "ICM setups for solo operators" or "small team, non-coder" instead of scrolling for an hour. You said you couldn't map all the pieces, Skool, Discord, the Lyceum, ICM, what each tier unlocks. → A single orientation page is on the way. One place that breaks all of it down so nobody's lost. You said you want to connect with each other. → We hear you. Meetups, pairing, and a recorded "After Tea" hangout are on the table. South Florida alone has over 1,000 of you. Let's use that. You said we've felt spread thin. → The most honest one. You're right. We're bringing on real help to run the day-to-day so the community gets consistency, and so Matt and I can keep building the things above instead of dropping balls. You called it, and we're fixing it. 📍 QUICK NOTE ON ICM: a few of you asked for "ICM with Copilot" or "ICM with n8n, Sheets, GoHighLevel." Good news, ICM already works with any model and feeds straight into the tools you're using. It's the structure underneath all of them, not a separate thing you have to relearn per tool. If that's not landing for you, that's on us to make clearer, and we will.
Congrats — lurker to participant.
That's the leap most people never take. Roughly 90% of our members are still on the other side: scrolling, saving, getting value, never saying a word. Not a knock. Just the math. Lurking isn't failure. It's the default. But you showed up. And that shift compounds fast. The classroom teaches you the tools. The community teaches you how to think with them. When you participate, you get compression — months of grinding folded into a thread someone else already broke so you don't have to. Less friction. Faster outcomes. Personal growth and business growth in the same lane. You don't need a hot take. You need a real question. Give before you extract. Your lurker era wasn't wasted — you were loading context. Welcome to Level 2. A few of you just made the jump, and I want to call it out: • @Vamsi Acharya • @Stacey Lubowa • @Martin Brion • @Mark Benjamin • @Keith Langskov • @Patti Wilcox • @Novus Vella • @Tony Rhodes @Cain Gray If you're still lurking — go check out what they're posting. Real builds. Real questions. No fluff. That's the energy we want in here. And if I missed you — my bad. Drop your name below. We'll get you in the next round. The reward for showing up isn't points. It's speed. You stop duct-taping alone. You stop renting confusion. Your stack starts to click because other people's scars are now in your context. What finally made you break the ice? ───
Congrats — lurker to participant.
🚨 UPDATE: FIXED IT! 🤖 Local LLM + VS Code = Not Autonomous (Yet?) | OpenCode vs. Claude Code
It turns out this wasn't an architectural limitation of VS Code extensions—it was a combination of using a model that was too small for agentic tasks, and a misconfigured context window that was suffocating my hardware. Here is exactly what I was doing wrong and how to fix it to get that true "Claude Code" autonomous experience locally: 1. The Model was Too Small for Tool-Calling I was using qwen2.5-coder:latest (which defaults to the 7B version). The 7B model is great for fast autocomplete, but it is fundamentally too small to reliably format the hidden JSON tool calls required to autonomously read and write files. The Fix: I switched to qwen3-coder:30b (an agent-tier model). The qwen2.5-coder:32b-instruct-q4_K_M would have also worked perfectly. Once you cross that 30B parameter threshold, the model is smart enough to actually use the VS Code extension's file-system tools on its own. 2. The Context Window was Crashing My RAM Even with the 30B model, it was initially taking over 3 minutes to read a file. Why? Because the VS Code extension (and Ollama GUI) was defaulting to an insane 256k-token context window. - Asking a 30B model to hold 256k tokens of memory caused its size to balloon to 45GB. - It overflowed my 32GB of RAM, spilled entirely onto my SSD pagefile, and bogged down my CPU trying to swap data. The Fix: I clamped the maximum context window down to 32k tokens. The model now runs flawlessly at 20GB, fits entirely inside my physical RAM and GPU VRAM, and operates at blazing-fast speeds. Conclusion: Yes, you absolutely can get that autonomous, repo-wide Claude Code experience locally in VS Code for free. You just need a 30B+ model and strict context window management! The Setup: I installed OpenCode extension in VS Code with Continue running qwen2.5-coder:latest locally. My goal: get that Claude Code autonomous agent experience (where the LLM reads files, writes code, runs commands, delivers results) but inside VS Code with a local model.
🚨 UPDATE: FIXED IT! 🤖 Local LLM + VS Code = Not Autonomous (Yet?) | OpenCode vs. Claude Code
1-30 of 2,120
Clief Notes
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
Powered by