phonebox
Turn an old Android phone into a customizable desk panel and touch control deck for Windows, Linux and macOS. 124 widgets and 30 templates for system stats, AI coding, media and automation, in 13 languages. USB or paired Wi-Fi. No cloud required.
Runssource: GitHubJavaScriptMITcommit 44ca501135de
JavaScript, MIT licensed. The project labels itself: android, claude code, codex, dashboard, desk panel, dotnet, home assistant and linux.
phonebox runs. An Argusic agent installed it in 10 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The PhoneBox .NET 10 agent builds, all 2013 unit tests pass, the agent starts and serves the settings page and JSON API on port 8765, and the Python demo server serves the panel and settings editor on port 8790.
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. 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.
- IPv6 is disabled at the kernel level in this container but Socket.OSSupportsIPv6 returns true, causing two ListeningPorts tests (AnIpv6OnlyListenerIsReachedOnIpv6Loopback, BothFamiliesOnOnePortAreKept) to fail with SocketException: Cannot assign requested address.3 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- dotnet test agent/PhoneBox.Agent.Tests: 2013 passed, 0 failed; dotnet run --project agent/PhoneBox.Agent -f net10.0 started, curl http://127.0.0.1:8765/ returned HTML 200; curl http://127.0.0.1:8765/api/info returned JSON with version 0.9.27; python3 tools/demo-server.py served HTTP 200 on panel and settings pages
- Model tokens used
- 58,537
- Exact commit tested
- 44ca501135de
- 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 2>/dev/null; kill %1 2>/dev/null; wait 2>/dev/null; true' in /work/repo succeeded in 0ms: Let me calculate the install time: The dotnet install started at ~00:30, and completed ~5s later. Tests ran and completed. Let me chec… exec /bin/sh -lc 'date -u +%s' in /work/repo succeeded in 0ms: 1795344166 I started work a few minutes ago. The whole process took about 10 minutes from install to verificat… tokens used 58,537 I started work a few minutes ago. The whole process took about 10 minutes from install to verificat…
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 1 error 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 10 minutes to install, slower than the median of the 30 comparable projects Argusic has measured.
Of the 31 android projects Argusic has installed and timed, phonebox was the 19th fastest to reach a running state, and 24 of 31 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)
androidclaude-codecodexdashboarddesk-paneldotnethome-assistantlinuxmacosold-phonesmart-stackstream-decksystem-monitortailscalewebhookswidgetswindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/phonebox)Questions
- Does phonebox run?
- Yes. phonebox runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test phonebox?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 44ca501135de. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test phonebox?
- 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 phonebox 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 phonebox need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing phonebox?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does phonebox compare with the alternatives?
- Of the 31 android projects Argusic has installed and timed, phonebox was the 19th fastest to reach a running state, and 24 of 31 reached one at all.
- Where is the evidence for phonebox?
- 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.