Skip to content

1.0.5 · DSH Memory

Choose a tag to compare

@KingsleyAsher KingsleyAsher released this 05 Nov 06:43
· 7 commits to main since this release

DSH Memory 1.0.5

修复工具调用完成后的记忆续步:DSH 步骤输入只包含本步新消息,原来在只有工具结果时可能以空证据快照替换已召回约定。现在从会话历史查找最近的真实用户任务,每步重新查询记忆;其他插件的 user 角色消息不能覆盖用户任务,删除、撤回及新任务切换仍然生效。

提示语区分历史资料和当前适用的用户偏好与工作约定,要求在计划及工具完成后的后续步骤中落实有效约定,不扩大条件或绕过授权。不引入后台自主执行器,不把所有历史记忆当作指令。

保留 1.0.4 的详情页、手动检查入口、静默自动更新和严格保存回执。中英文使用说明、项目记录、版本描述及下载链接同步到 1.0.5。

必要简查包括合成续步反例、真实本地 Python 工作进程的持久保存与召回、删除与任务切换、保存回执及已有发布检查;包内文件回读和公开内容扫描通过。没有使用私人记忆库、真实录音或外部付费接口,也未验证真实模型最终生成了笔记。更新源可见不等于当前宿主已经安装并重新加载。

自动更新沿用启动后约 15 秒和每 6 小时的检查,由宿主管理器安装;也可在“记忆 → 详情”主动检查。镜像可能延迟,更新器选择可用源中的最新有效版本,校验失败保留旧版。宿主要求重启时,保存工作并按提示重新加载后确认运行版本。

DSH Memory 1.0.5

Fix memory continuation after tool calls. DSH pre-step input contains only newly claimed messages; a tool-only continuation could replace recalled preferences with an empty evidence snapshot. Recall now uses the latest genuine user task from session history and queries current memory again at every step. User-role messages from other plugins cannot replace that task. Deletion, withdrawal and task changes remain effective.

Context guidance distinguishes historical evidence from applicable user preferences and work agreements. Current agreements should inform the plan and remaining steps after tool completion, within their conditions and authorization. This does not introduce an autonomous background executor or turn all historical text into instructions.

Retains the 1.0.4 details page, manual check, silent automatic updates and strict save receipts. Bilingual guides, project records, version descriptions and download links are synchronized to 1.0.5.

Focused synthetic checks cover the original continuation regression, persisted recall through a real local Python worker, deletion, task changes and save receipts, alongside the existing release checks. Archive round-trip and publication scans pass. No private memory database, real recording or paid API was used. Actual model-driven note creation and installation into the user's live Host were not verified.

The existing startup and six-hour checks remain active, with installation handled by the Host manager. A manual check is available under Memory → Details. Mirrors may lag; the updater selects the newest valid available release. Save work and reload when the Host requires it, then confirm the running version.

Build: 2aebd4004badabdc

SHA-256: 54eda2bb029f0d9b3c3fd32bacbda43249e33b91ad6ad16d0af76fba42067337