Source Availability
VulpineOS keeps the public repository focused on the open runtime: browser orchestration, operator interfaces, MCP tools, and stable extension interfaces. Optional providers can attach behind those interfaces without changing the public tool contract.
Open Source
| Component | Repository | What Is Public |
|---|---|---|
| VulpineOS | VulpineOS/VulpineOS | Browser runtime, MCP server, web panel, TUI, Juggler bindings, no-op extension interfaces |
| Vulpine Mark | VulpineOS/vulpine-mark | Set-of-Mark screenshots, visual element labels, JSON/SVG output, click/type/hover by label |
| MobileBridge for Android | VulpineOS/mobilebridge | Android ADB/CDP bridge, device listing, gestures, attached server, reconnect handling |
| Foxbridge | VulpineOS/foxbridge | CDP-to-Firefox proxy and protocol forwarding for compatible clients |
| Docs | VulpineOS/vulpineos-docs | Product docs, setup guides, and public project documentation |
Extension Boundary
Public VulpineOS builds expose stable extension interfaces. If no provider is registered, the corresponding tool returns a clear unavailable response instead of pretending a feature exists.
| Capability | Public Surface |
|---|---|
| Credential workflows | vulpine_get_credential, vulpine_autofill |
| Audio workflows | vulpine_start_audio_capture, vulpine_stop_audio_capture, vulpine_read_audio_chunk |
| Mobile workflows | vulpine_list_mobile_devices, vulpine_connect_mobile_device, vulpine_disconnect_mobile_device |
| Visual workflows | vulpine_annotated_screenshot, vulpine_click_label |
The public repository includes the interfaces, no-op fallbacks, operator status surfaces, and tests for graceful degradation. Provider implementations, private deployment wiring, and unreleased product details do not belong in public repos.
Browser Patch Boundary
The public source includes the browser patches needed for the released open runtime. Sensitive private experiments, detector notes, internal plan docs, and unreleased browser research should stay out of public history.
| Allowed Publicly | Kept Private |
|---|---|
| Stable public protocol/tool names | Private provider implementations |
| No-op extension interfaces | Private build wiring and credentials |
| High-level user-facing behavior | Detector notes and unreleased research |
| Public release artifacts and checksums | Internal plan docs and operational detail |
Publishing a binary does not publish source code by itself. Source becomes public only when implementation code, patches, symbols with sensitive detail, debug artifacts, or source bundles are committed or shipped.
See also
- MCP Browser Tools — stable public tool names
- Contributing — public repository workflow
- Launch Checklist — public release checks