dsh-locale-es

dsh-locale-es

Español | English | 中文

Spanish (es) language pack for the DeepSeek Harness Web UI — a community DSH client plugin that adds Español to Settings → General → Language.

It does not patch node_modules or the DeepSeek Harness source. It registers through the official locale registry (@deepseek-ai/dsh-client-locale), and keys it does not cover fall back to English automatically.

How do I put DeepSeek Harness in Spanish? Install this pack and pick Español in Settings → General → Language: it translates the whole Web UI without touching the DSH installation.

Verified versions

Compatibility

One pack version serves several DSH versions: the dictionary is the union of the namespaces any version read, what is left over is ignored, and what is missing falls back to English.

Updating DSH does not require reinstalling the pack; see Updating the pack.

DSH is a developer preview with breaking changes. This pack only uses the public locale registry API (ctx.locale.addLanguage / ctx.locale.register), so DSH upgrades need no code changes — only new keys have to be added (see Development).

Installing DSH globally

npm install -g @deepseek-ai/dsh@0.1.6-alpha.2

Do not use @latest: in the npm registry that tag points to 0.1.5-rc.2, older than the version this pack was tested against; the alpha tag points to 0.1.6-alpha.2. dsh --version differing from the @deepseek-ai/* package versions is normal — the CLI and the packages are published separately.

Install

[!WARNING] Do not install this package with npm install. It is not a standalone library: it is a DSH plugin. npm i dsh-locale-es leaves it in whatever directory you are in, pulls in extra peer dependencies, and DSH never loads it — you would still see the UI in English. The correct install is the one below, and it is a single line.

dsh plugin --profile web add dsh-locale-es

The package is published on npm, so that path installs the latest published version. To pin a specific commit (for example, to test an unpublished change):

dsh plugin --profile web add github:GuidoMaxier/dsh-locale-es#<commit>

Restart DSH, then open Settings → General → Language and pick Español.

Updating the pack

The profile pins the installation in its pnpm-lock.yaml: a new version does not arrive on its own. If you installed from npm the lock pins the published version; if you installed from GitHub it pins a commit. Either way:

dsh plugin --profile web update

Restart DSH afterwards. dsh plugin is a passthrough to pnpm: update re-resolves the dependency and then reconciles dsh.profile.bundles against what is installed, so uninstalling and reinstalling is not necessary.

Updating DSH itself needs none of this. The profile does not install its own copies of the harness packages: it symlinks them to the global installation (~/.dsh/profiles/node_modules/@deepseek-ai/* → the npm install), so raising the DSH version leaves this pack loading untouched.

Why there is no peerDependencies on @deepseek-ai/dsh-client-locale: node-semver accepts a prerelease only when the range names that same major.minor.patch, so >=0.1.0-rc.6 does not satisfy 0.1.6-alpha.2. The verified version is in the table above; the pack uses only the public locale-registry API (ctx.locale.addLanguage / ctx.locale.register).

Can I use pnpm instead of npm?

For the pack, there is nothing to choose. dsh plugin is a pnpm forwarder: it runs pnpm <args> inside the profile directory (apps/cli/src/plugin.ts). pnpm is already what manages profile plugins — you only need it on your PATH.

For installing DSH itself, use npm:

npm install -g @deepseek-ai/dsh@0.1.6-alpha.2

A global install of DSH with pnpm fails at startup with ERR_MODULE_NOT_FOUND. DSH imports packages it does not declare as dependencies, and pnpm only exposes declared dependencies to each package — so the modules are on disk but unreachable. npm's flat tree resolves them. Verified on Windows / Node 24 with pnpm 11.7.0, the version this repository pins.

Uninstall

dsh plugin --profile web remove dsh-locale-es

Restart DSH and the UI returns to the previous language. Your stored preference (locale.preference in settings.yaml) is kept, so reinstalling the pack re-activates Spanish by itself; delete it if you want the choice to fall back to the browser again.

Putting the interface in Spanish

1. Open Settings.
2. Go to General.
3. In the Language row, pick Español.

The choice is stored in the DSH settings document and survives restarts of both the server and the browser. If your browser is already in Spanish, DSH detects it and activates it without you touching anything.

Frequently asked questions

How do I put DeepSeek Harness in Spanish? Install the pack, restart DSH and pick Español in Settings → General → Language. The step-by-step is in Install.

Does DSH ship Spanish? No. The interface ships English and 中文 only; Spanish comes from a language pack like this one.

Does it translate the model's replies? No, it translates the interface: menus, settings, buttons and the visible tool text. The language of replies and reasoning is set by prompt or by another plugin.

How is this different from the multi-language plugins? It translates one language in depth: 1626 strings of the current version plus 39 that older versions still read, with a reviewed terminology table, instead of spreading the effort across many languages.

Does it work with my DSH version? It covers 0.1.5-rc.1 through 0.1.6-alpha.2; see Compatibility.

Does anything break when DSH updates? No. Keys that version does not know are ignored and missing ones fall back to English.

Does it change the DSH installation? It does not touch node_modules or DeepSeek Harness code: it registers through the public locale API.

Screenshots

See docs/screenshots/ for the rest.

Reporting a translation bug

Open an issue: https://github.com/GuidoMaxier/dsh-locale-es/issues

Include the namespace and key if you know it (for example workspace.rename.session.title), the text you see and your suggestion, a screenshot, and your DSH version (dsh --version). Strings are edited in data/es-dictionaries.json; see Development.

Scope

• 47 namespaces · 1626 keys for the current DSH — 1477 translated.
• +39 legacy keys in 8 namespaces DSH no longer declares but 0.1.5 still reads, so a user on @latest does not get new English either.
• Covers the shell and settings (settings, settings.models, settings.plugins, settings.agentPreset, settings.pluginInventory, permission.access), the plugin manager (pluginManager), chat and conversation (chat, conversation), trajectory, workspace, subagent, workflowRun, cordis, deliverables, approval, plan, job, feedback, sidebar, sidebarBrowser, sidebarOffice, common, and the rest.
• Missing keys fall back to English (es → en), which is the official DSH mechanism, so a newer DSH never breaks the UI.

How it works

A regular DSH client plugin, in two halves:

The bundle protocol

lib/client.js is not plain ESM. client-modules composes one bundle with every client plugin, and each module registers itself:

window.__ModuleLoader__.load({
  id: "dsh-locale-es",
  factory: () => {
    const module = { exports: {} }
    exports.inject = ["locale"]
    exports.apply = function apply(ctx) { /* … */ }
    return module.exports
  },
})

