AI Agent Hub
Back to plugins
🖥️

dsh-espanol

Client Updated 2026.08.21

Run the following command in DeepSeek Harness:

dsh plugin install mscnegocio-del/dsh-espanol

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install mscnegocio-del/dsh-espanol inside DeepSeek Harness to install the Spanish locale plugin; the source is hosted at https://github.com/mscnegocio-del/dsh-espanol

About this plugin

The DeepSeek Harness web GUI currently ships with only two interface languages, Chinese and English. For users who think and work in Spanish, navigating the tool means constantly parsing an unfamiliar language or settling for a compromise. dsh-espanol plugs that gap as a community plugin that registers Spanish dictionaries across all 29 UI namespaces, covering 718 strings, and appends an Español entry to the language selector in Settings.

The plugin follows a strict do-no-harm principle. It never forces Spanish on anyone: existing Chinese and English users see no change at all. Only a browser whose primary locale is Spanish and that has no stored zh or en preference will automatically land on the Spanish interface, mirroring the built-in browser-detection logic. Placeholders such as {count} and {name} are preserved, and technical terms like token, TTFT, LLM, and API remain untranslated so functional meaning is never distorted.

A few limitations are worth knowing. In the current version the Spanish preference is not persisted across restarts because the host locale schema only accepts zh or en; the workaround is browser auto-detection on every boot. Additionally, two string groups—slash-menu command descriptions and permission-preset names—remain in English by design, since they originate from host composition data rather than client-side locale dictionaries. These are tracked as deferred work. If you or your team want a natural Spanish interface when working with DeepSeek Harness, this lightweight plugin is the most direct way to get one.

Use Cases

  • A Spanish-speaking user wants to navigate the entire DeepSeek Harness UI in their native language
  • A multilingual team has members who prefer working in a Spanish interface
  • Users in Latin America or Spain reduce comprehension overhead when first exploring Harness

Best For

  • Developers or research teams who work in Spanish as their primary language
  • Users in Latin America and Spain who rely on the DeepSeek Harness web GUI
  • Platform or ops leads who want to extend a localized experience to multilingual teams