waha
WAHA - WhatsApp HTTP API (REST API) that you can configure in a click! Multiple engines: WEBJS (browser based), NOWEB (websocket nodejs), GOWS (websocket go), WPP (browser)
Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit 55a7d78e3fea
TypeScript, Apache-2.0 licensed. The project labels itself: ai bot, bot, http api, mcp, mcp server, mcp whatsapp, python bot and whatsapp.
waha runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 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 project builds, all 308 unit tests pass across 31 suites, and the server starts and responds to HTTP API calls (GET /api/sessions returns [] with 200 status, logged 'Nest application successfully started' and 'WhatsApp HTTP API is running on: http://[::1]:3000').
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 92 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.
- 2 unit tests in PhoneNumbersCacheRepository.test.ts failed: knex+sqlite3 Date handling inconsistency — stores epoch ms as number for onConflict merge but Date.toISOString() string for plain insert, causing TTL comparison to always pass and new Date() to produce NaN15 minutes
- 2 test suites (PixMessage, message.ack.utils) fail to load: @adiwajshing/baileys is ESM-only, Jest won't transform it through transformIgnorePatterns8 minutes
- Node.js v18 installed, project requires v22+ (v24 per .nvmrc)5 minutes
- Yarn 3 shipped by corepack, project needs yarn 4.17.1 for berry PnP compatibility5 minutes
- dist/vendor/esm.js compiled await import() to require() which cannot load ESM Baileys5 minutes
- 8 unit tests in session.abc.test.ts failed: buildSession() missing media config parameter2 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 62 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- yarn test:unit exited 0, 31 suites, 308 passed, 2 skipped; curl -H 'X-API-Key: 666' http://localhost:3000/api/sessions returned [] (200) confirming the server is alive
- Model tokens used
- 270,633
- Exact commit tested
- 55a7d78e3fea
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 0ms: Install started: 13:16, Current: 14:16, Elapsed: ~60 min Now I have all the data needed. Let me compile the final ARGUSIC_RESULT: exec /bin/sh -lc 'kill %1 2>/dev/null; kill 3484 2>/dev/null; kill 3605 2>/dev/null; true' in /work/repo succeeded in 0ms: Now I have everything. Let me compile the final report. 2026-09-28T14:17:58.413448Z ERROR codex_core::session: failed to record rollout items: thread 01a0e… 2026-09-28T14:17:58.413510Z ERROR codex_core::session: failed to record rollout items: thread 01a0e… tokens used 270,633 Now I have everything. Let me compile the final report.
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 15 minutes.
- Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
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.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.29 |
Topics (from GitHub)
ai-botbothttp-apimcpmcp-servermcp-whatsapppython-botwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-chatwhatsapp-mcpwhatsapp-webwhatsapp-web-api
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/waha)Questions
- Does waha run?
- waha runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test waha?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 55a7d78e3fea. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test waha?
- The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does waha take to install?
- 15 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 waha need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing waha?
- 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.
- Where is the evidence for waha?
- 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.