@busabase/dsh-plugin

Configuration

The defaults connect to Busabase at http://localhost:15419, start or reuse a loopback service on demand, enable live Inspector refresh, and require confirmation for review actions.

To use another address, adjust plugin load order, or tune server and refresh behavior, see the full configuration reference.

Connecting to Busabase Cloud

Override the Bundle row by id and point baseUrl at an https:// Busabase Cloud address (a root-host deployment, optionally with spaceId, or a workspace subdomain) to connect there instead of a local server:

- id: busabase
  config:
    baseUrl: https://busabase.com
    serverName: busabase

The plugin never manages or starts a remote server. When the remote plugin loads for the first time, it opens your OS browser for a standard OAuth sign-in; DeepSeek Harness stores the resulting token through its credential store, not in this configuration. The MCP connection still sends a fixed changeRequest permission ceiling. In this release the Inspector's review, merge, live refresh, and embedded Base/AirApp previews stay local-only: use the canonical Busabase Cloud link the Inspector shows to inspect, review, and merge remotely.

Desktop ChangeRequest previews use the existing official Sidebar Browser on a compatible DeepSeek Harness host (protocol v1, native browser capability, and the official registered browser provider). The Browser owns workspace readiness. Automatic previews, card clicks, and recognized preview links share this handoff; Busabase installs no official sidebar plugin. Opening a tab expands the official sidebar; a deduplicated preview can re-expand a collapsed sidebar. Desktop never falls back to a plugin Inspector or iframe. Cards retain accessible canonical links when native dispatch is unavailable or fails, and a deliberate click can retry. Other entity cards use their existing validated links; entities without a destination remain metadata rather than inert buttons. A successful handoff means the host accepted navigation, not that the guest page loaded.

On Web only, when the optional sidebarRight and sidebarRightTabs services are available, Busabase contributes a busabase-inspector tab definition and a keyed sidebar.right.pane.tab body. It does not replace the single root rightbar, so the official Sidebar and Browser remain mounted. Inspector is recoverable from the sidebar guide, and its Close control closes only its own tab. Its body hides a selection belonging to a different session. Inspector navigation carries no preview URL or bearer token in tab parameters. Web hosts missing these services retain the legacy root Inspector fallback. Desktop registers neither Inspector tabs/bodies nor a root fallback, including while optional services load or unload.

The sidebar coexistence regression tests mount the real SlotRuntime and official SidebarRight/SidebarBrowser registrations. Their native-path test uses a fake Desktop bridge and asserts a mounted webview shell; it does not prove Electron guest navigation, authenticated Cloud content, or true Desktop acceptance. The test-only DockKit and primitives dependencies are explicitly declared, with DockKit transformed by Vitest. A plugin-scoped Shiki 4 override satisfies the rc.2 primitives API while preserving the workspace default.

Local token persistence: the official Sidebar Browser stores its full current URL, including any preview bearer token, in the local dsh.sidebar-browser.v1. checkpoint. Closing the browser tab removes that checkpoint; hiding it, switching sessions, or unloading this plugin does not. This integration accepts that host-owned local persistence. The adapter deduplicates by session, Space, and ChangeRequest, never by URL or token, and never logs preview URLs.

Use Reopen, a card click, or Reload preview for a deliberate retry after closing a tab or a failed handoff. Native browser Reload retries the existing URL; an expired token requires a fresh authorized preview request (click the original ChangeRequest card again when its tool result has no preview URL). Failed preview fetches are not retried automatically. Review and merge remain in Busabase Cloud.