deepseek-ai/deepseek-harness--packages-browser-use-browser-use ↗★ 226k
@deepseek-ai/dsh-browser-use
注册独占的浏览器使用提供方，同一部署仅可启用一个。 面向需接入浏览器后端的部署者；加载第二个提供方会失败。
同名套件的其他儲存庫
安裝
此插件尚未提供可驗證的 bundle，或相容性檢查未通過。請先閱讀倉庫說明。 閱讀完整 README ↗
說明文件
閱讀完整 README ↗description: "Browser-use provider registration for deployments that enable one browser backend at a time." kind: "package-reference"
@deepseek-ai/dsh-browser-use
English | 中文
Summary
A deployment can enable one browser-use provider at a time. Loading another provider fails with the registered provider name. Each provider supplies its own tools and owns browser sessions. This package adds no model-visible tools or browser operations.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
Mount the service once beside the chosen provider in a Cordis composition:
- name: '@deepseek-ai/dsh-browser-use'
The service has no configuration. Provider plugins inject browserUse and call ctx.browserUse.register(BrowserUseProviderName(name)); the brand is exported from @deepseek-ai/dsh-browser-use/brand. The returned effect disposer releases that registration.
Providers stop admitting tool calls, close their resources, and await owned work before releasing the registration. ctx.browserUse.providerName reports the registered name until release.
Understand the implementation
Implementation internals — click to expand
One private name owns the slot. Cordis effects remove contributions when their plugin unloads; a repeated disposer cannot remove a later registration. The source contains no browser object, operation interface, resource lifecycle, or provider selector.
No runtime invariant companion is published: the registry has one authoritative field and exposes no independently maintained observation that can diverge. Duplicate rejection and plugin disposal are covered by the owning tests.
Further Exploration
- Browser use — provider selection and Session ownership.
- Playwright MCP provider — Playwright browser tools.
- Chrome DevTools MCP provider — Chromium inspection and control.
- Stagehand provider — native browser operations with AI assistance.
Model Experience
None, as this registry only records provider names.
KV Cache effect
Registration does not alter model requests. Provider-owned tools and guidance determine their own request-prefix effects.
Known Limitations and Deferred Work
The service limits registrations within its Cordis service instance.
- Browser ownership — providers own browser resources and enforce Session isolation; this service stores no browser state.
- Provider selection — configuration selects the provider; the model cannot switch registered backends at runtime.
Dev Note
Working context for maintainers — click to expand
None.