agent-ui
A modern chat interface for AI agents built with Next.js, Tailwind CSS, and TypeScript.
Could not verifysource: GitHubhomepageTypeScriptMITcommit 6dad9593fca6
TypeScript, MIT licensed. The project labels itself: agent, agno, ai, chat and self hosted.
Argusic could not get agent-ui running. An Argusic agent installed it in 2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Build and typecheck pass cleanly, production server answers HTTP 200 on all routes.
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 80 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.
- pnpm not found in system2 minutes
- pnpm install blocked by build policy for sharp1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- curl -s -o /dev/null -w %{http_code} http://localhost:3000 returned 200
- Model tokens used
- 36,435
- Exact commit tested
- 6dad9593fca6
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Here's the complete report. **Install**: `pnpm` was not pre-installed. Installed it via `npm install -g pnpm` (no root needed, … **Build**: `pnpm build` compiled successfully — all routes static, 0 errors, 0 warnings. TypeScript… **Launch**: `pnpm start` (Next.js production server) started on port 3000. `curl -s -o /dev/null -w… **Verification**: The app is a client-side chat UI that connects to user-hosted AgentOS instances. … tokens used 36,435 Here's the complete report. **Install**: `pnpm` was not pre-installed. Installed it via `npm install -g pnpm` (no root needed, … **Build**: `pnpm build` compiled successfully — all routes static, 0 errors, 0 warnings. TypeScript… **Launch**: `pnpm start` (Next.js production server) started on port 3000. `curl -s -o /dev/null -w… **Verification**: The app is a client-side chat UI that connects to user-hosted AgentOS instances. …
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 2 minutes, faster than the median of the 70 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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
- An agent with no time limit did not get it running.
Of the 71 agent projects Argusic has installed and timed, agent-ui was the 16th fastest to reach a running state, and 48 of 71 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Unverified | 80.00 | 0.03 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.02 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/agent-ui)Questions
- Does agent-ui run?
- Argusic could not verify that agent-ui runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test agent-ui?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6dad9593fca6. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test agent-ui?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does agent-ui take to install?
- 2 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 agent-ui need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing agent-ui?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does agent-ui compare with the alternatives?
- Of the 71 agent projects Argusic has installed and timed, agent-ui was the 16th fastest to reach a running state, and 48 of 71 reached one at all.
- Where is the evidence for agent-ui?
- 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.