[FEATURE] Manage Existing Memories.

[bdf1992]

Feature Description

Add a new tools for editing existing memories and creating new relations, allowing the LLM to affect only memories created previously, not create new ones.

Problem This Feature Solves

Currently, it's not possible for the LLM to edit its memory in any capacity using Basic Memory tools.
That means it's up to the person to manage editing existing memories and relationships.

EDIT: I think I was wrong about this. Looking at write_note again, it CAN edit files, but from my experience, the LLM is typically creating NEW files, even when instructed otherwise. This might be a ME problem. Maybe the AI Guide needs to account for those situations.

Proposed Solution

Describe how you envision this feature working:
edit_note: Allows the LLM to Edit existing memories rather than creating new ones.
relate_note: Seperate from editing, only creates new relationships based on context.

Impact

Right now, as the scope of a project grows the AI becomes less useful in managing existing memories and tends to create new memories and scope creep the files.

[phernandez]

Thanks for submitting an issue. I originally did have these edit and update_relation tools. But in practice the ai never used them. I consolidated to just write_note. If the AI calls write note with the same title and folder path it will perform an update. You can tell the AI to update notes or fix relations and it should be able to do it.

Let me know if this doesn't work for you.

[bdf1992]

@phernandez I just read through the docs again and made an Edit to my comment. I was wrong about write_note.

I'm finding the AI consistently prefers creating NEW memories to managing updates I request.

It will consistently create something like "Memory Name (UPDATED)"

Or when asking it to create new relations I find it tried to create a new memory to act as a place to create those relationships, rather than editing the relevant memories.

[bdf1992]

I think I figured out part of the problem. Sometimes, when it fails to find the file, it just defaults to creating a brand new file.

I think I'm also causing issues by changing the names of the files in some situations. Not sure if that's impacting this, but it doesn't seem to understand when I alter a file's NAME.

[phernandez]

Ahh. This makes sense. If you change the files manually the changes need to be synced back in so the db index is updated. Thats why the ai can’t see your updates for role renames. You can use the cli with the sync command to update the index basic-memory sync Add the —watch arg to have it watch for changes automatically I’m working on an update so the mcp process can do this automatically. Let me know if this helps.

…

On Wed, Mar 26, 2025, at 7:00 PM, bdf1992 wrote: I think I figured out part of the problem. Sometimes, when it fails to find the file, it just defaults to creating a brand new file. I think I'm also causing issues by changing the names of the files in some situations. Not sure if that's impacting this, but it doesn't seem to understand when I alter a file's NAME. — Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAO4H7UWQGSHCGCNG2UJL32WM5SPAVCNFSM6AAAAABZ3SHFGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJWGAZDOMZYHE>. You are receiving this because you were mentioned.Message ID: ***@***.***> bdf1992*bdf1992* left a comment (basicmachines-co/basic-memory#56) <#56 (comment)> I think I figured out part of the problem. Sometimes, when it fails to find the file, it just defaults to creating a brand new file. I think I'm also causing issues by changing the names of the files in some situations. Not sure if that's impacting this, but it doesn't seem to understand when I alter a file's NAME. — Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAO4H7UWQGSHCGCNG2UJL32WM5SPAVCNFSM6AAAAABZ3SHFGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJWGAZDOMZYHE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[phernandez]

This is still a new project. Lots of improvements to be made. Thanks for checking it out.

[bdf1992]

Well, so far, it's the best memory system I've used for Claude Desktop. I'm sold on this, and it's changed my entire workflow.

This is so much easier to manage than any other solutions I've tired, and the fact that it works with obsidian is brilliant.

[phernandez]

Thanks so much!

I've updated the docs at https://memory.basicmachines.co/ to be more clear about sync and updating notes by using the same title and folder names.

@bdf1992 if you have any other feedback feel free to get in touch via email: hello "at" basicmachines.co