LiveAgent
A fully functional AI Agent desktop client that supports Webui access and can be creatively customized and expanded!
Runssource: GitHubTypeScriptMITcommit a41515366d7e
TypeScript, MIT licensed. The project labels itself: ai agents, ai tools, claude code, claude desktop, codex, codex app, desktop app and fable.
LiveAgent runs. An Argusic agent installed it in 28 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Go gateway binary (agent-gateway / cmd/gateway) builds, starts on port 50052, and returns 200 on /api/status with proper Bearer auth; all Go tests pass; Node script tests (30/30), virtual-core tests (34/34), and GUI release backend tests pass; the desktop GUI (Tauri) cannot build due to missing system libraries (gobject-2.0) and OOM at 2GB during Vite/rolldown production bundle.
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.
- Vite build (pnpm build:gui and pnpm build:webui) OOM killed (exit 137) on 2GB container during rolldown chunking10 minutes
- Rust cargo check fails: missing system library gobject-2.0 (gobject-sys crate) — Tauri/WebKit dependency3 minutes
- Node.js 18.19.1 is too old for Vite 8 (requires 20.19+ or 22.12+)2 minutes
- pnpm not available on system PATH2 minutes
- Native binding @rolldown/binding-linux-x64-gnu missing after first pnpm install1 minute
- Go gateway build requires web/dist for embedded assets — not built due to Vite OOM1 minute
- Install time
- 28 minutes
- Cold machine to finish
- 32 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- /tmp/gateway -http-addr :50052 -token dev-token -agent-db /tmp/gateway-test.db started and curl -v -H 'Authorization: Bearer dev-token' http://localhost:50052/api/status returned HTTP/1.1 200 OK with JSON status payload. go test ./... across 19 packages: 18 passed, 1 flaky test passed on retry.
- Model tokens used
- 392,477
- Exact commit tested
- a41515366d7e
- 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.
/bin/sh -lc 'kill %1 2>/dev/null; pkill gateway 2>/dev/null; echo "Cleanup done"' in /work/repo succeeded in 81ms: Cleanup done Let me now assemble the final report exec /bin/sh -lc 'date +%s' in /work/repo succeeded in 0ms: 1791098615 2026-10-04T07:23:56.477725Z ERROR codex_core::session: failed to record rollout items: thread 01a10… 2026-10-04T07:23:56.555779Z ERROR codex_core::session: failed to record rollout items: thread 01a10… tokens used 392,477
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 7 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 did not, or is not known
- Took 28 minutes to install, slower than the median of the 38 comparable projects Argusic has measured.
Of the 39 ai-agents projects Argusic has installed and timed, LiveAgent was the 36th fastest to reach a running state, and 28 of 39 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.08 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.11 |
Topics (from GitHub)
ai-agentsai-toolsclaude-codeclaude-desktopcodexcodex-appdesktop-appfablehermeshermes-agentmcpoepnclawopen-sourceskillstauritypescriptwebui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/liveagent)Questions
- Does LiveAgent run?
- Yes. LiveAgent runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test LiveAgent?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a41515366d7e. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test LiveAgent?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does LiveAgent take to install?
- 28 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 LiveAgent need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing LiveAgent?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does LiveAgent compare with the alternatives?
- Of the 39 ai-agents projects Argusic has installed and timed, LiveAgent was the 36th fastest to reach a running state, and 28 of 39 reached one at all.
- Where is the evidence for LiveAgent?
- 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.