Desktop browser control
bb 0.43.3SDK 0.4.104pinned e865697 (desktop-v0.43.3)
Controls a selected desktop window through bb.sdk.experimental_desktopBrowsers. With this, a plugin can:
Use your automation tool on BB-owned tabs
What it gives you
- Discover instances on an explicit host and create thread-owned tabs with separate automation profiles
- Acquire expiring control; reveal the first tab and new CDP pages only in the already focused thread, without activating the desktop window. Personal tabs require an explicit handoff
- Give a worker on that host a private, scoped CDP WebSocket connection for DevBrowser or agent-browser
- Capture or reveal a tab and release control while preserving the tab and its login
- Observe changed tab and control state with a disposable two-second polling subscription; report disconnect errors
- List browsers installed on the desktop host and copy a profile's signed-in cookies into the personal BB browser or an automation profile
API
Each symbol links to the pinned commit it was read at.
ExperimentalDesktopBrowsersAreainterfaceExperimentalDesktopBrowserScopetypeExperimentalDesktopBrowserLeasetypeExperimentalDesktopBrowserCreateInputtypeExperimentalDesktopBrowserAcquireInputtypeExperimentalDesktopBrowserInstanceRequesttypeExperimentalDesktopBrowserImportCookiesInputtypeExperimentalDesktopBrowserImportSourcestypeExperimentalDesktopBrowserImportOutcometype
Used by
DevBrowser
The brief is Markdown, written for a coding agent: what the capability is, where it registers, every SDK symbol with a pinned permalink, the rules that bite, and what done means.