[Plugin] dsh-session-migrate — drag-and-drop session migration between workspaces #4845
ailiasdesu
started this conversation in
Show Your Plugins!
Replies: 4 comments
|
这个方向很实用,尤其是把“冷 Session”作为第一版边界,比尝试在线搬迁要靠谱得多。我按当前实现和上游 Workspace/JSONL 契约做了一轮源码审查,建议先明确标为 experimental,并优先补下面几项再让用户迁移不可替代的 Session:
在官方迁移 API 出现前,我会把“fork into a new rooted Session”作为默认安全路径,把本插件定位为只针对可恢复副本的实验工具。 我维护一个 DeepSeek Harness 社区 Handbook(与该插件无隶属关系),也把这轮审查整理成了可复用的迁移验收清单;待发布后会附链接,方便后续实现逐项打勾。 |
0 replies
|
补充:上述迁移安全契约已经发布在 Handbook 的 Session groups / storage migration section(v0.5.197)。清单是从当前上游公开 Workspace 契约提炼的,欢迎直接用于 issue/roadmap;如果实现更新,我也会按新证据修订。 |
0 replies
|
感谢 @liyangbing 的深度审查,全部采纳并在 cf35193 整改:
再次感谢!也期待您的迁移验收清单,后续逐项打勾。 |
0 replies
|
📦 插件已升级并更名:
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
dsh-session-migrate — migrate DSH sessions between workspaces straight from the Web UI settings panel, with drag-and-drop, automatic backup, and automatic rollback.
What it does
~1.9M-event logs) to another workspace with one drag & dropcwdchangesHow it works
workspaceRegistryservice (indexHeader→attachSession→detachSession) so session ownership (canonicalcwd) stays consistent with DSH's own semanticsnode:zlib— zero runtime dependency; directory naming (encodeSegment/projectKey) is kept in lockstep withdsh-session-persistence-jsonl, sosession.listnever sees a corrupt logctx.slots(official UI extension pattern), pure-DOM drag-and-dropInstall
Restart DSH, then open Settings → 会话迁移 (Session Migration).
Verification
plugin_checkpasses (bundle form); verified on a live DSH instance (list + migrate endpoints)Repo: https://github.com/ailiasdesu/dsh-session-migrate
Topics:
dsh-plugindeepseek-harnessdshAll reactions