redis-vl-python

Redis Vector Library. The AI-native Python client for Redis.

Runs with mockssource: GitHubhomepagePythonMITcommit 8bb2f69e6a6d

Python, MIT licensed. The project labels itself: anthropic, embedding, huggingface, large language models, llm, llmcache, mcp and openai.

redis-vl-python runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.5 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.

redisvl 0.27.2 installed in a venv with all unit tests passing (1619/27skipped), CLI responding correctly, and optional dependencies for MCP, HF, GoogleGenAI, and AzureOpenAI vectorizers resolved.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 54 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
54 / 100
cost of the verifying run
$0.10 (measured)
recorded runs
2
last tested
stars
436
forks
125
open issues
48
watchers
10
size
88 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing redis-vl-python, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Missing sentence-transformers dependency for HFTextVectorizer0.5 minutes
  • Missing google-genai dependency for GoogleGenAIVectorizer0.3 minutes
  • Missing fastmcp dependency for MCP tests0.3 minutes
  • Missing pydantic-settings dependency for MCP module0.2 minutes
  • 6 CLI unit tests require redis_url fixture (Docker Redis needed)
Install time
under a minute
Cold machine to finish
19 minutes
Errors hit and fixed
5 hit, 4 fixed with no human help
How the result was proved
python -m pytest tests/unit/ --noconftest --tb=no -q -k 'not test_listall_json and not test_info_json and not test_index_human_output and not test_stats_json and not test_stats_table' exited 0 with 1619 passed, 27 skipped; rvl version returned 'RedisVL version 0.27.2'; rvl --help printed expected output
Model tokens used
705,195
Exact commit tested
8bb2f69e6a6d
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- Missing extras found during testing: `pydantic-settings`, `fastmcp`, `sentence-transformers`, `go…
- No Docker or Redis server available in the container
**Test phase (1619 passed, 27 skipped, 0 failed):**
- Unit tests excluding 6 CLI tests needing `redis_url` (needs Docker Redis) and 1 repr test needing…
- MCP unit tests: **376 passed**
- GoogleGenAI vectorizer tests: **31 passed**
- Azure Argusic vectorizer tests: **36 passed, 1 skipped**
- CL tool help/version: all work (`rvl version` → 0.27.2)
**Remaining gaps (no fix possible without Docker):**
- 6 CLI tests need `redis_url` fixture (requires running Redis)
- Integration tests need Docker Compose (testcontainers)
- HF model download test times out in constrained environment

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 0.5 minutes, faster than the median of the 9 comparable projects Argusic has measured.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Hit 5 errors during setup, 1 of which were not solved.

Of the 10 anthropic projects Argusic has installed and timed, redis-vl-python was the 1st fastest to reach a running state, and 5 of 10 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks88.000.10
Argusic Runner1/3Did not run20.000.13

Topics (from GitHub)

anthropicembeddinghuggingfacelarge-language-modelsllmllmcachemcpopenaipythonredisredis-searchretrieval-augmented-generationsearchsemantic-cachevector-databasevector-search

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/redis-vl-python.svg)](https://argusic.com/subject/redis-vl-python)

Questions

Does redis-vl-python run?
redis-vl-python runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test redis-vl-python?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8bb2f69e6a6d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test redis-vl-python?
The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does redis-vl-python take to install?
0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does redis-vl-python need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing redis-vl-python?
5 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does redis-vl-python compare with the alternatives?
Of the 10 anthropic projects Argusic has installed and timed, redis-vl-python was the 1st fastest to reach a running state, and 5 of 10 reached one at all.
Where is the evidence for redis-vl-python?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion