Frontends overview
The Fox9 frontends and their platform shells: the Vigil and Glyph frontend skins, the Fox9 Admin app and the Voice PE satellite bridge; `just apps::vigil-build` builds Vigil with the gateway settings baked in and `just apps::vigil-install host=<alias>` ships it to the mini's state folder.
Living doc, checked against the code 2026-11-14
The ways to talk to Vulpine, and the app that hosts it. Every frontend is a client of the gateway
(crates/voice_gateway) over the generated protocol (packages/protocol). None of them owns capture authority, brain
turns or provider credentials: the gateway does. Read this page first; each row links the page that says more.
The frontends
| what you use | what it is | state | its page |
|---|---|---|---|
| Vulpine.app on the Mac | The desktop app (apps/glyph, bundle id com.voidfab.vulpine). It draws in the Glyph look: an ambient overlay beside your work, with a conversation window that slides in. |
ships | Vulpine.app, the desktop app and its design principles |
| Vulpine in a browser | The web app (apps/vigil), drawn in the Vigil look: a fullscreen or second-screen page with its frames, portraits and a transcript drawer. The gateway host serves the built page on its loopback (runtime/vigil-serve). |
ships | the frontend interfaces |
| A room speaker | A Voice PE puck in a room, bridged to the gateway by apps/satellite-esphome: one process per device, ESPHome’s native API on one side and an ordinary protocol client on the other. |
ships | Room speaker |
| Vulpine on iPhone | The iOS app (apps/phone), a GPUI app over the Rust Client Core (crates/phone_core): hold to talk, typed lines, Siri and Shortcuts. |
in development | Vulpine on iPhone |
| The terminal frontend | A text-only client (apps/tui) for a terminal over SSH or Mosh: the voice rows, the transcript and the brain’s ask-back dialogs. It runs from a checkout. |
ships | Terminal frontend |
| Vulpine Gateway.app on the gateway host | The host app (apps/admin-shadow): it holds the gateway, and its window, the Gateway window, shows what the gateway is doing and asks before every change. |
ships | Vulpine Gateway.app and the Gateway window |
Vulpine.app and Vulpine in a browser share the browser-clean Client Core (packages/voice-client) and the voice
chrome (packages/vulpine-voice-ui). The landing page is apps/site (the Vulpine site).
Run and test
- Vulpine in a browser:
just dev(its Vite dev server),just apps::vigil-devagainst the gateway relay on :8780,just apps::vigil-showcase(every frame on a scripted call, no gateway),just typecheck. - Vulpine in a browser, built and shipped:
just apps::vigil-buildtypechecks and builds the gitignored dist folder with the gateway workspace baked in (the absolutecatalog/agents/operatorpath on the gateway’s host; the build refuses a bundle without it) and stamps it (vigil-build.json,MANIFEST.sha256). The build has three pages: the app,/tour.htmland/showcase.html.just previewserves it on this machine.just apps::vigil-install [host] [clips=<folder>] [--dry-run]ships it to~/.local/state/vulpine/vigilon the gateway host, keeping the old one asvigil.previous; withclips=it also ships the fox’s clip folder to~/.local/state/vulpine/clips/<name>.just apps::vigil-serve-install [host] [--dry-run]serves the build on the gateway host’s loopback, 127.0.0.1:8794, as the launchd jobcom.voidfab.vulpine.vigil(runtime/vigil-serve), andjust apps::vigil-serve-smokechecks it. - Vulpine.app:
just glyph-dev(the Tauri shell, mic off until enabled),just glyph-typecheck,just glyph-build,just glyph-tauri-check,just glyph-showcase. - Vulpine Gateway.app:
just apps::admin-install [host]. - The terminal frontend:
just apps::tui, orbun apps/tui/src/main.ts --gateway <ws url>;bun run --cwd apps/tui typecheck,bun test apps/tui/tests(headless, against a loopback fake gateway).
See also
- The frontend interfaces: the skins, the Client Core and the Visual Themes.
- The Gateway window: what the host app’s window shows.
- The glossary for Frontend Skin, Shell, Visual Theme and Client Core.