xyberos-redis
Redis plugin — RFC-0019, M4. RedisVectorStore + RedisMemory + cache
backing for CacheResponder, all lazy-importing redis. Covers the
[state] extra scope (cache + state + vector).
Install
pip install xyberos-redis # from PyPI
pip install "xyberos-redis[state]" # pulls in redis
# development (editable, from this repo):
pip install -e ./redis
pip install redis # or: pip install xyberos[state]
Usage
from xyberos import create_app
from xyberos_redis import RedisPlugin
app = create_app()
app.load_plugin(RedisPlugin(url="redis://localhost:6379")) # or set REDIS_URL
vector = app.resolve("redis_vector") # a VectorStore
memory = app.resolve("redis_memory") # a Memory
cache = app.resolve("redis_cache") # exact-match string cache
RedisPlugin(replace_defaults=True) also swaps the app's vector_store /
memory providers.
CacheResponder backing
RedisVectorStore is a full VectorStore, so it plugs straight into the core
CacheResponder for near-exact prompt -> answer caching:
from xyberos.llm import HashEmbedder
from xyberos.router import CacheResponder
from xyberos_redis import RedisVectorStore
responder = CacheResponder(store=RedisVectorStore(url="redis://localhost:6379"),
embedder=HashEmbedder())
responder.teach("what is xyberos?", "a cognitive platform")
Design
RedisVectorStore— one Redis hash per namespace; vectors JSON-encoded; queries scored with exact cosine (the same scan-and-score approach as the stdlibSqliteVectorStore, so behavior — and parity — holds without needing a RediSearch vector module).RedisMemory— one entry perstore()appended to a Redis list;retrieve()returnsMemoryEntrys oldest-first, mirroringSqliteMemory.RedisStringCache— tiny exact-matchget/set/deletewith optional TTL.redisis imported lazily; a clearProviderErroris raised when missing.
Tests
pip install pytest fakeredis
pytest tests/
Tests run against fakeredis (an in-memory redis-py client), so they need no
Redis server; they skip cleanly when redis/fakeredis are absent. The vector
parity tests run the exact scenarios the SqliteVectorStore reference passes.
Ship location
[state] extra (redis already added to pyproject.toml).
Metadata
Release files for xyberos-redis 0.1.2
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 |
|---|---|---|---|---|
| xyberos_redis-0.1.2.tar.gz | 9.2 kB | With provenance | Details for xyberos_redis-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| xyberos_redis-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for xyberos_redis-0.1.2-py3-none-any.whl |
Total release size: 17.9 kB
Release files / xyberos_redis-0.1.2.tar.gz
| Download URL | xyberos_redis-0.1.2.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c778bc8496625001373f1808aa464ffd791cb8ddab73ecc00bb22c5c75976bd
|
|
BLAKE2b-256 checksum How to use checksums |
98e455a9790d85d53e11d4908324864411a309c2ebee1a73e838813f2a7e251c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 11, 2026.
Transparency logRelease files / xyberos_redis-0.1.2-py3-none-any.whl
| Download URL | xyberos_redis-0.1.2-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b5d3852ee2f1196f8f80a7702853a35a1e88d5026fc5dabed4bd2b9950fa285
|
|
BLAKE2b-256 checksum How to use checksums |
0c6c91c920493ba9d98c1343756fa133e54f390e8f7d50d0d484b5fb409d634a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 11, 2026.
Transparency logSecurity for xyberos-redis 0.1.2
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for xyberos_redis-0.1.2.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 Oct 11, 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.