Vulpine
Vulpine, a self-hosted voice runtime: how it works, how to run it, and how to extend it.
Vulpine documentationVoice runtime
- Pages
- 93
- Sections
- 7
Start here
What Vulpine is
The voice runtime around the agent you already run: what it does, what runs where, and the words it uses.
- Overview: what Vulpine is and what runs where, in one page
- Architecture: how voice, turns, speech workers and the brain fit together
- Glossary: skins, the gateway, the brain, loadouts
- Key decisions: what was decided, why, and what it means for you
- What you can say: the callsign, follow-ups and the spoken verbs
Install it
The two apps to a green doctor (or a clone, for developers), then the gateway running and a release you can roll back.
- Install: the two signed apps: the setup window runs every step to a green doctor
- Developer install: from a clone: mise, just install, each step’s checks
- Run the gateway: run it locally, find its config, roll a new version
- Release and rollback: cut a release, roll it, roll it back
Plug in your own
Every replaceable part is a hardpoint: a typed slot, the implementation you bind into it, and its qualification.
- Hardpoints: the slots, and how an implementation is bound and qualified
- Your speech recognizer: what an STT implementation must do
- Your voice and TTS: what a speech-output implementation must do
- A worked example: a TTS engine bound as the voice, start to finish
- Your agent: the brain is Pi today: the tools Vulpine gives it
- Your avatar: what a rig draws from the typed picks
- Your house: the two adapter contracts for homes, rooms and services
Look something up
The reference is generated from the code, so it is the place to check a name.
- Gateway config: every section and key of config.toml
- Every just recipe: build, roll, deploy and check
- Command lines: every CLI and its flags
- Brain tools: what the brain can call
Vulpine is a voice assistant you host yourself. The gateway runs on a Mac in the house: it hears each spoken turn, answers the requests on its own short list of verbs, and hands everything else to your agent, the brain, which runs on Pi today. You talk to it through Vulpine.app on a Mac, a browser tab or a room speaker; Vulpine Gateway.app holds the gateway and its window. You address it by its callsign, “Fox Nine”.
System mapGuided views and component paths
Open the system map full page: pick a guided view (the voice round trip, the authority boundaries, the integrations), or click a component to follow its paths.
Sections
Install and operate
What Vulpine is, Install, Developer install and 4 more.
The voice path
Architecture, Glossary, Glossary: runtime terms and 9 more.
The brain
Brain tools, Speculation tool gate, Tool policy and search and 4 more.
Frontends
Frontends overview, Vulpine in a browser, Vulpine.app, the desktop app and 8 more.
Contracts
Contracts overview, JSON Schemas, Frontend WebSocket and 39 more.
Adapters and integrations
Integrations, Home adapter, Room adapter and 4 more.
Reference
7 pages.
For agents
The site answers agents as well as people: an MCP server at /docs/mcp, every page as Markdown at its URL plus .md, and /docs/llms.txt and /docs/llms-full.txt.