app-ssh
Advanced SSH & Web Terminal - Home Assistant Community Apps
Could not verifysource: GitHubShellMITcommit 60a2d61b7ef1
Shell, MIT licensed. The project labels itself: addon, addons, app, apps, home assistant, home automation, homeassistant and ssh.
Argusic could not get app-ssh running. An Argusic agent installed it in 40 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
All config files validate cleanly (YAML, JSON, Dockerfile, shell scripts), Python dependencies install correctly, ttyd binary serves HTTP 200 on its web terminal endpoint, but the full add-on stack (Docker build + HA supervisor runtime) cannot be exercised in this container.
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 30 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.
- Docker not available in container - cannot build the Docker image for this HA add-on
- No test suite exists in the repository - CI is an external reusable workflow
- Cannot run sshd/ttyd stack without HA Supervisor environment (bashio, s6-overlay, SUPERVISOR_TOKEN)
- Install time
- 40 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 0 fixed with no human help
- How the result was proved
- not verified - no test suite exists and Docker image cannot be built without Docker daemon
- Model tokens used
- 243,226
- Exact commit tested
- 60a2d61b7ef1
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- The s6 service tree (init-docker, init-mosquitto, init-mysql, init-ssh, init-user → sshd, ttyd) h…
- `ttyd` binary (v1.7.7) was downloaded and tested independently — it serves HTTP 200 on `/` and re…
**What could not be done:**
- Docker is not available in this container, so the Docker image cannot be built
- No `apt-get` root access to install `openssh-server`/`tmux`/`zsh` for testing the full stack
- The add-on requires the HA Supervisor (bashio API, SUPERVISOR_TOKEN, s6-overlay) to run, which is…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": false, \"install_minutes\": …
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": false, "install_minutes": 40, "errors": [{"msg": "D…
tokens used
243,226Replay 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
- 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
- An agent with no time limit did not get it running.
- Took 40 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Hit 3 errors during setup, 3 of which were not solved.
Of the 4 addon projects Argusic has installed and timed, app-ssh was the 4th fastest to reach a running state, and 2 of 4 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 30.00 | 0.02 | |
| Argusic Runner | 1/3 | Did not run | 30.00 | 0.02 |
Topics (from GitHub)
addonaddonsappappshome-assistanthome-automationhomeassistantsshssh-server
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/app-ssh)Questions
- Does app-ssh run?
- Argusic could not verify that app-ssh runs. Argusic installed and launched it on a clean machine in 40 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test app-ssh?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 60a2d61b7ef1. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test app-ssh?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does app-ssh take to install?
- 40 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 app-ssh need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing app-ssh?
- 3 things broke in the recorded run. Each one, and the time it cost, is listed on this page.
- How does app-ssh compare with the alternatives?
- Of the 4 addon projects Argusic has installed and timed, app-ssh was the 4th fastest to reach a running state, and 2 of 4 reached one at all.
- Where is the evidence for app-ssh?
- 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.