Better real photographs, without handing an image service your private magazine.
This release adds DSH Visuals, a separate optional image-source plugin for Vibeify. It searches public catalogues using only a short displayed title from an explicit magazine page, preserves creator and licence provenance, and keeps Vibeify readable when the plugin or every provider is unavailable.
Downloads
Choose the ZIP for your computer and compare it with SHA256SUMS before opening it.
| Platform | Release evidence | What to open |
|---|---|---|
| Apple-silicon macOS 14+ | Verified. Public download, archive integrity, source validation, and the isolated end-to-end installer flow pass on a real Mac. | Install DSH Vibeify.command |
| Windows 10/11, x64 or arm64 | Preview. PowerShell parsing and cross-platform installer contracts pass; a real Windows installation run is still required before this is labelled verified. | Install DSH Vibeify Windows.cmd |
| Current desktop Linux, x64 or arm64 | Preview. Shell syntax and cross-platform installer contracts pass; representative real distribution runs are still required before this is labelled verified. | install-dsh-vibeify-linux.sh |
Compatibility
| Component | Qualified version or boundary |
|---|---|
| DSH Vibeify | 0.15.6 |
| DSH Visuals | 0.1.0, installed alongside Vibeify but optional at runtime |
| DeepSeek Harness | Tested with @deepseek-ai/dsh 0.1.1-rc.2. DSH remains a fast-moving developer preview. |
| Node.js | 22.19+ within Node 22, or Node 24+ |
| Image sources | Wikimedia Commons and Openverse without keys; Pexels and Pixabay with reader-supplied keys |
What changed
- The friendly macOS, Windows and Linux installers add the separate
dsh-visualspackage alongside either Vibeify provider mode. - Wikimedia Commons, Openverse, Pexels and Pixabay results pass through one provenance-preserving adapter and are ranked for title relevance, dimensions and non-repetition.
- Wikimedia and Openverse results are accepted only when a reusable licence and original landing page remain available.
- Pexels and Pixabay keys are entered under Settings → Images, stored through DSH's local credential service and resolved only for an individual provider request.
- The browser receives configured/not-configured status, never the stored key. Keys are excluded from RPC results, logs, cache, previews, public articles, commits and support reports.
- Only a short title from an explicit magazine page is searched. Ordinary Chat cards, article bodies, prompts, attachments, history, preferences and current private images do not cross this boundary.
- Search is loopback-only, bounded, fail-soft and cached locally for 30 days. A recent URL pool reduces accidental visual repetition.
- If no suitable reusable image exists, the unique story-specific local cover remains. The plugin does not pretend that every subject has an exact lawful photograph.
Checks performed
- 182 Vibeify tests pass.
- 6 DSH Visuals tests pass, including credential isolation, provider failure, reusable-licence filtering and loopback-only RPC.
- macOS isolated installer flow and cross-platform source contracts pass.
- Generated browser clients match their source modules.
- Plugin manifests, skill front matter, package contents, shell syntax and JavaScript syntax pass.
- No Pexels or Pixabay secret value is embedded in the repository or release packages.
Upgrade and rollback
Finish active DSH work before upgrading. The friendly installer installs immutable packages, canary-boots them away from the live port, and restarts only after idle confirmation.
To roll back, download the 0.15.5 release assets, install that versioned source, then restart DSH after current work finishes. Removing DSH Visuals does not delete DSH sessions, Codex authentication, DeepSeek credentials, browser-stored Vibes, previously published pages, or provider keys already held by DSH's credential service.
Add Pexels or Pixabay
Open DSH Settings → Images after installation. Follow the official provider link, create a key under that provider's own terms, paste it into the password field, then choose Save key. Do not paste keys into Chat, a terminal command, an issue, a screenshot or a support report. A blank field never clears a stored key; Remove key is the separate clearing action.