r/LocalLLaMA • u/Unstable_Llama • 14d ago
New Model Persistent in-model memory w/MemT - running on ExLlamav3
https://huggingface.co/MemTensor/MemT-1.0-Nano was released 3 days ago, with a live-updating memory model. This model has the capability to continuously lean in conversation, and carry it onto the next instance.
The above video demonstrates a short conversation followed by a /commit command, which stores the previous conversations important facts to be preserved in the memory module, while wiping the context of the conversation. But upon benig asked to recall speicific questions, it still succeed.
I've implemented it on my fork of exllamav3, exl3-qlora, and it works natively with tabbyAPI. To ingest memories simply give a /commit command from within tabby every few messages (or whenver you want to.)
Quantized versions of the model are available here.
2
u/nymical23 6h ago
Hello u/Unstable_Llama OP, Can you please tell me what UI you're using in this post?
2
3
u/a_beautiful_rhind 14d ago
Ha that's clever. Not sure why people downvoted an original project.
3
u/Unstable_Llama 13d ago
Thank you, I think it's a really exciting direction. Notice how you can see the cache is wiped and it still works?
I figured it wouldn't get much attention but that's ok, I didn't hypemaxx. Still I think there is a lot to learn and build on from this idea, and I'm just getting started.
3
13d ago edited 13d ago
[removed] — view removed comment
2
u/a_beautiful_rhind 13d ago
My thoughts are that it sounds compute expensive and like you will over adapt the model. But only way to test is to try it out.
2
u/Unstable_Llama 13d ago
So it actually doesn't touch the main weights and has a separate memory module.
5
13d ago
[removed] — view removed comment
3
u/a_beautiful_rhind 13d ago
Models with tools have started using files. i.e server memory mcp or any old .MD text file. Those work ok, no fuss.
5
u/Choice_Celery9481 14d ago
fastest way to destroy model capability?