okay Codexers, this is something i've wanted to do for a long time but simply haven't prioritized it. so at today's codex club call we're going over: - why bother building a second brain in Obsidian? is it even worth it? - if so - how do you actually build one? like how do i get started from scratch? - what's the best way to integrate it into my day-to-day work? - how do i auto-magically keep it up-to-date so it doesn't get stale or become burdensome to maintain? if that sounds like your cup of tea, add the call to your calendar HERE 🗓️ hopefully see you in 2 hours!

alrighty guys, it's finally here. this is what i intended to give y'all at Tuesday's Codex Club Call before i had the screen recording issues. i felt bad for the tech fail and spent the last 2 days upgrading Eddy from a simple skill into a fully-fledged Codex plugin. what does Eddy do? well check out the attached Loom... but in short Eddy edits raw footage into a retention-optimized ready-to-publish YouTube video (still review the output obviously) AND creates short-form videos from the raw footage with captions. it also applies studio sound to your audio. it can also apply motion graphics.. i will continue to update Eddy as i find other things i want an agentic video editor to do, but it's already pretty good if i say so myself. @Karl Bro this one is for you brother! how to install it: paste this into Codex and hit enter: @plugin-creator install [lennoxsaint/eddy](https://github.com/lennoxsaint/eddy) how to use it: dump your raw footage into Codex, type "@eddy - edit this" that's it. pro tip: if you don't know how to use Eddy, just ask codex "how do i use Eddy?" lastly, if you have any requests or spot any bugs/things it can do better, let me know in the comments below!

i just published the full CAPS walkthrough. this is the clearest version of what i mean when i say Codex is not just a coding app for me anymore. it is the place where my work lives. the mechanism is pinned productivity: 1. one conductor thread that holds the shape of the day 2. pinned lanes for the work that actually matters 3. proof receipts so the system cannot fake progress 4. memory so good decisions do not disappear 5. browser-in-agent work so Codex can actually move the task forward that is the difference between a normal to-do list and CAPS. a to-do list stores intentions. CAPS helps turn those intentions into action. watch the full video here: https://youtu.be/3ctSNHFw8Rw grab the free CAPS repo here: https://github.com/lennoxsaint/caps-productivity-kit

Codexers - welcome to the club! we've had a big influx of new members over the past 24 hours and it's a true pleasure to have you here. i've got a new X article hot off the press for you HERE. the promise: - give the link to the article to your Codex agent and give it this prompt: "read this article: https://x.com/lennox_saint/status/2063320914901795309 then create a plan to install the CAPS system it describes. also use this github repo: https://github.com/lennoxsaint/caps-productivity-kit then return with a summary of everything you set up, how it can help me specifically, what immediate practical benefits i can expect and one test prompt i can run right now to see everything you've set up in action." once you've done that - let me know below what your Codex did (or even better - share a screenshot)!

Codexers - welcome to the club. Codex Club is for non-coders, service operators, freelancers, consultants, creators, and quietly dangerous business people who want to stop saving AI posts and start shipping useful things. the goal is simple: use Codex and AI to build your first practical AI service product. not theory. not prompt hoarding. not "one day i should learn how this works." every week, you get: - one practical Skill Drop or Codex workflow. - one Weekly Build Challenge. - a simple proof prompt. - a place to post what you made, what broke, and what you need help with next. start here: go to the Start Here classroom page first. it shows you how Codex Club works, what to do in your first 10 minutes, where the current weekly challenge lives, how to post proof without overthinking it, and when Build With Lennox makes sense. your first move: this week's challenge is Find Your AI Service Product. your job is to pick one AI service product idea from real signal, not vibes. use Skill Drop 001: Offer Signal Snapshot. then post your first proof using this sentence: I help [buyer] get [outcome] using [AI/Codex mechanism]. ugly first drafts count. quiet lurker mode does not build the thing. new here? reply with: 1. what you already help people do. 2. who you want to help. 3. your rough AI service product sentence: I help [buyer] get [outcome] using [AI/Codex mechanism]. then go do the Week 1 challenge in Weekly Build Challenges.