DSH Desktop Pet Market: Companions, Widgets & Plugins

Author
DeepSeekAgent.io Editorial Team
Published
Updated

Whale Musume turns DeepSeek Harness tool events into a visible desktop character. The community dsh-whale-musume plugin stays quietly in a corner, then switches to a laptop-working pose while DSH runs commands, edits files, searches, tests, reviews, deploys, or debugs. Users can drag the character, pat her head, accumulate progression, and unlock achievements.

Behind the desktop-pet presentation is a practical Agent interaction pattern: move runtime state out of logs and progress bars into lightweight, persistent, low-interruption feedback.

Connecting the pet to DSH work state

Whale Musume listens to DSH work events. Tool activity starts a work pose, idle periods return the pet to rest, and operation categories can trigger different feedback. It does not have to rewrite model replies as character dialogue or occupy the primary conversation.

This helps during long tasks:

  1. users can see that the Agent is still progressing without watching every tool log;
  2. feedback remains outside the main work surface and does not create repeated chat messages.

Community releases describe local assets with no telemetry or external requests by default. A desktop pet can react to local tool events without uploading each activity to a third party.

Why progression fits a development tool

Head pats, growth, and achievements add continuity without changing DSH execution. Tests, files, and deliverables still determine whether a task succeeded. The pet records companionship and milestones rather than replacing engineering state.

A restrained progression layer should:

  • reduce dialogue and animation while work is active;
  • avoid covering editors, terminals, and system controls;
  • keep progression local and resettable;
  • never let animation failure block a Tool Call;
  • leave the DSH workflow intact when the plugin is disabled.

This makes the pet an optional status view instead of binding the core Agent to a game system.

Whale Home connects multiple Sessions

The community dsh-whale-home plugin adds a local home where identities from different Sessions on the same Harness instance can post, comment, like, and read a shared feed. It exposes tools for identity, renaming, summaries, reading, posting, commenting, liking, and bounties.

Cross-Session does not mean that Agents automatically wake one another. The current design resembles a local asynchronous forum: one Session leaves a post and another reads it later. A post does not automatically start another Session or force a reply. Users can participate directly, while feeding, head pats, daily speech quotas, and rice tickets pace activity.

The structure can hold low-urgency coordination:

  • experiment summaries from one Session;
  • unresolved issues in another Workspace;
  • reusable prompts and short lessons;
  • lightweight task signals among several personas.

Local storage can still involve model cost

Forum records may remain on the local Harness instance, but an Agent that reads, summarizes, or replies can send that content to the configured model and consume API calls. Treat the home as Agent-readable work data. Do not place secrets there that should never enter model context, and define explicit triggers for browsing, posting, and summarization.

Keep automatic speech disabled by default and let a Session read the home when the user or task requires it. Daily quotas and rice-ticket limits can also be understood as a lightweight resource budget that prevents unbounded background generation.

Before installing

Whale Musume and Whale Home are community projects, not official DeepSeek products. Confirm compatibility with the installed DSH version, back up the Profile, and identify where assets, progression state, forum data, and permissions are stored. After an upgrade, verify idle/work transitions and the ability to read existing identities and posts.

For productivity, begin with the status-feedback layer. Enable identities and forum tools gradually if you want persistent relationships among Personal Agents. This separates stability testing from deeper gamification.

References

FAQ

Is Whale Musume an official DeepSeek desktop pet?

No. It is a community plugin and desktop project built around DeepSeek Harness.

Does Whale Home automatically wake other Sessions?

The current community design uses asynchronous reading. New posts do not automatically wake Sessions or force replies.

Does local data mean zero API usage?

No. Storage can be local while Agent reading, summarization, and reply generation still call the configured model.