Feature Request: Add Moorcheh as vector store backend for agent LTM
Author: Neelpatel1604Created Jul 10, 2026Updated Jul 10, 2026
Summary
Add Moorcheh as a new vector store backend for SuperAGI agent long-term memory (LTM), following the existing VectorStore + VectorFactory pattern used by Redis, Pinecone, Qdrant, and Weaviate.
Motivation
- SuperAGI has no unified memory provider - LTM is wired via
VectorStoresubclasses andVectorFactory - Moorcheh is a managed, text-first semantic search/memory service - fits the existing
add_texts/get_matching_textflow without requiring self-hosted vector DB infra - Useful for teams that want serverless agent memory without running Redis/Pinecone/Qdrant
Proposed scope (v1)
- Add
MOORCHEHtoVectorStoreTypeenum - New
superagi/vector_store/moorcheh.pyimplementingVectorStore - Wire into
VectorFactory.get_vector_storage()andbuild_vector_storage() - Config:
MOORCHEH_API_KEYinconfig_template.yaml - Add
moorcheh-sdktorequirements.txt - Unit tests under
tests/unit_tests/vector_store/ - Allow LTM when
LTM_DB=Moorcheheven for non-OpenAI models (Moorcheh handles embeddings)
Out of scope (follow-up PRs)
- Resource uploads via
LlamaVectorStoreFactory - Knowledge marketplace
/connect/moorchehendpoint - GUI LTM picker update
- Per-agent
LTM_DBwiring (stored in config but not used at runtime today)
Integration points
| Layer | Files |
|---|---|
| Write | superagi/agent/output_handler.py |
| Read | superagi/tools/tool_response_query_manager.py |
| Bootstrap | superagi/jobs/agent_executor.py |
Acceptance criteria
-
LTM_DB=Moorchehcreates memory viaVectorFactory - Tool outputs are written to Moorcheh after each step
-
ToolResponseQueryManagercan recall relevant past tool output -
get_matching_textreturns{"documents": [...], "search_res": "..."} - Unit tests pass in CI ]
Source: TransformerOptimus/SuperAGI