Claude Code + Obsidian = UNLIMITED Memory! Solves Claude's Memory Problem!

Key Takeaways

Everyone knows that enthropic models are incredible, especially when it comes to coding. But when you're working with large code bases and long context, you'll sometimes notice a problem. Even when the model is quite powerful itself, like the Opus 4.6, they can still lose focus over time and occasionally forget steps you previously gave them. And when you're building a complex project, that can slow things down. But today I want to showcase a simple solution and it's with a tool called Obsidian which is completely free. Obsidian is a notetaking app that stores everything as a plain markdown file inside your folder on your computer. It is called the vault. This means your notes are not just text files. No proprietary format, no lockups, fully private and completely offline. But what makes it perfect for cloud code is that it keeps your memory or your context persistent. It keeps it structured and it is going to be there for your entire project for the architecture decisions, the design choices, key instructions, session summaries, to-do lists, bug notes, naming conversations, basically anything that matters. Because when it comes to readable markdown files in a folder, Cloud Code can directly read from the vault. It can search it. It can reference specific notes and it can even update them so that it could build on sessions after sessions. This gives Claude the long memory that it normally lacks in a chat interface or simply through the Claude code instance. So no longer you have to reexplain the same context every single time. the model is going to stay aligned with your original vision. Remember important details across weeks or even months and it produces far more consistent and focused code and this will overall dramatically reduce the forgotfulness and the problem that often happens in large code bases. So in short, when you combine Obsidian with cloud code, you have persistent memory and it enables a second brain for your codebase, which overall is going to get you better generations, smoother workflows, and far less frustration when you're working on large longunning projects. Still running object detection with NMS pipelines in 2026? Well, it's time for you to upgrade. And this is where I would like to introduce Ultral Litics YOLO 26, the nextG edge first vision model built end to end from the team behind YOLO version 5, YOLO version 8 as well as YOLO 11. YOLO 26 removes the non-maximum suppression entirely. This means true NMS free end to end inference, no fragile post-processing, lower latency as well as cleaner deployment. It removes distribution focal loss for better large object reliability and hardware compatibility. It also adds stall enhancements for stronger small object detection. It's up to 43% faster with CPU inference real time on existing hardware and built for edge devices in production systems. Plus, the new MUSGD optimizer improves training stability and convergences. This isn't built to win benchmarks. It's built to win in production. It's open source as well under the AGPL 3.0 for research and enterprise licensing is available for commercial deployment through Ultralytics. So if you're looking to try this out, you can do so cuz YOLO 26 is live now. You can try it out on the Ultralytics platform, which is today's video sponsor. Built end to end built for edge and this is the new standard for realtime vision AI. To get started, just make sure you have Claude Code ready and installed on the latest update, as well as having Obsidian installed, which is completely free to install, and I'll leave a link to this in the description below. Now, after installing, you will have this popup, and this is where you're going to need to create your vault. Now, what is a vault? Well, Obsidian basically is going to store all of your notes within your specific vault in a plain markdown file. This means everything is just a normal text file, but it is going to be readable, private, and easy for our tool like cloud code for example to easily access. Because these files live within this particular folder, Claude can see them, read them, search them, and update them during your coding sessions. Over time, the vault is going to become the persistent knowledge base for your project. Storing all of the important things that we're talking about that is prevalent within any codebase like the architecture decisions, the coding rules that you have set, bugs, session summaries, all of this could be updated and present within this one folder so that in future sessions it doesn't lose any sort of memory or any sort of behavior that you had taught it. So give it a name and you can select the location of wherever you want to place this vault. We have created the vault but what do we put inside it? Well this is where you want to simply start off with your file structures. You want to make sure that you are putting in all the relevant context that your cloud code agents can use. Making sure that you provide your GitHub related information whether that's your codebase prds research anything that claude can reference when making decisions. You can even provide meeting notes like transcripts that Claude can actually scan to recall past conversations from different sessions. You can even provide personal notes, ideas, writing, and long-term thinking that you personally have. So, we have created the vault and I have now added in a couple of different files, a few simple files like the project overview, my daily notes. And this is essentially where you want to provide as much context as possible, whether that's coding rules, session logs, whatever it may be. Cuz think of this as a memory file system for your AI instead of trying to remember everything inside the chat within the cloud code instance. Claude can read these notes whenever it needs because it's in an MD format. And this is where it gets powerful because I can simply even reference certain files or certain text stacks within this Obsidian vault before generating the code so that Claude can check how the project is structured, what frameworks I'm actually using, the coding conversations. And what I really like about Obsidian is it gives you a graph view of everything as well, so you get a better context idea of your real project memory. Now, what I would also recommend is installing the agent skills to use Obsidian better because this will teach Claude code how to interact with your vault that you have created better cuz it has these predefined skills that will be able to read your markdown files easier. So, Claude can parse your notes or any relevant information better. It can also write and update notes for you, which is great because after a claud session has completed for you, you can essentially have it write up a session note and upload it directly to your vault like I did over here after coding out I had created this simple note after that session so that whenever I pick up another cloud code session, I can reference this previous note so that it has that persistent memory in future generations. It also has ability to search and also reference content, maintain persistent memory through a normal chat instance as well as working with structured data. To get started, copy this first command, which is to install the marketplace for this plug-in. And you can then add that marketplace and then run the plug-in install command to set up the Obsidian skill. And you can set this up for your instance. And once that is ready, you can get started with your codebase. Now, to showcase our second brain in action and what it's capable of doing, what we're going to be doing is having it first reference a prior project. This is where I had an active project, a CRM dashboard with this text stack that I had built previously. Now, there's a lot of missing features. And what we're going to have it do is have Claude Code first pull the project context. This is where we're going to have it build a deals canband board using the Prisma deal model. and we're going to have it follow the CRM component architecture as well as the SHAD CN UI patterns that were previously active within our context. This is where it will first start off by checking out the component architecture, knowing which SHAD CN components you actually use, also referencing reusable patterns by reading the Shad CN UI patterns for forms, tables, modals, and toast notifications. also following the coding standards. And lastly, it can even update the vault cuz after it has finished generating this, it will update it based off the context, the new context that we had generated so that for future generations, it can reference this session to get better, smarter results even further in the future. So you can see that right now it is referencing the existing CRM project and the Prisma schema and it's able to reference the detailed information that we have present within our vault. So rather than having it just find context every single time, this persistent memory is going to be stable and always there within this vault so that pod can continuously use it whenever it needs it. And just an FYI, when you're working with the new Obsidian skill that we had installed, you can simply just type in /obsidian and then open up the Obsidian CLI so that Claude can actually use the Obsidian CLI to either read, create, edit notes, it can search the vault. So if you want to then ingest prior context, you can use the search vault command so that it is able to give your cloud code instance the particular knowledge that it needs. You can manage tasks, daily notes, as well as plug-in development. When you're working on a larger project with a lot of sub agents, it is going to be able to clearly describe the context across multiple agents and so that there's no deviation from whatever you're working upon. All the agents have the same mindset and that they're able to keep the same context as it's working through the progress. So in this case, one agent could be working with the deal pipeline and the other one could work on the analytics chart and over time it will be able to keep the same context, the same structure, the same text stack as it develops through everything. Thanks to cloud code getting the correct context that it needed for building out a new feature for our CRM dashboard like the shaden UI components, it was able to build out the cananban board feature that we had requested. This is where it was able to keep the consistency of our overall dashboard. It was able to use the correct components and you can see that it coded out this beautiful functionality with animations as added in all of the components that we had looked for. And that is what this new second brain actually solves. It makes your life easier when you're working with these AI agents. What's great is that the vault actually grows too cuz Claude always has up-to-date project memory when you reference the vault and after you have gotten the context you can even generate and update the code and provide daily notes on what was accomplished so that your overall notes is going to be able to stay up to date and for example you can just simply use the obsidian skill the markdown skill so that it is able to create a new note so that it provides a new daily note that our future session can actually revisit. That way, it is able to get the correct context as to what was added or built. And you can see right now that it is searching our previous pattern of the CRM dashboard that I built and it's going to create a new note on whatever it had developed. If you like this video and would love to support the channel, you can consider donating to my channel through the super thanks option below. Or you can consider joining our private Discord where you can access multiple subscriptions to different AI tools for free on a monthly basis, plus daily AI news and exclusive content, plus a lot more. But that's basically it, guys. I hope you enjoyed today's video. This is essentially where you can have Claude always have up-to-date project memory with this second brain. But all you got to do is make sure that you have the correct structure set up with your file structure. and which is why I will leave this article in the description below. It's not extraordinary or anything, but it tells you the basic structure that you need when you're working with this workflow. But that's basically it, guys. I hope you found this video to be helpful. It is something that will make sure your AI sub agents within Claude have the correct context that it needs over time. I'll leave all these links in the description below. But with that thought, guys, thank you guys so much for watching. Make sure you join the newsletter, subscribe to our second channel, join our discord, follow me on Twitter, and lastly, make sure you guys subscribe, turn on notification bell, like this video, and please take a look at our previous videos so that you can stay up to date with the latest AI news. But with that thought, guys, have an amazing day, spread positivity, and I'll see you guys fairly shortly. his offers.