hellodigua/dsh-emoji

English | 简体中文

Add switchable, customizable inline emoji to DeepSeek Harness responses.

Preview

Installation

Add the plugin to the Web Profile with the DSH CLI, then restart the Web Host:

dsh plugin --profile web add dsh-emoji

Use dsh-emoji@0.2.0 to pin this release. A plain npm install dsh-emoji only adds the package to the current Node.js project; it does not enable the DSH plugin.

How it works

• When the AI wants an emotional or decorative reaction, the built-in protocol tells it to emit a semantic marker such as ::happy::. The Host converts that marker into an inline image from the active emoji pack without another model call.
• Built-in and uploaded packs share 40 stable semantic keys, can be switched at any time, and support four display sizes.
• Rewriting applies only to plugin markers and plugin images. Unicode emoji in ordinary text, code, links, unknown markers, and other Markdown images are left unchanged. Reply text must separate multiple plugin emoji, while a key may repeat later.

Adjusting emoji frequency

After installation and a Web Host restart, open Settings → Plugins → Whale Emoji:

• Off: do not use emoji.
• Smart: use emoji only when it meaningfully helps express emotion, up to 3 per turn. This is the default.
• Frequent: consider emoji more readily without forcing one or seeking multiple emoji, up to 4 per turn.

You can also choose an emoji pack, adjust its display size, or use Additional prompt to control emoji selection, tone, and usage. Changes apply to the next reply without a restart. The model still decides whether to use an emoji.

Uploading your own emoji pack

Click Upload ZIP in the same settings card. After upload, select the pack and save; the next model call uses it without a Host restart. A custom pack implements the same 40 stable semantic keys as the built-in pack, so the AI keeps emitting markers such as ::happy:: while only the final image changes.

The ZIP may contain these files directly or inside one top-level directory:

my-whale.zip
├── pack.json
└── images/
    ├── happy.png
    ├── sad.png
    ├── thinking.png
    ├── celebrate.png
    └── ...the remaining canonical keys

pack.json:

{
  "schemaVersion": 1,
  "keySet": "dsh-emoji-core@1",
  "id": "my-whale",
  "name": "My Whale Emoji",
  "version": "1.0.0"
}

schemaVersion identifies the technical ZIP format, while keySet identifies the semantic set implemented by the images. Uploaded packs must currently declare dsh-emoji-core@1. See the core semantic contract for the normative meaning, visual guidance, and boundaries of every key.

The 40 filename keys are:

happy, sad, confused, watching, angry, speechless, doge, overloaded,
neutral, laughing, crying, sweating, thinking, okay, nodding, sleeping,
hurt, peeking, approve, heart, shy, star-eyes, laugh-cry, touched,
scared, facepalm, eye-roll, sigh, frustrated, playful, snickering,
sarcastic, cool, celebrate, cheer, thanks, sorry, hug, please, applause

Each key must have exactly one matching .png. IDs use lowercase letters, digits, and hyphens; versions use SemVer. Content at one id@version is immutable, so changed assets require a new version. Limits are 20 MiB per ZIP, 80 MiB expanded, 2 MiB per file, and 512 pixels per image dimension. Path traversal, extra files, missing keys, unknown keySet values, spoofed formats, and conflicting content are rejected.

User packs live under $DSH_HOME/emoji-packs/ (default ~/.dsh/emoji-packs/), while Settings stores only the active id@version. Remove hides a pack from the selector but intentionally retains its immutable bytes for historical messages. Uploading the exact same ZIP restores that version.

Compatibility

This version targets npm @deepseek-ai/dsh@0.1.0-rc.6 and declares DSH peers as ^0.1.0-rc.6. Local development pins the exact rc.6 type graph, while the Web Profile provides the shared runtime at deployment.

Local development

Requires Node.js ^22.19.0 || >=24 and pnpm 11.

corepack pnpm install
corepack pnpm typecheck
corepack pnpm test
corepack pnpm build
corepack pnpm pack --dry-run