Yuxi

可私有部署的多租户知识智能体平台:统一 RAG、知识图谱、多智能体、MCP/Skills、沙盒与权限管理。Yuxi = Cloud Agents + Knowledge RAG, Self-hosted knowledge agent platform for RAG, knowledge graphs and multi-agent workflows.

Runssource: GitHubhomepagePythonMITcommit bd07ab4ac4fa

Python, MIT licensed. The project labels itself: agentic rag, ai agents, deepagents, docker, document ai, fastapi, harness and kbqa.

Yuxi runs. An Argusic agent installed it in 34 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

1640 backend unit tests pass on Python 3.12 with uv, after installing system X11 library stubs and adding test/__init__.py for import resolution.

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.28 (measured)
recorded runs
2
last tested
stars
7,161
forks
1,130
open issues
89
watchers
50
size
51 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 Yuxi, 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.

  • ImportError: `libxcb.so.1` not found — OpenCV (`cv2`) requires X11 system libraries missing from the container.10 minutes
  • ImportError: `test.live_api_cleanup` import fails because `test` resolves to Python stdlib module (a regular package) instead of the project's namespace package at `backend/test/`.5 minutes
  • 2 test failures: `test_kubernetes_storage_init_migrates_only_real_entries` and `test_runtime_identity_migration_preserves_symlink_without_following_target` assert directory mode `0o755` but get `0o775` due to container umask `0002` instead of `0022`.3 minutes
Install time
34 minutes
Cold machine to finish
40 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
Model tokens used
528,170
Exact commit tested
bd07ab4ac4fa
Container image
sha256:4c3d41857be3

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.

How the result was proved
runs before 2026-09-07 did not record the command used to check the result
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

The end of the recording

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

exec
/bin/sh -lc 'cd /work/repo/backend && export PATH="$HOME/.local/bin:$PATH" && LD_LIBRARY_PATH=/tmp/…
Let me wait for the final verification run.
 succeeded in 102012ms:
  /work/repo/backend/package/yuxi/knowledge/implementations/milvus.py:1416: PyMilvusDeprecationWarn…
    connections.disconnect(self.connection_alias)
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
================= 1640 passed, 7 warnings in 94.04s (0:01:34) ==================
All 1640 tests pass. Let me now produce the final result.
tokens used
528,170
All 1640 tests pass. Let me now produce the final result.

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

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 34 minutes.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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 mocks92.000.08
Argusic Runner2/3Runs100.000.28

Topics (from GitHub)

agentic-ragai-agentsdeepagentsdockerdocument-aifastapiharnesskbqakgqaknowledge-baseknowledge-graphlanggraphllmsmcpmilvusmulti-agentneo4jragself-hostedvue

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/Yuxi.svg)](https://argusic.com/subject/yuxi)

Questions

Does Yuxi run?
Yes. Yuxi runs. Argusic installed and launched it on a clean machine in 34 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test Yuxi?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit bd07ab4ac4fa. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Yuxi?
The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Yuxi take to install?
34 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 Yuxi need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Yuxi?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for Yuxi?
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