DSH | dsh-locale-es | Spanish (es) language pack for the DSH Web UI

[GuidoMaxier]

Unofficial project, independently developed and maintained by community members.

Project URL: https://github.com/GuidoMaxier/dsh-locale-es

Introduction

A community language pack that adds Spanish (es) to the DSH Web UI. It is a regular DSH
client plugin: it registers the language through the official locale registry
(@deepseek-ai/dsh-client-locale) via ctx.locale.addLanguage, and supplies
per-namespace dictionaries via ctx.locale.register. It does not patch node_modules
or the DeepSeek Harness source.

Install

dsh plugin --profile web add github:GuidoMaxier/dsh-locale-es

Restart DSH. The UI comes up in Spanish on its own — no trip to Settings needed. To
switch later: Settings → General → Language.

Removing it is the same, one line:

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

Scope

• 42 namespaces · 1305 keys — 1174 translated.
• Covers the shell and settings (settings, settings.models, settings.plugins,
  settings.agentPreset, settings.pluginInventory, settings.permission), chat and
  conversation (chat, conversation), trajectory, workspace, subagent,
  workflowRun, cordis, deliverables, approval, plan, job, feedback,
  sidebar, common, and the rest.
• Keys the pack does not cover fall back to English automatically (es → en), so a
  newer DSH never breaks the UI.

Screenshots

Settings → General → Language:

The General panel, fully in Spanish:

A conversation:

The sidebar:

Plugin and model settings — the surfaces with the longest copy:

Notes on terminology

• Technical terms stay in English where Spanish-speaking developers already use them:
  workspace, plugin, prompt, shell, token, timeline, tool calls.
• Tool names (Bash, Read, Write, …) and permission preset identifiers are not
  reachable through the locale registry, so they remain in English.
• Labels are kept short on purpose: Spanish runs longer than English, and fixed-width
  elements (buttons, chips, sidebar rows) have little room. "New task default" is
  simply "Predeterminado".

Tested against DeepSeek Harness 0.1.5-rc.2, Node.js ≥ 22.

Two things I'd be glad to hear from Spanish-speaking users: does any technical term
feel off (I kept workspace, plugin, prompt, token, timeline and tool calls
in English where a Spanish equivalent would read forced), and are there surfaces still
showing English that I missed?

[unera]

Related proposal, may matter for how this one ships: make the UI locale an ordered preference list (e.g. ru → en → zh) instead of a single choice, so a partly translated UI falls back to a language the user actually reads rather than to untranslated islands and Chinese source keys. It also keeps the shipped-locale set from being a closed enum.

Details and a link list of the other language threads: #11699