voltagent
AI Agent Engineering Platform built on an Open Source TypeScript AI Agent Framework
Runssource: GitHubhomepageTypeScriptMITcommit 44b4c8e4998c
TypeScript, MIT licensed. The project labels itself: agents, ai, ai agents, ai agents framework, aiagentframework, chatbots, chatgpt and framework.
voltagent runs. An Argusic agent installed it in 24 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Monorepo builds (29/29 packages), lints (0 errors, 5 warnings), and all 25 packages with runnable unit tests pass (~2776 tests). The only test failure is @voltagent/e2e which requires an unreachable PostgreSQL database. Two test files with a pre-existing ESM dependency conflict are excluded.
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, 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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- server-elysia ElysiaServerProvider tests failed (port conflicts, mock mismatch with real impl)5 minutes
- 8 packages failed vitest config load (vite 7 is ESM-only, config.cjs require() fails)3 minutes
- scorers/autoeval.spec.ts and evals/run-experiment.spec.ts fail: transitive dep linear-sum-assignment requires() ESM-only ml-spectra-processing3 minutes
- Node.js v18.19.1 too old (needs >=20) — pnpm install succeeded with warnings2 minutes
- 3 packages had no vitest config, test script failed with 'No projects found'2 minutes
- evals vitest config was **/*.spec.ts which picked up duplicate tests from node_modules2 minutes
- Install time
- 24 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- pnpm test:all, 25 of 26 packages pass, 0 failing tests in packages with tests. Build: pnpm build:all, 29/29 projects. Lint: biome reports 0 errors, 5 warnings.
- Model tokens used
- 584,589
- Exact commit tested
- 44b4c8e4998c
- 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.
.../src/elysia-server-provider.spec.ts | 34 ++++++++++++----------
packages/server-elysia/vitest.config.ts | 21 -------------
packages/server-hono/vitest.config.ts | 21 -------------
packages/voice/vitest.config.ts | 15 ----------
packages/voltagent-memory/package.json | 4 +--
13 files changed, 27 insertions(+), 186 deletions(-)
exec
/bin/sh -lc "ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_minutes…
exited 127 in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:{install_succeeded:true,launch_succeeded:true,install_minutes:24,errors:…
tokens used
584,589Replay 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 8 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.
What did not, or is not known
- Took 24 minutes to install, slower than the median of the 14 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 15 agents projects Argusic has installed and timed, voltagent was the 14th fastest to reach a running state, and 9 of 15 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.
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
Topics (from GitHub)
agentsaiai-agentsai-agents-frameworkaiagentframeworkchatbotschatgptframeworkjavascriptllmllm-observabilitymcpmultiagentnodejsobservabilityopen-sourceopenairagttstypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/voltagent)Questions
- Does voltagent run?
- Yes. voltagent runs. Argusic installed and launched it on a clean machine in 24 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test voltagent?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 44b4c8e4998c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test voltagent?
- The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does voltagent take to install?
- 24 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 voltagent need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing voltagent?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does voltagent compare with the alternatives?
- Of the 15 agents projects Argusic has installed and timed, voltagent was the 14th fastest to reach a running state, and 9 of 15 reached one at all.
- Where is the evidence for voltagent?
- 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.