Turtle
e7def469e1
* feat(i18n): key translation pairing records by heading section Replace the whole-file blob hashes in *.i18n.yaml with one entry per heading section that still holds language-specific content, keyed by the English heading-slug path. Blocks identical across the pair (generated table rows, code blocks, shared regions) stay out of the hash, so edits to different sections and identical regenerations merge with Git's default text merge, including on GitHub. Remove the dsh-translation-pairing merge driver, its resolver command and installer wiring; gen-translation-brief recovers last-confirmed text from commit history. Migrate all active records, archive the superseded Agent Note, and record the replayed conflict reduction in the new one. * test(i18n): refresh translation prompt snapshot for the terminology note * feat(i18n): exclude only code blocks and generated regions from pairing records Replace byte-equality masking with an explicit rule: a record hash skips fenced code blocks and BEGIN/END GENERATED regions, the two kinds of content the pairing gate already requires to be identical on both sides. Move generated data into regions written into both pages: gen-config-catalog renders both languages and the record with per-package regions labelled by code identifiers; gen-module-graph keeps its table in a region; gen-doc-graphs splices the event matrix regions into the Chinese page. Add a generic region splice beside the region grammar.
description, kind
| description | kind |
|---|---|
| Computer-use provider registration for deployments that enable one desktop driver at a time. | package-reference |
@deepseek-ai/dsh-computer-use
English | 中文
Summary
A deployment can enable one computer-use provider at a time. Loading another provider fails with the registered provider name. Each provider supplies its own tools and desktop operations. This package adds no model-visible tools and does not coordinate concurrent Sessions.
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-computer-use'
The service has no configuration. Provider plugins inject computerUse and call ctx.computerUse.register(ComputerUseProviderName(name)); the brand is exported from @deepseek-ai/dsh-computer-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.computerUse.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 driver object, operation interface, 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
- Computer use — provider selection and shared-desktop limits.
- Cua Driver MCP provider — use an installed driver.
- Cua Driver native provider — use the npm runtime.
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.
- Shared desktop — concurrent Sessions and separate DSH processes can operate the same desktop; callers coordinate whole computer-use workflows.
- Provider selection — configuration selects the provider; the model cannot switch registered drivers at runtime.
Dev Note
Working context for maintainers — click to expand
None.