Foxbridge CDP Proxy
Foxbridge translates Chrome DevTools Protocol (CDP) into Firefox’s Juggler and WebDriver BiDi protocols.
📖 Full documentation at foxbridge.vulpineos.com
Repository: PopcornDev1/foxbridge
Role in VulpineOS
In VulpineOS, foxbridge runs as an embedded CDP server — not a separate process. It wraps the kernel’s Juggler client directly:
- One Camoufox process shared between TUI, MCP tools, and OpenClaw agents
- Shared browser contexts — fingerprints and cookies persist across all interfaces
- Zero overhead — no second Firefox instance
Kernel → Camoufox (single process) → Juggler pipe → juggler.Client
├── TUI (direct Juggler calls)
├── MCP server (36 tools)
└── Embedded foxbridge CDP on :9222
└── OpenClaw connects via cdpUrlTest Results
| Backend | Tests | Status |
|---|---|---|
| Juggler (Camoufox 146) | 74/74 | ✅ 100% |
| BiDi (Firefox 148) | 62/62 | ✅ 100% |
| Go unit tests | 227 | ✅ All passing |
Full Documentation
Visit foxbridge.vulpineos.com for:
- CDP domain coverage (13 real domains + 20 stubs)
- BiDi backend implementation details
- Request interception guide
- PDF generation and IO streaming
- Performance metrics
- CLI reference
- Puppeteer usage examples
- Testing guide
See also
- Foxbridge Quick Start — get started with foxbridge
- Foxbridge CDP Coverage — 13 Chrome DevTools domains
- Architecture — single-process runtime overview
Last updated on