DojoAgents
DojoAgents: Full-Market AI Copilot for Personal Investment
Runssource: GitHubPythonApache-2.0commit 9b3a9ba51084
Python, Apache-2.0 licensed.
DojoAgents runs. An Argusic agent installed it in 26 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
dojoagents 0.2.11 installed editable in /tmp/dojo-venv with all dependencies, the React dashboard frontend built by the npm/vite packaging hook, the full pytest suite passes 1772/1772 with 3 skipped, and the dashboard server runs locally and returns real data (KWEICHOW MOUTAI quote 1330.75, market overview with 7734 CN listings) on live HTTP endpoints.
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 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- test suite: 8 failures on fresh install (dojosdk 0.1.33 schema drift in sector-brief-extract list/write models + pagination, plus HuggingFace kline wire-format change)13 minutes
- system uv not installed and Node 18.19.1 too old for Vite 8 build hook1 minute
- dashboard /health route returns 404 (no such route in this app)1 minute
- Install time
- 26 minutes
- Cold machine to finish
- 23 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest -q exited 0 with 1772 passed, 3 skipped; dojoagents dashboard --host 127.0.0.1 --port 8765 answered 200 on /, /api/v1/market/overview, /api/v1/ticker/quote?ticker=600519.SS, /api/v1/portfolio with real market data, then was stopped cleanly
- Model tokens used
- 1,987,612
- Exact commit tested
- 9b3a9ba51084
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Launch (real)** — `dojoagents dashboard --host 127.0.0.1 --port 8765` started, "Uvicorn running o… - `GET /` → 200 (SPA) - `GET /api/v1/market/overview` → 200 with real data (cn listed_count 7734, weighted_pe 15.65) - `GET /api/v1/ticker/quote?ticker=600519.SS` → 200 live quote (KWEICHOW MOUTAI last_price 1330.75) - `GET /api/v1/utility/search/company-ticker?q=600519` → 200 - `GET /api/v1/utility/market-data-revision` → 200 revision JSON - `GET /api/v1/portfolio` → 200 seeded portfolios - stopped cleanly afterwards. **Notes** - `test_asyncio_boundaries.py` passes 4/4; the `.agents/scripts/audit_asyncio_usage.py` referenced … - No third-party keys were needed for this run (data_mode=offline uses the local DojoSDK snapshot f… - `/health` doesn't exist in this app (404) — root `/` and the API routes above are the real checks.
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.
- 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 26 minutes to install, slower than the median of the 43 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 44 Python projects Argusic has installed and timed, DojoAgents was the 44th fastest to reach a running state, and 23 of 44 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/dojoagents)Questions
- Does DojoAgents run?
- Yes. DojoAgents runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test DojoAgents?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9b3a9ba51084. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test DojoAgents?
- The run that produced this verdict cost $0.40: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does DojoAgents take to install?
- 26 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 DojoAgents need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing DojoAgents?
- 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.
- How does DojoAgents compare with the alternatives?
- Of the 44 Python projects Argusic has installed and timed, DojoAgents was the 44th fastest to reach a running state, and 23 of 44 reached one at all.
- Where is the evidence for DojoAgents?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.