Skip to Content
Introduction
VulpineOS

VulpineOS

Operate browser agents on a hardened Firefox-based runtime with real operator controls, remote access, and a public extension surface for optional providers.

Engine-level guarantees
Injection filtering, action lock, optimized DOM export, trust warming
Operator surfaces
Web panel, TUI workbench, remote control plane, MCP browser tools
Extension seams
Credentials, audio, mobile bridge, visual labels, and no-op public fallbacks

What Ships Now

SurfaceWhat it is
VulpineOSPublic browser-agent runtime with Vulpine browser orchestration, web panel, TUI, remote server, and MCP tools
FoxbridgePublic CDP-to-Firefox bridge for CDP clients
Vulpine MarkPublic set-of-mark labeling for visual browser workflows
MobileBridge for AndroidPublic Android device discovery and session control

Why VulpineOS Exists

Most browser-agent stacks still fail on three basic problems:

  1. Hidden prompt-injection content reaches the model.
  2. The page mutates between read and action.
  3. The model burns too much context on low-value browser structure.

VulpineOS handles those problems inside the browser/runtime itself:

LayerPurpose
Injection-Proof FilterRemoves hidden or non-visible content before it reaches the agent
Action LockFreezes the page while the agent is deciding
Optimized DOM ExportCompresses browser state into lower-token semantic output
Trust WarmingBuilds stronger browser trust over time for long-lived identities

Operator Stack

The runtime is not just a browser fork. It ships with the surfaces needed to run agents as an actual system:

SurfaceWhat it covers
Web PanelFleet view, agent sessions, approvals, proxies, contexts, logs, scripts, security, settings
TUI WorkbenchSSH-friendly operator view with live conversations, contexts, and browser state
Remote AccessServed web panel and remote TUI control over the same runtime
MCP Browser Tools38 tools for browser control, reliability checks, realism, screenshots, audio, and mobile workflows
FoxbridgeCDP bridge so compatible clients can drive the same Vulpine browser runtime
VulpineOS operator panel

Open Runtime, Extension Surfaces

The runtime and tool interfaces are public. Optional integrations attach behind stable provider interfaces; public builds return clear unavailable responses when a provider is not attached.

See Source Availability for the exact public-source boundary.

Quick Start

curl -fsSL https://vulpineos.com/install | bash vulpineos

Use vulpineos serve when you need a remote control plane, and vulpineos remote --url http://host:8443 --api-key KEY to connect from another machine.

Last updated on