Skip to content
Vulpine
Esc
↑↓navigate↵open⌘Jpreview
On this page

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.

Plug in your own

Every replaceable part is a hardpoint: a typed slot, the implementation you bind into it, and its qualification.

Look something up

The reference is generated from the code, so it is the place to check a name.

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

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.

Was this page helpful?