v0.1 · runs on a Raspberry Pi

A voice assistant
that lives at home.

Plug a Pi into your home network. Say a word. Talk to your lights, your music, your home. Your voice never leaves the room.

Install on a Pibash
$curl -fsSL https://sudo.abhishekslab.xyz/install.sh | bash

Fresh Raspberry Pi OS Lite (64-bit) · 5–10 minutes.

Install guideRead the docs

01 · setup

One flow.
No terminals.

Plug a monitor and keyboard into your Pi, run the one-liner, open http://localhost:3000 in a browser. The wizard installs Docker, brings up Home Assistant and the voice stack, configures MCP — no clicking through Home Assistant screens.

  • 01The one-liner installs Node, fetches the source, builds the onboarding app.
  • 02Pick a wake phrase, a color, a name for the home. Seconds, not forms.
  • 03Sudo brings up Docker, Home Assistant, whisper, piper, wakeword — all in sequence.
  • 04Creates a scoped sudo_agent HA user, mints its token, wires MCP.
  • 05Runs an end-to-end smoke test before declaring done.
journalctl · live
✓ node v20.20, git 2.39
✓ created user sudoassist
✓ source unpacked
✓ next build complete
✓ service active on :3000
Open http://<pi-ip>:3000 in a browser.

02 · inside

Every piece, local.

  mic ─► openWakeWord ─► whisper ─► voice loop ─► claude
                          (STT)          │            │
                                         ▼            ▼
                                       piper    home assistant
                                       (TTS)      via MCP
                                         ▲            │
                                         └────── actions & state

Every named piece runs in Docker on the Pi. Audio never leaves the device. Only the recognized text is sent to Claude, and only after the wake word fires.

03 · why

Small details, everywhere.

audio

Your voice stays here

Wake word, speech-to-text, and text-to-speech run on the Pi. The mic feed never reaches the internet.

control

Tools for your home

Claude gets MCP tools to read and control your lights, switches, scenes, sensors, and scripts — nothing more.

safety

Scoped access

The assistant holds a non-admin HA token. It can touch only the entities you expose. No surprises.

setup

No-click setup

One page, a few choices, and the wizard handles Docker, Home Assistant onboarding, MCP, and verification itself.

portable

Move between devices

Export an encrypted bundle; restore on a new Pi with a passphrase. Replace hardware without re-onboarding.

upgrades

Deploy = verify

Pinned images + schema migrations. If the smoke test fails after an upgrade, Sudo auto-rolls back to the last known-good.

private

Local by default

Runs entirely on your LAN. Bind to 127.0.0.1 if you prefer; expose to LAN for a phone dashboard if you don’t.

open

Open source

Fork it, self-host the tarball, run the whole stack inside your own network. No cloud lock-in.

04 · portable

Your setup, exportable.

Every install can emit a single encrypted .sudo-bundle with your secrets, voice-loop config, and Home Assistant state. Drop it on a new Pi to migrate in minutes.

Bundle formatVersioned upgrades