home-assistant-vibecode-agent
Home Assistant MCP server agent. Enable Claude Code, Cursor, VS Code or any MCP-enabled IDE to help you vibe-code and manage Home Assistant: create and debug automations, design dashboards, tweak themes, modify configs, and deploy changes using natural language
Runs with mockssource: GitHubhomepagePythonMITcommit d361f865b42f
Python, MIT licensed. The project labels itself: claude, claudecode, cursor ai, home assistant, home assistant addons, home automation, homeassistant and mcp server.
home-assistant-vibecode-agent runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1 minute and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
HA Vibecode Agent v2.10.48 starts, serves /api/health (200, no auth), and responds to authenticated REST API calls via a mock Home Assistant backend running on port 8123.
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.
- except Exception in app/api/hacs.py:480 caught HTTPException(400) from HACS-not-installed check and re-wrapped it as 500, causing test_json_body_is_not_query_validation_error to fail3 minutes
- httpx 1.x incompatible with starlette TestClient — pytest collection failed with TypeError: Client.__init__() got an unexpected keyword argument 'app'1 minute
- Install time
- 1 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- Launched uvicorn (port 8099) pointed at a schema-correct mock HA on port 8123 (REST API + WebSocket). curl /api/health returned 200 with JSON. curl /api/entities/list with bearer auth returned 4 entities (sensor.temperature, light.living_room, switch.kitchen, climate.thermostat). curl /api/entities/services returned 3 domains (homeassistant, light, hacs). curl /api/entities/call_service with light.turn_on returned success. curl /api/system/config returned HA config. All unauthenticated requests to protected endpoints returned 403. Swagger /docs returned 200.
- Model tokens used
- 300,320
- Exact commit tested
- d361f865b42f
- 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.
/work/repo/venv/lib/python3.12/site-packages/httpx/_client.py:690: DeprecationWarning: The 'app' …
warnings.warn(message, DeprecationWarning)
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
======================== 36 passed, 9 warnings in 0.65s ========================
Let me record the time spent and kill the servers.
exec
/bin/sh -lc "pgrep -af \"uvicorn\\|mock_ha\" | grep -v grep | awk '{print "'$1}'"' | xargs -r kill …
echo \"Cleaned up\"" in /work/repo
succeeded in 0ms:
Cleaned up
tokens used
300,320Replay 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 1 minute, faster than the median of the 8 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, 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.
Of the 9 claude projects Argusic has installed and timed, home-assistant-vibecode-agent was the 5th fastest to reach a running state, and 5 of 9 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 | 1/3 | Runs with mocks | 92.00 | 0.02 |
Topics (from GitHub)
claudeclaudecodecursor-aihome-assistanthome-assistant-addonshome-automationhomeassistantmcp-servermcp-serversvibecoding-tool
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/home-assistant-vibecode-agent)Questions
- Does home-assistant-vibecode-agent run?
- home-assistant-vibecode-agent runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test home-assistant-vibecode-agent?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d361f865b42f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test home-assistant-vibecode-agent?
- 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 home-assistant-vibecode-agent take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does home-assistant-vibecode-agent need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing home-assistant-vibecode-agent?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does home-assistant-vibecode-agent compare with the alternatives?
- Of the 9 claude projects Argusic has installed and timed, home-assistant-vibecode-agent was the 5th fastest to reach a running state, and 5 of 9 reached one at all.
- Where is the evidence for home-assistant-vibecode-agent?
- 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.