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 |
|---|---|
| The agent loop's settings page on the dsh web client's Plugins page: the parallel tool-call cap of the agent-loop namespace. | package-reference |
@deepseek-ai/dsh-client-ui-settings-agent-loop
English | 中文
Summary
Open Plugins in the sidebar and select Agent loop in the Official group to set how many parallel-safe tool calls one step may run at once. The page stages what is typed and writes it only on save, marks a value the user overrode, and offers to reset it to the deployment's default. The page exists while the Host serves the agent-loop namespace.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
The Agent loop card in the Official group opens the page. Parallel tool calls bounds the calls the loop runs at once within one step; the field renders the effective value, and once overridden carries an Overridden badge with Reset to default beside it. Nothing is written until Save; leaving the page drops the draft, an empty field saves as a reset, and text that is not a number blocks the save and says so under the field.
Understand the implementation
Implementation internals — click to expand
The Host half is an empty apply, present only so the package holds a Loader row the client module system serves the browser half for. The browser half binds the agent-loop namespace through ctx.configForms.get, keeps the staged form in AgentLoopCardController over the shared SettingsFormModel of ui-primitives, and registers AgentLoopCard into the Plugins page's plugins.item slot through ctx.configForms.whileServed. The page's copy lives in this package's settings.agentLoop dictionary.
Further Exploration
- ui-plugin-manager — the Plugins page and the
plugins.itemslot the page registers into. - ui-settings — the settings scope and the served-namespace watch the page rides.
- ui-primitives — the settings form model and fields the page renders.
- agent-loop — the loop that registers the
agent-loopnamespace.
Model Experience
None, as the package is a browser-side settings surface that registers no model surface.
KV Cache effect
None; this package neither assembles nor sends a provider request.
Known Limitations and Deferred Work
- One field of the namespace — the Host section carries only the parallel cap; the composed
agentsarray is boot composition, not a user setting, and has no field here. - Runtime invariant: No companion is published. The page holds no owned relationship of its own: what it shows derives from the settings mirror, and what it writes the Host validates.
Dev Note
Working context for maintainers — click to expand
None.