v0.5.22: In-App Updates, Conversation Tabs and Ollama Subagents

This patch release contains the three pull requests merged after v0.5.21:

• Check versions → Update works in the desktop app (#325).
  • The Host updated dsh-mnemon by running pnpm from PATH in the owning Profile. The desktop app's Host has no pnpm on PATH, so the dialog only reported that pnpm was missing, and DSH's Plugins page cannot update an installed plugin.
  • The update now goes through DSH's own plugin installer, as dsh plugin add dsh-mnemon@<version> does. It uses the Profile's package manager, which in the desktop app is the app's bundled pnpm, with the Profile's registry settings, fallbacks and lock. It installs the exact checked version, so pnpm's 24-hour release window does not hold it back. An optional Strategy the Profile added on its own updates the same way.
  • DSH checks the DSH versions the new release supports before keeping it. A failed install restores the Profile's files, and the dialog shows pnpm's error line and DSH's log. The enabled plugins stay as they were, and success is reported only once DSH lists the new version.
  • DSH loads the new Memory System page as soon as the files change, which used to close the dialog before the update reported back. The new page now reopens Status with the dialog, which shows the update and the restart it needs.
  • Until DSH restarts, a notice above every Memory System page names the installed version and the one that still runs, whether the update came from Check versions or dsh plugin. Status shows the running version and Check versions the installed one, so it no longer offers an update dsh plugin already installed.
• The Memory System works in a conversation tab whose Agent is not loaded (#326).
  • Mnemon found a conversation's workspace only through its loaded Agent. For a conversation DSH showed but had not resumed, for example one whose Agent preset is no longer in the profile, Status read "Waiting for workspace" and Project Documents failed with memory Source is unavailable in the requested management scope.
  • With workspace or centralized storage, runtime memory and Memory Spaces in that tab used the directory DSH started from. Entries saved that way stay in that directory.
  • The Host now finds the workspace in DSH's workspace registry, which lists every session whether or not its Agent is loaded. A new Project Document is written directly. When Documents are full, a task Agent in the conversation's workspace archives the least recently used one first, and a task Agent also chooses a new Memory Space's Provider; both used to fail with "current DSH agent is not live".
• Memory subagents recover when a chat template requires a user query (#328, issue #327).
  • On Ollama 0.33 with Qwen3.x, idle review and the other memory subagents failed with no user query found in messages, sometimes after the review had already created a Document. A subagent's only user turn is its prompt. Once tool results filled the context window, Ollama's truncation dropped that prompt and kept the tool results.
  • When a server refuses a subagent request this way, Mnemon adds a short user turn to that step and retries it at once; later tool continuations of that subagent end the same way. Subagents on servers that never refuse, and the main conversation, send exactly what they did before. A larger Ollama context length also avoids the truncation.

#Upgrade and compatibility

Supported hosts: DSH 0.2.0-rc.2 (npm latest and next) and DSH 0.1.7-rc.2. Complete profiles require Node ^22.19.0 || >=24.0.0. Older hosts should retain v0.5.16.

Install dsh-mnemon@0.5.22 through Plugins → Add plugin, then choose Enable now. The CLI alternative is:

dsh plugin --profile web add dsh-mnemon@0.5.22

Include the version for the first 24 hours after publication. pnpm 11 does not pick a version published less than a day ago, so until then a plain install or update picks 0.5.21, which both hosts accept. A versioned install pins the version; upgrade it later with dsh plugin --profile web update --latest dsh-mnemon.

• Existing installations: for the first 24 hours run dsh plugin --profile web add dsh-mnemon@0.5.22. Afterwards dsh plugin --profile web update dsh-mnemon works (update --latest for a versioned install). Then restart DSH.
• Desktop app: DSH's Plugins page cannot update an installed plugin, and 0.5.21 and earlier cannot update themselves in the app. Update once by removing dsh-mnemon on the Plugins page and adding dsh-mnemon@0.5.22 again, then quit the app completely and reopen it. Your memory data stays. From 0.5.22 on, Memory System → Status → Check versions → Update installs later releases.
• Restart notice: the running Host reports it, so it first appears for updates from 0.5.22. After installing 0.5.22 over an older version, restart DSH as before.

No memory storage or configuration migration is required.

#Changed packages

The Starter pins 17 component packages; none of them changes.

#Verification

The versioned release acceptance installs the release package through Add plugin on both supported hosts. Each fix has its own before-and-after record:

• updates through DSH's installer;
• a conversation tab without a loaded Agent;
• subagents and chat templates that require a user query.

Publication verifies the complete pinned composition, the Registry installation and the real upgrade before creating the GitHub release.

Previous release: v0.5.21.