Build DSH Desktop Pets: Contracts, Privacy & Licenses

A stable DSH companion separates host-event adapters, a character state machine, rendering assets, and local settings. This makes DSH upgrades, character swaps, and Live2D additions easier to maintain.

Start with idle, working, waiting, success, and error. Debounce consecutive Tool Calls and derive state from structured events. Pet failure must never block Agent execution.

Declare accurate engines.dsh, avoid installing a second DSH runtime into the Profile, initialize lazily, uninstall cleanly, and validate every release through a fresh Profile and cold start.

Keyword awareness, account balance, weather, accessibility speech, and voice should be independent opt-ins. Basic state reactions do not require chat text. Balance features should expose minimal data through a local backend without sending API keys to the browser.

Document code, illustration, Live2D model, voice, music, and font licenses separately. Local display rights do not automatically permit redistribution or commercial use.

A desktop-pet market should record author, repository, version, compatibility, type tags, network and data access, per-asset licenses, install and uninstall steps, screenshots, resource use, and last verification date.

References

• Community pet v2.4.0 engineering and compatibility
• Desktop contracts, settings, and privacy controls
• DSH plugin-market lifecycle discussion

FAQ

Must a DSH pet use Live2D?

No. Static image sequences are easier to keep lightweight and compatible.

Can a market display one license for everything?

Only when code and every asset share that license. Otherwise list them separately.

Does state integration require modifying DSH source?

Prefer plugin events and structured host markers over patching built-in packages.