Skip to Content
Compatibility Matrix

Compatibility Matrix

This matrix answers a different question from the domain coverage page: not just “is a method implemented?”, but “what works together in a real client/backend/browser combination?”

Browser targets

Target browserBackendStatusNotes
Camoufox / Playwright-style Firefox buildsJugglerRecommendedPrimary production path for VulpineOS
Standard Firefox 129+BiDiSupportedUses native WebDriver BiDi endpoint
Standard Firefox without usable BiDi endpointJugglerDepends on buildRequires a Juggler-capable binary

Client compatibility

Client/toolJuggler backendBiDi backendNotes
PuppeteerSupportedSupportedJuggler path has 74/74 Puppeteer tests, BiDi path has 62/62
OpenClawSupportedPartial / situationalVulpineOS embeds foxbridge primarily through the Juggler path
chrome-remote-interfaceSupportedSupportedBest for direct CDP method access
browser-use / generic CDP clientsSupportedSupportedDepends on which CDP domains they require

CDP domain status

AreaStatusNotes
TargetSupportedContexts, attachment, target lifecycle
PageSupportedNavigation, screenshots, frame tree, isolated worlds
RuntimeSupportedEvaluate, callFunctionOn, properties, object lifecycle
InputSupportedMouse, keyboard, touch
NetworkSupportedCookies, headers, interception hooks, user agent
FetchSupportedContinue, fulfill, fail, response body
EmulationSupportedViewport, UA, geolocation, timezone, locale
DOMSupportedQuery, describe, resolve, box model, focus, file inputs
AccessibilitySupportedFull AX tree
PerformanceSupportedPage timing metrics
IOSupportedPDF stream reading
ConsoleSupportedConsole event forwarding
BrowserSupportedVersion info, close, basic window APIs
Stub domainsNo-op successFor client compatibility where real behavior is not required

For exact methods, see CDP Domain Coverage.

VulpineOS-specific passthrough methods

Methodfoxbridge statusBrowser requirementNotes
Page.getOptimizedDOMForwardedVulpineOS/Camoufox build with method presentNot standard CDP
Page.resolveRefForwardedVulpineOS/Camoufox build with method presentRef-based interaction helper
Page.focusByRefForwardedVulpineOS/Camoufox build with method presentRef-based focus helper
Page.setActionLockForwardedVulpineOS/Camoufox build with method presentFreezes page execution during reasoning
Page.getShadowDOMForwardedVulpineOS/Camoufox build with method presentShadow-root inspection helper
Page.getAnnotatedScreenshotNot currently forwardedN/AUse VulpineOS MCP or direct Juggler
Page.secureSetInputValueNot currently forwardedN/APrivate/extension workflows use direct Juggler path
Browser.startAudioCaptureNot currently forwardedN/ANot exposed through foxbridge today
Browser.stopAudioCaptureNot currently forwardedN/ANot exposed through foxbridge today
Browser.getAudioChunkNot currently forwardedN/ANot exposed through foxbridge today

For examples, see VulpineOS Methods.

Version expectations

SurfaceExpected state
CDP clientChrome-oriented client expecting normal discovery endpoints
foxbridgeCurrent main / released build matching the docs site
Camoufox / VulpineOS browserMust contain the Juggler methods being forwarded
Standard FirefoxWorks through BiDi for standard CDP coverage, not VulpineOS-only passthrough methods

Known limitations

LimitationImpact
VulpineOS passthrough methods are not Chrome-standard CDPClient code must treat them as product-specific extensions
Not all Juggler methods are auto-forwardedUnsupported methods return method not found
Some domains are compatibility stubs onlyClients may connect successfully but not get real functionality for those domains
VulpineOS-specific methods depend on the target browser build, not foxbridge alonefoxbridge can only forward what the browser actually implements

See also

Last updated on