MemWireConfig. Choose your vector store, embedding model, and LLM provider, then tune recall and graph settings to fit your use case.
Components
Vector Databases
Connect to a vector store.
Embedding Models
Choose embedding model.
LLMs
Use any LLM provider with recalled context.
SQL Databases
Choose where to store metadata ledger for memories, graph edges, and categories.
Recall tuning
Recall assembles relevant memories into a formatted context string for injection into LLM prompts.Graph construction
MemWire organises memories in a graph. Edges encode semantic relationships between memories.Memory classification
Memories are automatically classified into categories using zero-shot cosine similarity.Feedback loop
SQL Databases
MemWire stores memory metadata — content, graph edges, categories, and access counts — in a SQL database, while all embedding vectors live separately in a vector store. SQLite is the default because it requires no server or configuration, letting you run MemWire locally out of the box; switch to PostgreSQL or any other SQLAlchemy-compatible database by settingdatabase_url.
Performance
Search quality
Control how memories are retrieved during search and recall.Recall tuning
Recall assembles relevant memories into a formatted context string for injection into LLM prompts.Graph construction
MemWire organises memories in a graph. Edges encode semantic relationships between memories.Memory classification
Memories are automatically classified into categories. Classification uses zero-shot cosine similarity against anchor phrases.Feedback loop
The feedback loop reinforces graph edges that led to good responses, and weakens edges that did not contribute.
Call
memory.feedback() after each LLM response to close the loop:

