VulpineOS turns browser-agent loops into a managed operator runtime. Pre-configured workspace, identity vault, multi-agent orchestrator, 36-tool MCP toolbelt, and a Vulpine browser session — all wired in by default.
The agent runtime runs autonomous browser-agent loops with tool calls, session state, and a workspace tailored for web tasks.
VulpineOS adds the browser context, identity vault, MCP toolbelt, and operator controls needed to run agents in parallel against real websites.
A plain agent loop assumes a vanilla browser and a single-process workflow. VulpineOS lifts it into an operator-grade runtime.
A generated workspace with browser-tool primitives and identity-aware session prompts. No manual wiring per agent.
Compatible clients can drive Vulpine browser through Foxbridge — the same Chrome DevTools Protocol surface, but on top of a fingerprint-coherent Firefox core instead of vanilla Chrome.
Spawn, pause, resume, and manage agents from the TUI or served web panel. Sessions persist across restarts. Per-agent budgets and approval gates included.
Each agent receives a fingerprinted browser context from the vault. Cookies, fingerprints, proxies, and trust state move with the session — not with the agent process.
Each agent runs inside the VulpineOS orchestrator with a per-agent workspace config that exposes our 36-tool MCP toolbelt. When the agent decides to click or navigate, it goes through VulpineOS's MCP server, through the Juggler protocol, into a Vulpine browser session managed by the orchestrator.
Browser routing is auto-detected. With Foxbridge running, compatible CDP clients can connect to the shared Vulpine browser instance.
docs.vulpineos.com/architecture — full breakdown of the Vulpine browser / agent runtime / orchestrator path.
docs.vulpineos.com/openclaw-camoufox-setup — end-to-end install plus troubleshooting.
github.com/VulpineOS/VulpineOS — source, issues, and discussions.
Self-host the runtime today, or join the private waitlist for the managed operator layer when it opens.
