Mnemon
中文
mnemondsh-mnemon
Contents

v0.5.33: Git Sync Finds Its Token, and Memory Tasks Leave No Empty Conversations

View source on GitHub

This patch release fixes two reported bugs and documents how the desktop app updates from older releases: #437 to #441. Only the Starter changes.

  • Git sync finds its token whatever Git configures (#441, issue #408). On a computer whose Git configuration names a user for the host or turns on credential.useHttpPath, as Git Credential Manager setups do, Git sync over HTTPS kept saying "Needs credentials" although you were signed in or had given a token: Git looked the token up under that name or path and found nothing. Git now looks it up under the name dsh-mnemon stored, whatever the configuration says, and an address that writes its host in capitals or with its port, such as https://GitHub.com:443/..., finds its token too.
    • gitee.com refuses x-access-token, so it is offered the token under oauth2; every other host keeps x-access-token.
    • A host that wants another user name, such as Bitbucket or a self-hosted Gitee, takes it in the address, as in https://x-token-auth@bitbucket.org/.... A password or a token in the address is still refused.
    • When the host rejects a credential it was offered, the sync settings now say so and name it, the GitHub sign-in, the saved token or MNEMON_SYNC_GIT_TOKEN, instead of saying credentials are needed.
  • Memory tasks no longer leave empty conversations (#438, issue #435). Every memory task that runs outside a conversation runs under a task Agent whose session DSH keeps: Save to memory, Ask Agent, Document archive, a new Memory Space's Provider choice, Tidy names and descriptions, runtime memory capacity maintenance and memory reconciliation. Where DSH held no record of such a session, its sidebar listed it as an empty Untitled conversation under Ungrouped, one more for every task, and DSH's ACP session list listed it on any host. The task Agent's session now carries the origin DSH gives its own subagents, so neither list shows it; the tasks run and report as before. Rows earlier releases left stay until you archive them with Archive session.
  • Updating the desktop app from 0.5.30 and earlier on DSH 0.2.1 (#437, issues #433 and #436). There, Check versions → Update stops with already-installed, and the command line does not manage the desktop app's profile. The documentation now gives the route: uninstall dsh-mnemon on the Plugins page, add it again with Add plugin as dsh-mnemon@<version>, then restart the app. Your memory data and settings stay.
  • README. The READMEs end with the star history and a License section (#439, #440).
  • For plugin authors. A plugin that reads session logs now sees a task Agent session with origin: "subagent" and no parent; the Delegated child sessions section of the workflows reference describes it.

Upgrade and compatibility

DSH 0.2.0-rc.2, 0.2.1-rc.1 and 0.2.1-rc.2: use Memory System → Status → Check versions → Update, then restart DSH. That works from dsh-mnemon 0.5.31 and later on every supported DSH, and on DSH 0.2.0-rc.2 also from 0.5.19 in the WebUI and from 0.5.22 in the desktop app. Older installations, including 0.5.30 and earlier on DSH 0.2.1, where the update stops with already-installed, update once by hand: quit DSH, install the exact version, then start DSH again.

sh
dsh plugin --profile web add dsh-mnemon@0.5.33

An explicit version avoids pnpm selecting an older release during its 24-hour release window. The command line does not manage the desktop app's desktop profile: there, Uninstall dsh-mnemon on the Plugins page, add it again with Add plugin as dsh-mnemon@0.5.33, then quit the app completely and open it again. Your memory data and settings stay.

Supported DSH releases are unchanged: DSH 0.2.0-rc.2 and 0.2.1-rc.1, and the 0.2.0 and later 0.2 releases after them (>=0.2.0-rc.2 <0.2.1-0 || >=0.2.1-rc.1 <0.3.0-0), which includes 0.2.1-rc.2, now npm's latest and next. DSH refuses this release on DSH 0.1.7, 0.2.0-rc.1 and the 0.2.1 alphas; Compatibility and upgrades says what to do there.

Git sync addresses that name a user are new in this release. An earlier dsh-mnemon refuses a saved address that names a user, even to change or disconnect it, so remove the name before going back to one.

Existing memory and settings need no migration, and stored settings keep their keys. Plugin peer floors and the Starter's external runtime dependencies are unchanged.

Changed packages

Package Previous New
dsh-mnemon 0.5.32 0.5.33

The other 17 component versions are unchanged.

Verification

Release acceptance installs the new Starter through Add plugin on fresh DSH 0.2.1-rc.2 and 0.2.0-rc.2 hosts, checks Status, Runtime, a Native space with CLI and WebUI recall, Entities and Check versions, updates a v0.5.32 installation through Check versions on each, and updates a v0.5.30 installation on DSH 0.2.1-rc.2 with the exact install above. The release branch passes the full workspace verification on the pinned DSH 0.2.1-rc.2, the root tests against an installed DSH 0.2.0-rc.2, and 64 real Git sync checks on each of the two releases.

Each change has its own record in the evidence index:

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

Previous release: v0.5.32.