DSH Desktop Pet Installation: Desktop, Web & Rollback

DSH pets may ship as GitHub sources, release ZIPs, Profile dependencies, or legacy Web injections. Their load locations and upgrade paths differ.

Before installing, identify Desktop versus Web, the exact DSH version and engines.dsh range, whether the plugin was tested in Electron, and where Profile and progression backups live. Desktop and Web use different origins, so local storage normally does not migrate automatically.

Prefer the DSH plugin manager for projects using the current contract. Fully exit Desktop after installation, reopen it, and confirm the settings or companion entry. Avoid applying legacy host-file patches to current Desktop builds.

Validate idle, working, completion, and failure states; disable behavior; restart persistence; network controls; and clean uninstall. Roll back through the plugin manager rather than deleting the whole Profile. For cold-start Preset errors, check Runtime Hoisting.

References

• Community Desktop installation instructions
• Desktop support and Web storage boundary
• DSH Plugin Manager guide

FAQ

Why is the pet missing after installation?

Confirm the active Profile and fully restart the host. Hot reload may not replace an injected page script.

Does Web progression move to Desktop?

Usually not. Separate origins isolate local storage unless the plugin provides export and import.

Should I copy another user's complete Profile?

Avoid it. Profiles can contain unrelated plugins, version locks, and local configuration.