This release is a pre-release and may not be stable for production use.
Redis Iris
One package for every Iris product: an opinionated Python API per product, and the iris CLI to set them all up.
Install
Requires Python 3.11+. uv is the recommended installer.
uv add redis-iris # library, in your project
uv tool install redis-iris # iris CLI, isolated
iris --help
pipx or pip
pipx install redis-iris
python -m pip install redis-iris # inside an active virtual environment
From a source checkout, uv tool install --force . installs or replaces the iris tool, and
python -m redis_iris runs the CLI wherever the package is installed.
Alpha releases may change commands and output contracts. Pin a version in automation and check the release notes before upgrading.
The stack
Iris is a suite of products. Use one, or all of them.
| Product | What your agent gets | Instead of |
|---|---|---|
| Agent Memory | Ordered session history, summarized automatically. Durable memories extracted in the background, typed to your domain and steered away from sensitive data. Recall across sessions, scoped to one customer plus shared team knowledge. Erase a customer in one call. | an in-process store, a hand-built extraction chain, regex scrubbing |
| Playbook | Answers only from published, versioned FAQs and Skills, scored. Rollback and withdrawal. Proposes an FAQ for human review when nothing covers the question. | a vector store of unreviewed policy docs |
| Context Retriever (coming soon) | Typed MCP tools generated from your data model: get, filter, search, per entity. Read-only agent keys scoped to one surface. Your Redis data stays where it is. | hand-written @tool functions over your database |
| Lens (coming soon) | One trace per turn: which memories and documents entered the prompt, tokens, cost. | guessing why the agent said that |
| LangCache (coming soon) | Exact and semantic cache for repeated questions, scoped by attributes, conversation-aware. | paying for the same answer twice |
User guides
| Your agent... | Guide | Product |
|---|---|---|
| forgets customers between sessions | Remember customers | Agent Memory |
| quotes policy nobody approved | Answer from approved policy | Playbook |
| needs live account data, not documents | Live account data | Context Retriever |
| needs all three in one message | One support turn | Iris |
| needs to be configured | Configuration | all |
| needs an Agent Memory service created | Set up Agent Memory | Agent Memory |
| needs a Playbook and an agent key created | Set up Playbook | Playbook |
| has policy content to author and publish | Playbook CLI | Playbook |
Integrate with an existing agent
Built your stack with a popular orchestration tool? A skill lets your coding agent do the wiring.
| I want my agent to... | Skill |
|---|---|
| figure out what it needs | add-redis-iris |
| remember customers | add-agent-memory |
| quote approved policy only | add-playbook |
| use live account data | add-context-retriever |
The CLI
iris <product> <command> creates services, mints keys, and manages content. Shared options go
before the product name.
iris agent-memory service create --from service.yaml --write-env .env
iris playbook faqs validate ./faqs # offline
iris playbook faqs sync ./faqs --publish changed
iris --json --no-input playbook faqs plan ./faqs # unattended, one JSON value on stdout
iris --profile production playbook health
Settings resolve from command options, environment variables, the selected TOML profile, shared
TOML settings, then defaults. API keys belong in environment variables. Exit codes are 0 for
success, 1 for operational failures, and 2 for invalid input or configuration. Help, version,
completion, and local validation work without credentials or a network connection.
Guides: Set up Agent Memory, Set up Playbook, Playbook CLI, Configuration, example TOML.
Documentation
| Resource | Start here to... |
|---|---|
| Core reference | Every redis_iris class and setting |
| User guides | One problem, one fix, per product |
| Skills | Wire a product into an existing agent with a coding agent |
| llms.txt | Hand the whole docs site to a coding agent in one fetch |
| Design | What the package is, and why it is shaped this way |
| Release notes | Check changes before upgrading |
Contributing
Bug reports, documentation improvements, and new integrations are welcome. Open an issue or read the contributor guide.
task install
task check # formatting, lint, types, offline tests, package build
Maintainers publish with the release runbook.
License
MIT.
Metadata
Release files for redis-iris 0.1.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| redis_iris-0.1.0a1.tar.gz | 472.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| redis_iris-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 571.3 kB
Release files / redis_iris-0.1.0a1.tar.gz
| Download URL | redis_iris-0.1.0a1.tar.gz |
|---|---|
| Size | 472.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cfd702c42d6abc6dfcad9391864dfba5ae244599859b42d4dc2155915dec540f
|
|
BLAKE2b-256 checksum How to use checksums |
7c3087375333aabaf8d0b482a22374f0560a30e2d5896cd8fdec1bdd368f47f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / redis_iris-0.1.0a1-py3-none-any.whl
| Download URL | redis_iris-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 98.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e8c4bcad3139dd7d05554255566f0b8168df6cb71dd7b6af16e43b7e6721a30c
|
|
BLAKE2b-256 checksum How to use checksums |
ef4fe5d8eb56d13f4e9bc6dd3eff1a556725e02884743ada4a61df268c55edbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|