better-chatbot

Formerly Better Chatbot. Navigator is an open-source AI workspace for agents, MCP and workflow automation.

Runs with mockssource: GitHubhomepageTypeScriptMITcommit 9c9ed86fd54d

TypeScript, MIT licensed. The project labels itself: agent, ai, ai chatbot, automation, chatbot, claude, gemini and low code.

better-chatbot runs, with stand-ins for the services it depends on. An Argusic agent installed it in 11 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Install succeeds, build succeeds, all 38 unit test files pass (405 tests), dev server launches and returns HTTP 200 on /sign-in and / with redirect; PostgreSQL unavailable so auth/chat features require a running Postgres instance.

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

At a glance

verdict
Runs with mocks
Argusic Score
56 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
2
last tested
stars
1,196
forks
349
open issues
57
watchers
27
size
32 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 better-chatbot, 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.

  • Next.js 16 requires Node.js >=20.9.0, system has v18.19.12 minutes
  • Dev server instrumentation.ts calls process.exit(1) on DB migration failure, preventing launch without PostgreSQL2 minutes
  • pnpm not found in PATH1 minute
  • No PostgreSQL in container (no root, no Docker)
Install time
11 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
pnpm test exited 0 (38/38 files, 405/405 tests passed); curl -s -o /dev/null -w '%{http_code}' http://localhost:3000/sign-in returned 200; pnpm build completed with all routes listed
Model tokens used
101,707
Exact commit tested
9c9ed86fd54d
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
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

- **No PostgreSQL available** — no root to install, no Docker; app gracefully degrades
- **BETTER_AUTH_SECRET too short** — used a 36-char secret
tokens used
101,707
All verified.
**38 test files passed (405 tests total). Build succeeds. Dev server launches and returns HTTP 200 …
Summary of issues found and fixed:
- **pnpm not found** — installed via npm
- **Node.js 18 too old for Next.js 16** — downloaded Node.js 20.19.1 as drop-in
- **DB migration kills startup** — patched `instrumentation.ts` to warn instead of `process.exit(1)`
- **No PostgreSQL available** — no root to install, no Docker; app gracefully degrades
- **BETTER_AUTH_SECRET too short** — used a 36-char secret

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

  • Recovered from all 4 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

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 11 minutes to install, slower than the median of the 140 comparable projects Argusic has measured.

Of the 141 agent projects Argusic has installed and timed, better-chatbot was the 94th fastest to reach a running state, and 94 of 141 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Did not run20.000.12
Argusic Runner1/3Runs with mocks92.000.06

Topics (from GitHub)

agentaiai-chatbotautomationchatbotclaudegeminilow-codemcpmcp-clientmcp-servernextjsollamaopenaiopenai-realtimeuivercelvoice-aiweb-uiworkflow

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/better-chatbot.svg)](https://argusic.com/subject/better-chatbot)

Questions

Does better-chatbot run?
better-chatbot runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 11 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test better-chatbot?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9c9ed86fd54d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test better-chatbot?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does better-chatbot take to install?
11 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 better-chatbot need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing better-chatbot?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does better-chatbot compare with the alternatives?
Of the 141 agent projects Argusic has installed and timed, better-chatbot was the 94th fastest to reach a running state, and 94 of 141 reached one at all.
Where is the evidence for better-chatbot?
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