Import Knowledge and Memory Portability (import-kb)
A utility package for importing distilled knowledge into a ChromaDB-based Long-Term Memory (LTM) system and backing up or restoring OmegaClaw user memory.
Purpose
The import-kb package is designed to bridge the gap between static knowledge files (JSONL, MeTTa) and an active agent's memory. It processes structured knowledge, generates vector embeddings, and upserts them into a ChromaDB collection, enabling semantic search and retrieval for AI agents.
The package also provides memory_portability, a programmatic interface for exporting and restoring OmegaClaw conversation history and user LTM records. OmegaClaw Core remains responsible for its CLI, container lifecycle, transfer-directory mount, and user-facing decisions.
Supported Embedding Models
This package supports two primary embedding modes:
- OpenAI (Cloud):
- Default model:
text-embedding-3-large - High accuracy but requires an internet connection and an API key.
- Default model:
- SentenceTransformers (Local):
- Default model:
intfloat/e5-large-v2 - Runs fully offline on your local machine.
- Can be configured to use any model compatible with the
sentence-transformerslibrary (e.g.,all-MiniLM-L6-v2).
- Default model:
Installation
You can install the package directly from PyPI:
pip install import-kb
Or install it locally in editable mode:
git clone <repository-url>
cd import-knowledge-package
pip install -e .
Setup
Create a .env file in your project root or set the following environment variables:
OPENAI_API_KEY: Required if using OpenAI embeddings.CHROMA_DB_PATH: (Optional) Custom path to your Chroma database. Defaults to looking for/PeTTa/chroma_dbor a localchroma_dbfolder.
How to Run
Command Line Interface (CLI)
After installation, you can run the import via the provided entry point:
# Use OpenAI embeddings (default)
import-knowledge
# Use Local embeddings
import-knowledge --local
# Use a specific local model
import-knowledge --local --model "all-MiniLM-L6-v2"
# Override OpenAI model
import-knowledge --model "text-embedding-3-small"
Alternatively, run it as a module:
python3 -m import_knowledge.import_knowledge --local
Programmatic Usage
You can initialize the embedding system and trigger the import programmatically from your Python scripts:
from import_knowledge import initLocalEmbedding, main
# Initialize for local use
initLocalEmbedding(model_name="intfloat/e5-large-v2")
# Run the import process
main()
Memory Portability
MemoryTransfer exports selected user-memory components to one portable archive and imports them using either overwrite or append behavior.
Configuration
The implementation uses environment variables and can also accept paths directly:
MEMORY_DIR: OmegaClaw memory directory containinghistory.mettaand import transaction state.CHROMA_DB_PATH: ChromaDB persistence directory.MEMORY_TRANSFER_DIR: Directory containing exported and imported archives. Defaults to/memory-transfer.EMBEDDING_PROVIDER:LocalorOpenAI.SENTENCE_TRANSFORMERS_MODEL: Active local embedding model. Defaults tointfloat/e5-large-v2.OPENAI_EMBEDDING_MODEL: Active OpenAI embedding model. Defaults totext-embedding-3-large.EMBEDDING_DIMENSION: Optional vector dimension for a custom embedding model.OMEGACLAW_VERSION: Optional source version recorded in the archive manifest.
OpenAI re-embedding also requires OPENAI_API_KEY.
Export
from memory_portability import MemoryTransfer
transfer = MemoryTransfer()
# component may be "history", "ltm", or "both".
result = transfer.export(component="both")
print(result["filename"])
The export is synchronous. If the host application permits concurrent memory writes, it should hold its memory-write lock while exporting when a cross-component point-in-time snapshot is required.
The archive contains only the selected files:
manifest.json
history/history.metta
vector/collections.json
vector/records.jsonl
ChromaDB is exported as logical user-memory records rather than raw database files. Knowledge priors and operational records are excluded.
Import
The filename must be a plain .tar.gz filename located inside the configured transfer directory:
result = transfer.import_archive(
"omegaclaw-memory-20260822T120000Z.tar.gz",
mode="overwrite",
include_history=True,
include_vectors=True,
)
Import modes:
overwritereplaces the selected user-memory components and restores their previous state if the operation fails.appendkeeps existing history and LTM records, appending history and assigning namespaced IDs to imported vectors.
Archives are validated before live memory is modified. Validation covers the manifest, allowed archive members, paths, sizes, checksums, record counts, and embedding dimensions. Missing or incompatible embeddings are regenerated with the active embedding provider.
Interrupted Import Recovery
Call recovery before starting a new import or before the host agent begins using memory:
recovery = transfer.recover()
print(recovery["status"])
Recovery completes an already committed transaction or rolls back an interrupted one. Import receipts prevent the same archive and import selection from being applied more than once.
Dependencies
openai: For cloud-based embeddings.sentence-transformers: For local, offline embeddings.chromadb: Vector database for storage.python-dotenv: Management of environment variables.tqdm: Progress bars for batch processing.
License
This project is licensed under the Apache License 2.0. See LICENSE file for details.
Metadata
Release files for import-kb 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| import_kb-0.2.0.tar.gz | 2.6 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| import_kb-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.3 MB
Release files / import_kb-0.2.0.tar.gz
| Download URL | import_kb-0.2.0.tar.gz |
|---|---|
| Size | 2.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8cd0437cca910a579d938c0b43a9d2eb0b8a21e2460870cb9c36277d7f895204
|
|
BLAKE2b-256 checksum How to use checksums |
7f4231765f06f16e45478579ab6ac798be0a7012b410d1510dfe4f005e88735e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / import_kb-0.2.0-py3-none-any.whl
| Download URL | import_kb-0.2.0-py3-none-any.whl |
|---|---|
| Size | 2.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
28a737064f2ad0142a7c8a533d5364a6629addbd4978d1a193e59b0e84067df2
|
|
BLAKE2b-256 checksum How to use checksums |
e2cc67391f8a47054f0c0257002963aa28dabd9619ba29062202a7c83f2cefe2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for import-kb 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.