Product · Web panel

Operator console, embedded in the binary.

Twelve pages of operator UI compiled into the runtime. Spawn agents, watch conversations, inspect contexts, manage proxies, check security status, edit webhooks, run scripts, audit logs — all from a localhost web panel that needs no separate deploy.

Embedded React SPA48 control messagesWebSocket auth

What's on the panel

Twelve routes ship with the binary: Dashboard, Agents, Agent Detail, Bus, Contexts, Proxies, Security, Webhooks, Scripts, Settings, Logs, and Login. The Agent Detail view splits into separate Conversation, Action Trace, Raw Session Log, Recording, and Fingerprint tabs so operator-visible activity stays separate from sensitive action payloads.

Live agent status

WebSocket subscriptions to Vulpine.agentStatus and Vulpine.conversation events. Bulk pause/resume/kill.

Trace classification

Trace rows labelled RUN, OK, PARTIAL, TIMEOUT, FAIL, THINK, or WARN — no more flat 'system' badge.

Raw log redaction

Provider hidden-reasoning, signatures, bearer fragments, secrets, cookies, credential URLs all masked.

Sidebar runtime context

Live route, browser mode, gateway state, agent count visible across every page.

Auth

The panel validates access via /auth/check, keeps the access key only for the current browser session, and authenticates the agent-events WebSocket with an access subprotocol — not a tokenised URL — so keys never end up in browser history or referer logs.

Resources

Architecture deep-dive
docs.vulpineos.com/architecture — every patch, where it lives, and why.
VulpineOS source
github.com/VulpineOS/VulpineOS — runtime, patches, additions.

Self-host the runtime today.

Pull the source, build the binary, and drive your first agent. The waitlist gates the managed runtime; the open-source path is open now.

Read the docs→Star on GitHub