Happy Saturday everyone, here’s something new for this weekend!

Has anyone found a good workaround for getting Gemini to remember your preferences across all chats when you have a Google Workspace account? I'm a solo business owner and use Gemini for a variety of tasks, but I find myself having to repeat the same information in every new chat, such as my writing style, formatting preferences, business information, brand voice, and other recurring instructions. I've experimented with Gems, but they seem limiting because I have different Gems for different purposes. If I need the functionality of multiple Gems in one conversation, there doesn't seem to be a way to combine them, so I end up repeating information anyway. Has anyone come up with a workflow that solves this? If not, maybe I should l use a different AI platform? I was using ChatGPT but did not like it. Thank you!

Quick update for the community: in my last post I mentioned I was planning something with Fable 5. That plan is now in motion, and honestly, the results are next level. I handed it a seriously complex task — multi-step, the kind of thing that usually breaks other models — and it just… handled it. I genuinely don't think any other AI model could have done this end-to-end. Discussion for the group: 1️⃣ Who here is using Fable 5 in Claude Code? 2️⃣ What's the most valuable thing it's done for you so far — a workflow, an automation, a build? Share below — let's learn from each other's use cases. 👇 Meanwhile, I'm off to power up a client's business with Claude Code with Fable 5 AI Model, and Hermes AI. Full breakdown coming in the next video. 🚀

There's a guy on Reddit making a full-time living fixing vibe-coded apps. But the most interesting thing he said wasn't about the founders hiring him. It was this: "About 70% of what I end up fixing is stuff the founder could have checked themselves in an afternoon." That line stuck with me. Because it means the rescue business isn't booming because building with AI is too hard. It's booming because nobody told founders what to check before they shipped. And I see this every week. People are shipping real products. Apps they described in plain English. Apps they prompted into existence. Apps with paying customers. Honestly, I love that. That is the promise of this whole moment. But there is a quiet gap between: "It works on my screen." and "This is safe to put in front of customers." That gap is exactly where the rescue invoices come from. The good news? That gap is checkable. You do not need to become an engineer to close it. You just need a short checklist you run every single time before you deploy. Here are the four things that break most often and how to fix them: https://open.substack.com/pub/thisaitooldoesthat/p/the-vibe-coding-rescue-economy-exists?r=7rf2o6&utm_campaign=post&utm_medium=web&showWelcomeOnShare=true