First DSH desktop pet catalog

First DSH Desktop Pet Catalog: Overlays, Status Pets & Live2D

Author
DeepSeekAgent.io Editorial Team
Published
Updated

The first wave of the DSH desktop pet market already spans several product shapes: native transparent overlays, in-Web status pets, optional desktop shells, full-body sprite characters, and Live2D companions. Each can reflect DeepSeek Harness activity, but installation, event sources, platform coverage, and asset licensing differ substantially.

This catalog uses public READMEs, releases, and plugin listings. It focuses on fields that belong on a market page so users can choose and creators can prepare complete listings.

First project catalog

dsh-pet-desktop

dsh-pet-desktop provides a native transparent, frameless, always-on-top, click-through overlay with edge snapping. It scans ~/.codex/pets, ~/.dsh/pets, and bundled assets, supports the Codex Pet format, and includes nine animation tracks, state bubbles, affinity, token metering, and a local loopback API.

It fits users who want a character continuously present on the desktop. Its market listing must separate code and character-asset licenses: the project marks code as Apache-2.0 and the whale decoration as MIT.

dsh-pet

dsh-pet is a registry-driven companion supporting Live2D and sprite pets, Workshop installation, state tracking, feeding, and manifests. It behaves more like a pet-market container in which characters, runtime, and installation metadata can evolve separately.

That structure suits a multi-character market. A listing should lock down manifest schema, asset version, migration, and uninstall behavior so a character update does not corrupt local progression.

dsh-nailong-desktop-pet

dsh-nailong-desktop-pet uses a transparent AppKit companion on macOS and offers an in-Harness fallback elsewhere. Nailong and whale presets demonstrate the format; its Hatch v1 asset contains nine semantic states and 57 frames. A /create-desktop-pet Skill and related tools turn source images into custom pets.

This demonstrates a creator-tool category: users can build character packs in addition to installing finished pets. Listings need source-image rights, generated-asset terms, and export-format details.

dsh-whale-girl-live2d and dsh-live2d-companion

dsh-whale-girl-live2d covers the Web experience with one plugin and provides an optional small macOS shell. It combines Live2D, tool state, interaction, and balance information. dsh-live2d-companion also defaults to a Web widget, offers an optional desktop mode, and ships through dsh.bundle.

Live2D offers expressive continuous characters. Review must cover model, texture, motion, physics, and commercial-use licenses separately.

dsh-desktop-pet and dsh-whale-pet

dsh-desktop-pet is a plugin-first ambient status indicator with no separate daemon or browser. It emphasizes zero network calls, zero extra LLM cost, and deterministic event-to-state mapping. dsh-whale-pet maps five Harness states to character behavior through structured shell.overlay events and avoids UI scraping.

These status pets have a lighter runtime and answer a practical question: what is the Agent doing now? Listings should state clearly whether the pet is a full desktop overlay or appears only inside Harness.

Required market fields

A screenshot cannot establish whether a pet will run reliably. Every DSH desktop pet listing should include:

  • runtime shape: in-Web, native overlay, standalone process, or optional shell;
  • renderer: frame animation, Sprite2D, Live2D, or another format;
  • state source: structured Harness events, plugin API, local loopback, or UI scraping;
  • platforms and tested versions: macOS, Windows, Linux, Web, and verified DSH releases;
  • data boundary: network use, directories read, and access to API keys or Session content;
  • resource cost: CPU, memory, GPU, additional model calls, and background processes;
  • licenses for code, models, textures, audio, and fonts;
  • installation and rollback: source, version, checksum, uninstall steps, and retained data;
  • interaction: drag, resize, click-through, edge snapping, skins, bubbles, and usage displays.

What the first projects reveal

A useful market should not classify only by character name. Strong top-level categories include desktop resident, Harness widget, Live2D character, status and usage component, and creation tool. One character can have multiple implementations, and one runtime can load multiple character packs.

Start with the DSH desktop pet selection guide, then verify Desktop, Web, and rollback installation. Creators should complete the plugin contract, privacy, and asset-license checklist and use structured events from the Tool Call state guide.

References