Turtle
38c7a9fbf4
* feat(release): publish package source, declaration maps, and documentation Every release member publishes its TypeScript source and the declaration maps that resolve into it, and @deepseek-ai/dsh publishes the repository Markdown documentation staged from docs/ at prepack time. The ./src/* export most members already declared now resolves for an installed consumer, and a consumer editor follows a declaration to the implementation. Bundled JavaScript maps stay unpublished; the vendored family and the Desktop runtime file policy are unchanged. Rationale: .agents/notes/implemented/process/2026-10-08-published-source-and-docs.md * feat(release): publish JavaScript maps and compress bundles Every emitted JavaScript map ships beside the bundle it describes, and the workspace build and the client preset compress bundles without mangling identifiers. The documentation payload now mirrors the website publication manifest and is removed again by `postpack`; Desktop and the Python executable exclude the published source, documentation, and maps; `clean` removes a staged copy. Typert's publication contract gains the Remote declaration map. * fix(release): keep node bundles readable for the worker image The browser worker image lowers `yield*` only as a whole statement and rewrites `for await` loops by their source layout, so compressed node-side entries either fail that lowering or lower to unparseable code. Only the browser bundles keep compression, which removes about a third of their text. The bundle-purity assertion now matches the module-loader call regardless of the quote style compression picks, and the release-pack fixture exercises the installed package's new documentation requirement. * feat(release): publish the whole documentation tree `@deepseek-ai/dsh` copies `docs/` in full instead of the website's page set: the maintainer documents, the generated migration records, the translation guidelines, and the `*.i18n.yaml` consistency records ship with the installed package, so the documentation's own links resolve without a checkout. * feat(release): publish the upgrade guides with the documentation The staged documentation keeps the website's page set and adds every `docs/upgrade-guide/` document, which is what an installed reader consults when a released change breaks something. The rest of the maintainer tree stays out. * test(release): expect source and maps in master's new payload cases * feat(release): keep installed docs and source readable in Desktop Desktop keeps the published src/ and docs/ trees inside app.asar, and every model shell call receives DSH_INSTALL_DIR and DSH_NODE_EXECUTABLE so an agent can read them through Electron's Node mode. Staging also generates docs/upgrade-guide/README.md, an index of the upgrade guides grouped by the release they upgrade from. Minified client bundles print string literals with backticks: the worker image packer now recognizes those chunk requests, client license banners are prepended after minification so their text survives, and the affected artifact tests accept either quote. * test(desktop): read archived docs through the Windows PowerShell form Regenerate the config catalog for the shifted shell-env source line. * test(desktop): wait for the GUI-subsystem Electron process from PowerShell * build(release): publish source and maps from the message-quotes package * build(release): publish source and maps from packages new on master * build(release): publish source and maps from the tool-office package
description, kind
| description | kind |
|---|---|
| Browser-use provider registration for deployments that enable one browser backend at a time. | 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.
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.