textbee
Open-source SMS gateway. Turn your Android phone into an SMS API: send and receive SMS from your apps over REST and webhooks. Self-hostable, with a free hosted plan.
Runssource: GitHubhomepageTypeScriptMITcommit 454e59e4d059
TypeScript, MIT licensed. The project labels itself: android, android sms, android sms gateway, android sms sender, api, foss, gateway and mcp server.
textbee runs. An Argusic agent installed it in 10 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The textbee.dev monorepo builds and runs: API (NestJS) compiles and initializes all modules; Web (Next.js) builds all routes; all 67 API test suites (1478 tests) and all 49 web test files (428 tests) pass.
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.
- API billing webhook tests fail: globalThis.crypto.subtle undefined in ts-jest (polar-sdk v1.0.0 requires Node>=22)5 minutes
- Web postcss tailwindcss native binding missing (requires Node>=20)3 minutes
- pnpm binary not in PATH1 minute
- Next.js web build requires Node>=20.9.0 (system has 18.19.1)1 minute
- API NestJS build does not copy mail template assets to dist1 minute
- Install time
- 10 minutes
- Cold machine to finish
- 24 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- cd api && pnpm test -> 67 suites, 1478 passed. cd web && pnpm test -> 49 files, 428 passed. cd api && node dist/src/main.js -> Nest initializes all modules. cd web && pnpm build -> Next.js builds 75 static/dynamic routes.
- Model tokens used
- 223,718
- Exact commit tested
- 454e59e4d059
- 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.
Test Files 49 passed (49)
Tests 428 passed (428)
Start at 07:39:11
Duration 33.68s (transform 2.00s, setup 17.09s, collect 11.30s, tests 28.46s, environment 27.78…
Both test suites pass completely. Let me compile the final result.
exec
/bin/sh -lc 'cd /work/repo && export PATH="/tmp/node-v20.9.0-linux-x64/bin:/home/runner/.local/bin:…
succeeded in 134ms:
ERR_PNPM_NO_IMPORTER_MANIFEST_FOUND No package.json (or package.yaml, or package.json5) was found…
EXIT: 1
tokens used
223,718Replay 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 5 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 10 minutes to install, slower than the median of the 25 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 26 android projects Argusic has installed and timed, textbee was the 15th fastest to reach a running state, and 19 of 26 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.
- A quick evaluation: it was running 10 minutes after the clone.
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)
androidandroid-smsandroid-sms-gatewayandroid-sms-senderapifossgatewaymcp-serveropen-sourceself-hostedsend-smssimsmssms-apisms-gatewaysms-sendertext-messagetwilio-alternativewebhooks
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/textbee)Questions
- Does textbee run?
- Yes. textbee runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test textbee?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 454e59e4d059. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test textbee?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does textbee take to install?
- 10 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 textbee need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing textbee?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does textbee compare with the alternatives?
- Of the 26 android projects Argusic has installed and timed, textbee was the 15th fastest to reach a running state, and 19 of 26 reached one at all.
- Where is the evidence for textbee?
- 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.