Patching Claude Code's memory system Last week asked it to help me fix a memory leak bug, and this week I encountered a similar problem, and it guessed it from scratch. It can store preferences and project information, but it is not suitable for storing pit records - it is getting longer and longer, and it can only be searched in full text, and the search for "script keeps rising" cannot find "how to fix memory overflow". What I want is that when I have a problem, it can say "We solved something similar before." My solution: Maintain the experience library separately + semantic search + automatic update • Record pitfalls: scenarios, problems, solutions, lessons • Build a local search library to support semantic matching - "script memory keeps rising" can find "how to fix memory overflow" • Writing rules: check the database first when encountering problems and then do it • Automatic update: After writing experience, it will be automatically stored in the database, and there is no need to manually maintain the current more than 20 articles, to be honest, it has not really come in handy - most of them have only recently been precipitated. But this is planting trees, and after planting them now, they will enjoy the shade. Technology stack: ChromaDB for vector storage, Claude Code hooks for real-time triggering, launchd for timing bottom.