VulpineOS
Star on GitHub →
Product · Runtime

The runtime, end to end.

VulpineOS is a Vulpine browser runtime, a multi-agent orchestrator, a 36-tool MCP bridge, a web panel, a terminal workbench, and a Go runtime that ties it all together. Self-host the whole stack.

Open source · MPL 2.0Self-hostedBring your own keys
01

What it is

The runtime launches the Firefox-based Vulpine browser, attaches the Juggler automation protocol, and hands every agent an isolated browser session. Foxbridge can expose the same context to compatible CDP clients. Every browser session is identity-scoped, fingerprint-coherent, and security-hardened by four C++ patches that ship with the build.

On top of that you get a multi-agent orchestrator, a vault for persistent identities, a 36-tool MCP toolbelt, cost tracking, agent-bus policies, recordings, and a script DSL for repeatable browser tasks that don't burn LLM tokens.

01

Vulpine browser

Firefox 146.0.1 fork with four operator-grade security primitives baked into the C++ core.

02

Multi-agent orchestrator

Spawn, pause, resume, kill hundreds of agents from one process. Sessions persist across restarts.

03

Identity vault

Cookies, localStorage, fingerprints, and proxy assignments per citizen. SQLite via pure-Go modernc.

04

MCP toolbelt

36 typed browser tools exposed over Model Context Protocol. Any MCP client can drive a session.

02

How it fits together

One Vulpine browser process is shared across every operator surface, with Foxbridge bridging CDP-native clients into the same browser contexts the TUI and MCP server already see.

Kernel  →  Vulpine browser (single process)  →  Juggler pipe  →  juggler.Client
                                                          ├──  TUI  (direct Juggler calls)
                                                          ├──  MCP server  (browser tools over MCP)
                                                          └──  Foxbridge CDP server  :9222
                                                                  └──  compatible CDP clients  →  same contexts
Architecture · one Vulpine browser, many operator surfaces
03

Lifecycle

The orchestrator allocates contexts from a pre-warmed pool, applies the citizen's fingerprint, and hands the session off to the agent. When the agent finishes, the context is recycled — capped at 50 uses to avoid memory drift, monitored for per-context memory limits, and torn down with full process-group cleanup.

04

Quick start

  1. 01Clone the repo — git clone https://github.com/VulpineOS/VulpineOS.
  2. 02Build — make fetch && make setup && make dir && make build (artifact builds finish in under 5 minutes on Apple silicon).
  3. 03Run — ./vulpineos boots the orchestrator, the MCP bridge, and the TUI in one process.

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