[feat] Add Valkey database and Vector database adapters

[edlng]

Summary

Closes #7795

Adds Valkey as a database backend (session store) and vector database adapter, using the Valkey GLIDE client (valkey-glide). Valkey is a Redis fork maintained by the Linux Foundation.

The session store (ValkeyDb) implements the BaseDb interface: sessions, memories, metrics, evals, knowledge, cultural knowledge, traces, spans, and learnings. Data is stored as JSON in Valkey keys with secondary index sets for filtered lookups.

The vector store (ValkeyDB) supports vector similarity search, keyword search, and document CRUD using Valkey's search module (for FT.SEARCH). Supports auth, TLS, and database selection.

Includes cookbook examples for storage and vector DB usage, unit tests with a mocked GLIDE client, integration tests against a live Valkey instance, and schema definitions that document the expected fields for each record type.

Type of change

• Bug fix
• New feature
• Breaking change
• Improvement
• Model update
• Other:

---

Checklist

• Code complies with style guidelines
• Ran format/validation scripts (./scripts/format.sh and ./scripts/validate.sh)
• Self-review completed
• Documentation updated (comments, docstrings)
• Examples and guides: Relevant cookbook examples have been included or updated (if applicable)
• Tested in clean environment
• Tests added/updated (if applicable)

Duplicate and AI-Generated PR Check

• I have searched existing open pull requests and confirmed that no other PR already addresses this issue
• If a similar PR exists, I have explained below why this PR is a better approach
• Check if this PR was entirely AI-generated (by Copilot, Claude Code, Cursor, etc.)

---

Additional notes

Known limitations, both consistent left as-is to remain consistent with the existing Redis adapter:

• _find_keys_by_tag caps results at 1000 documents. Documented in the docstring.
• keyword_search does not escape FT.SEARCH special characters. Documented in the docstring. Fixing this properly means changing both Redis and Valkey together, better as a separate PR.

[github-actions]

PR Triage

Missing issue link: Please link the issue this PR addresses using fixes #<issue_number>, closes #<issue_number>, or resolves #<issue_number> in the PR description. If there is no existing issue, please create one first.

[github-actions]

This pull request has been automatically marked as stale due to 14 days of inactivity. If this is still relevant, please update it or leave a comment.

[edlng]

Unmarking as stale.

[edlng]

Hey @kausmeows , could you take a quick look at this PR?

[edlng]

Hey @kausmeows , could you take a quick look at this PR?

[harshsinha03]

Hey @edlng closing this in favor of #8141. It'll go out in the next release. Thanks for using Agno!