A bundle that only exports ESM symbols loads without registering, and the loader then reports the failure against a different plugin, because the registration count desynchronizes. tools/build-client.ts emits the correct form.

Development

The scripts need tsx from a DeepSeek Harness checkout, so run them there:

# Re-extract the English corpus from an updated checkout
node --import tsx/esm tools/extract-dictionaries.ts <repo-root> data/en-dictionaries.json

# Bring new keys into es without overwriting translations (seeded in English)
# Moves the keys upstream removes into the legacy dictionary instead of dropping them.
node --import tsx/esm tools/sync-es.ts data/en-dictionaries.json data/es-dictionaries.json \
  data/legacy-dictionaries.json

# Apply a translation batch (replaces existing keys only)
node --import tsx/esm tools/apply-patch.ts data/es-dictionaries.json data/patches/38-nuevo.json

# Rebuild the browser bundle — commit the result
node --import tsx/esm tools/build-client.ts data/es-dictionaries.json lib/client.js

# What is still pending
node --import tsx/esm tools/report-progress.ts data/en-dictionaries.json data/es-dictionaries.json

To test without installing, mount the pack as an overlay. --patch must come before the app's own flags (the web subcommand uses passThroughOptions(), so an app flag first cuts the launcher's parse):

pnpm dsh web --patch <repo>/cordis.patch.yml --no-open      # correct
pnpm dsh web --no-open --patch <repo>/cordis.patch.yml      # error: unknown option

When the pack is already installed in the profile, the overlay fails with duplicate loader entry id: dsh-locale-es. Remove it first (dsh plugin --profile web remove dsh-locale-es) and reinstall it when you are done.

Terminology

• Technical terms stay in English where Spanish-speaking developers already use them: workspace, plugin, prompt, shell, token, timeline, tool calls.
• Command tokens (compact, export, plan…) are never translated: they are what you type on the command line.
• Labels are kept short on purpose. Spanish runs longer than English, and fixed-width elements (buttons, chips, sidebar rows) have little room; the terminology.json table is the reviewed record of those choices.

What the locale registry cannot translate

• Permission preset identifiers (Read Only, Workspace Write, Full access) — the core defines them without display names.
• Tool names (Bash, Read, Write, …) — technical identifiers.
• Model output, file paths and other data, obviously.

Credits

Hernán Casasola — LinkedIn · GitHub @GuidoMaxier

License and disclaimer

MIT. Unofficial community project, independently developed and maintained; not reviewed or endorsed by DeepSeek.