I just built my first site using a playbook on 0ne AI. I've made probably 10 sites since I started. This one was different. Instead of building from scratch again, I created a playbook. It defines exactly how I want my static sites to look. Then I set up a context doc so I can rinse and repeat every time. Now the process is dead simple. Fill out the context doc like Jimmy showed in the lesson. Feed it to 0ne AI. The playbook builds the site. Tried it last weekend. Wow. Site one came out great. Site two? Done so fast it wasn't even close to how long my old builds took. Hearing it is one thing. Doing it is when it all clicks. Now I'm hooked on thinking about more playbooks I can build. The speed and how repeatable it is got me. Where else am I doing the same thing over and over that could be systemized like this? That's the real unlock. Build it once. Run it forever. What would you build a playbook for?

Just put together a quick beginner's walkthrough on using 0ne AI alongside Obsidian for note sharing. If you've been meaning to get this set up but kept putting it off, this is your sign. I'll show you how to run the AI we built in Claude Code, the basics of Obsidian (don't worry, it's way less intimidating than it looks), and how to grab my favorite plugin so you can share notes without the headache. This is the first of a few I've got planned, so consider it your starting point. Watch it, try it, and drop a comment if you got it working or if you got stuck somewhere. More coming soon 🎥

Hey @Jimmy Fuentes @Juan Gomez, I used to see at the bottom of my terminal session a line of text that showed me the percentage of my "usage" for that session. It's not there anymore! Did I change something accidentally, or is it a VS Code thing? TIA!

How to Fix a Crashed or Frozen Update Hey everyone - quick troubleshooting guide based on a real issue one of our members ran into today. What Happened During a routine update, the install froze halfway through. When she tried to open Claude Code again, she got this error: The term 'C:\Users...\node_modules@anthropic-ai\claude-code\bin\claude.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Translation: The update started downloading the new version but never finished. The old version was already removed, so now the system can't find the program at all. Nothing is broken with your computer or your data -- it's just a half-finished update. How to Fix It (2 Minutes) Step 1: Open PowerShell Press the Windows key Type PowerShell Click Windows PowerShell (run as Administrator if prompted) Step 2: Uninstall the broken version Copy and paste this command, then press Enter: npm uninstall -g @anthropic-ai/claude-code Wait for it to finish completely before moving to the next step. Step 3: Reinstall fresh Copy and paste this command, then press Enter: npm install -g @anthropic-ai/claude-code This will download and install a clean copy. It may take a minute or two. Step 4: Verify it works Copy and paste this command, then press Enter: claude --version You should see a version number printed out. If you do, you're good to go! If That Doesn't Work In rare cases, the leftover files from the crashed update can block the reinstall. If Step 3 fails or you still get errors, run these commands one at a time: Remove-Item -Recurse -Force "$env:APPDATA\npm\node_modules\@anthropic-ai" npm install -g @anthropic-ai/claude-code Then run claude --version again to confirm. How to Avoid This in the Future Don't close the terminal while an update is running -- let it finish If your internet connection drops mid-update, just re-run the install command above and it will pick up cleanly Updates usually take under a minute, so if it's been stuck for more than 5 minutes, it's safe to close and re-run the install

Just pushed the latest update. If you're running 0ne, you can update right now by typing /0neUpdate in your terminal. Here's what changed: 0neSync — your new daily execution engine This is the big one. The old DayOS skill has been rebuilt from the ground up as 0neSync — a constraint-router-first system. Run it anytime — between tasks, at the gym, whenever you feel drift — and it answers one question: "What is the single highest-ROI thing I should do right now?" It works in two layers: 1. The constraint router (new) — checks your deadlines, protected time blocks, and your current constraint, then gives you ONE next physical action. No overwhelm. No decision fatigue. Just the next move. 2. The DayOS cycle (same as before) — capture, clarify, complete, weekly review. If you already built that muscle memory, it all still works. Triggers: /0neSync, "what now", "what's next", "set the constraint." Terminal font auto-fix If you've ever seen garbled characters in your terminal (weird symbols where icons should be), /0neDoctor now detects and auto-installs the correct font (JetBrainsMono Nerd Font). No more manual font troubleshooting. Internal fixes - Install template cleanup - Sync verification tool fixed (was causing a recurring loop for some users) How to update: Open your terminal and run /0neUpdate. It'll download, merge your customizations safely, and verify everything with the doctor. Takes about 30 seconds. Drop any questions below or bring them to the next live call.