Runtime 0.6.0: portable Codex memories
This release adds explicit Codex v1/v2 semantic-memory inspection and import, plus readable, verifiable JSON/Markdown handoff packages. Native sources and Qdrant records remain independent of plugin installation. Uninstalling the plugin does not remove stored memories or exports.
Inspect the installed qdrant-memory codex --help before selecting an operation.
Preview imports and review skipped records before committing them. Credentials,
code fences, raw conversations and unsupported artifacts do not become semantic
memories through this adapter.
Handoff verification checks record identity, content, scope, size and checksums.
It does not claim that Codex has adopted the package: the status remains
HANDOFF_PENDING until the destination confirms actual adoption. Bulk native
writeback is not provided.
macOS/Linux use descriptor-relative no-follow reads. Windows uses checked native handles, refuses reparse points and remote volumes, and requires persistent private ACLs for created handoff directories. Unsupported filesystem guarantees fail closed.
Scoped deletion also supersedes quarantined events for the deleted scope. Retrying failed work or restarting the provider cannot recreate those deleted memories; records in other scopes remain intact.
The optional CPU backend uses upstream FastEmbed 0.9.1. Profiles created before Runtime 0.5.5 may record the older 0.9.0 pipeline fingerprint. Preserve their environment, store and cache; export authorized records and re-embed them into a new profile and collection before switching. Do not relabel an existing collection's pipeline fingerprint. See the CPU setup guide below.
Explicit model preparation allows 15 minutes per artifact, retaining byte limits, immutable hashes and atomic cache publication. Slow networks have a wider window. An incomplete or over-budget download never becomes a ready cache. All model downloads share a 30-minute network budget. Real CPU CI allows 60 minutes, leaving time for dependencies and acceptance after download. The cancellable deadline covers connection, response headers and streamed body reads, including continuous tiny fragments. Timeout closes the stream/client, removes temporary files and releases the preparation lock before a retry.
The Codex/Ollama Cloud acceptance uses synthetic data and local embedding fixtures. It validates harness/tool behavior, not embedding-model inference. Runtime, Python MCP, managed launchers and Skills have independent releases and reviewed pins. Publishing this Runtime does not automatically upgrade them or publish the Codex Marketplace candidate.
Install this release
Confirm version 0.6.0 is available on PyPI before installing:
python -m pip install 'hermes-plugin-qdrant-memory[mcp]==0.6.0'
qdrant-memory --help
This installs the standalone CLI and MCP base without Hermes. Add the local
extra for optional CPU embeddings. Model preparation requires explicit approval.
Configure a private profile before memory operations. See the
standalone guide
and CPU setup.
Metadata
Release files for hermes-plugin-qdrant-memory 0.6.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 | Actions |
|---|---|---|---|---|
| hermes_plugin_qdrant_memory-0.6.0.tar.gz | 422.0 kB | With provenance | Details for hermes_plugin_qdrant_memory-0.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hermes_plugin_qdrant_memory-0.6.0-py3-none-any.whl | Python 3 | none | any | Details for hermes_plugin_qdrant_memory-0.6.0-py3-none-any.whl |
Total release size: 581.2 kB
Release files / hermes_plugin_qdrant_memory-0.6.0.tar.gz
| Download URL | hermes_plugin_qdrant_memory-0.6.0.tar.gz |
|---|---|
| Size | 422.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5099eb7adf0a7aac27c23dd663f36fc48782fcb7b5a24618dab1aec4c9d0099c
|
|
BLAKE2b-256 checksum How to use checksums |
94c647c6cdd806d8322596394c50a12f1255ffda65576bd5a53f898e4c7a3214
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logRelease files / hermes_plugin_qdrant_memory-0.6.0-py3-none-any.whl
| Download URL | hermes_plugin_qdrant_memory-0.6.0-py3-none-any.whl |
|---|---|
| Size | 159.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
484a3cdd45ee5ecff92b76be062046597a7fcf9e58ad9667a993a80b77ef6a15
|
|
BLAKE2b-256 checksum How to use checksums |
83b3c3cac42e78f6ae633e879f5b71c6bcf6ad98930d6c1b01e575feb689f436
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logSecurity for hermes-plugin-qdrant-memory 0.6.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for hermes_plugin_qdrant_memory-0.6.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logA 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.