Configuring dsh-emoji
After DeepSeek Harness loads dsh-emoji in the Web Profile, its settings card, 设置 → 插件 → 表情(Whale Emoji), provides these controls:
| Setting |
Behaviour |
关闭 |
Disables emoji use. |
智能 |
The default; allows up to 3 images per reply when they help express meaning. |
高频 |
Requests one suitable emoji in every reply, with up to 4 images per reply. |
| Additional prompt |
Adds instructions for selection, tone and usage context. |
| Pack and size |
Selects the image set and one of four sizes: small, normal, large-ish and large. |
Changes apply from the next reply without restarting the Web Host. The frequency policy still depends on model compliance.
How dsh-emoji processes replies
The model selects from 42 permitted Unicode emojis representing 40 stable semantic keys. DeepSeek Harness’s Host converts recognised output to an inline image from the active pack. The conversion also recognises 😄, 🙂 and images produced by dsh-emoji. It leaves other Unicode emoji, code, links, double-colon text and ordinary Markdown images unchanged. Multiple plugin images must be separated by valid body text, while the same image may recur in different positions.
Uploading dsh-emoji packs
The settings card accepts a ZIP containing pack.json and an images/ directory, optionally inside one same-named directory. pack.json must declare schemaVersion: 1, keySet: "dsh-emoji-core@1", an id, a name and a SemVer version. The archive must provide exactly one PNG for each of the 40 standard keys. ZIP size is limited to 20 MiB, extracted size to 80 MiB, each file to 2 MiB, and image dimensions to 512 pixels. DeepSeek Harness stores packs in $DSH_HOME/emoji-packs/. Removing a pack from the selection list does not delete its bytes, preserving versioned URLs in historical messages.
DeepSeek Harness compatibility
The current release targets npm @deepseek-ai/dsh@0.1.0-rc.7 and declares DSH peers ^0.1.0-rc.7. Local development requires Node.js ^22.19.0 || >=24 and pnpm 11.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub