Mushegh

An open-source, voice-first assistant

Self-hosted, and it orchestrates: it plans, delegates, decides, and manages the day. Connected device execution, bounded background work, and a private operational HUD.

He plans and delegates

Mushegh frames the task, breaks it down, decides what matters now, and hands each piece to the agent that should hold it. See architecture.

He is a live copilot

Voice in, sentence out, with the day managed around what you are actually doing. See the voice pipeline and phones.

He does not write the code

Every kind of engineering work is Bagadata's. Mushegh frames it; Bagadata plans it and his council does it. See the fleet.

He is checked, not trusted

Every action passes the authorisation plane, and every physical action passes the interlock at the actuator. See security.

What Mushegh actually is

He is the head of the system. Not a component in it — the thing that decides what the system does next. He plans, decomposes, delegates, follows up, and is responsible for the day-to-day: what is scheduled, what needs saying, what can wait. He runs on a Python brain with device-side edge processes for audio and laptop operations, behind a private gateway that serves the HUD and the phone route.

His own remit stops at engineering. Code, frontend, backend, database, and every kind of engineering work goes to Bagadata, because that is a different job with a different shape: it needs a room full of opinions that argue before they commit, and a senior who holds the plan together while they work.

The fleet at a glance

Four agents live in this process and are reached by an in-process call — the fastest transport there is, and the only one that cannot lose context in serialisation. They share one interface with the eighteen remote workers, so Mushegh addresses all of them the same way. How the fleet works.

Bagadata

The development agent

Every kind of engineering work goes here. Bagadata expands the brief, runs the council of coding CLIs in a room where they argue, compiles the master plan, assigns each step to the seat that should do it, and follows it through to a verified result.

Hasan-Jalal

The authorisation plane

Whether an action is allowed, decided before it happens, for every actor including Mushegh. He tracks everything his hands can reach, and he is the one agent that keeps working whatever else is happening.

Hugh

Custody of the house

The physical side. His interlock is checked at the actuator itself, a ceiling is refused rather than assumed infinite, and the E-Stop cannot be cleared in software.

Artaxias

The protocol desk

The standing procedures — the goodnight ritual, the drills, the backups — and a library of read-only maintenance probes that report the state of this machine on request.

Current repository inventory

Voice, information and consent

The iPhone route sends spoken requests to the brain and plays sentence replies. Supported tools can reach connected laptop or host executors. Camera viewing is live-only in the current setup. Presence observations use source timestamps and explicit uncertainty.

The HUD primarily shows information. Its E.D.I.T.H. approval workspace is the explicit exception: the owner can review the exact pending action and choose Accept or Reject through a separate protected API. Other panels do not become general operational controls.

Declared is not live. A subsystem that is declared, a seat whose CLI is installed, a tool in the registry, a credential in the environment and a provider that answers are five different facts, and this site keeps them apart. Everything here is written from the repository; it describes what the code says, and it does not connect to your private services.

Start with one verified path

Follow Quick start, inspect configuration, then validate voice, source freshness and device routing on your actual deployment. Cloud providers and integrations require their own configuration; self-hosting does not make external calls local.