dsh-message-edit

One-Line Description

Adds revokable message editing, regeneration, retry, and branch version navigation capabilities to DeepSeek Harness conversations. It commits each modification as an independent conversation version, keeping the original session untouched and deletable, allowing you to switch back to old versions anytime.

Core Features

• Edit three types of text blocks: confirmed user messages, assistant thinking blocks, and assistant response blocks
• One-click regeneration of the latest confirmed assistant response, reusing the original user input
• Re-execute (Retry) any historical turn in the Timeline
• Supports two cascade strategies: truncate (default, discards old follow-ups) and preserve (carries subsequent user inputs into the new branch in order)
• Session header provides undo (←) and redo (→) buttons, switching current version by atomic effect unit
• New Timeline tab displays complete branch tree, operation timestamps, before/after edit content, current version, and retryable turns

Technical Implementation

• Language: TypeScript (ESM), build outputs index.mjs (Host) and client.js (Browser)
• Key Dependencies: @deepseek-ai/dsh-agent, @deepseek-ai/dsh-session, @deepseek-ai/dsh-session-query, @deepseek-ai/dsh-workspace
• Architecture Pattern: Cordis plugin dual-end structure. Host registers HTTP route /message-edit for timeline reading and edit execution; Client registers conversation.view and conversation.session.header.actions two slots via slots. Event sourcing: each branch appends message-edit/version events, effect/inverse pairs stored, inverse chain automatically composed by parent version
• Entry Files: Host entry src/index.ts (apply(ctx) registers HTTP routes), Client entry src/client/index.ts (registers two UI slots)

Use Cases

When you collaborate with the model for long sessions using DSH, are unsatisfied with an old response, or want to try different branch directions at the same point with a different prompt—this plugin lets you branch from any historical turn to continue without starting a new session. The original session is always preserved and can be switched back to anytime. Ideal for power users who need to iteratively refine the same conversation structure without losing previous work.

Prerequisites & Compatibility

Installation

dsh plugin --profile web add github:Moeblack/dsh-message-edit

Configuration

This plugin requires no additional configuration. Model routing (provider, model, maxTokens) is automatically read from the current session's request headers by the plugin—no manual specification needed.

FAQ

Q: Do Edit, Regenerate, and Retry operations rewrite the original session?

A: No. The plugin never rewrites Session events in place. The original session remains as an immutable append-only log, and each operation branches off a new conversation version from before the target turn.

Q: What's the difference between truncate and preserve cascade strategies?

A: truncate only re-executes the target input in the new version after branching and discards old follow-ups; preserve also carries unexecuted user inputs after the target into the new branch, running through the subsequent turn's tool chain in order.

Q: Does undo/redo really delete events?

A: No. Each operation appends an effect/inverse pair event. Undo simply switches along the inverse chain to an existing old version; the branched version is still retained in the version tree and can be switched back to.

Q: What content can be edited?

A: Only confirmed text blocks are supported—user message body, assistant thinking block, and assistant response body. Other content blocks like images, tool calls, and attachments are not editable.

Q: Does editing a message affect workspace files or artifacts?

A: No. The plugin explicitly only manipulates session events and derived Agents, with no联动 to restore or modify workspace files, command external effects, or existing artifacts.

Q: Where is the Timeline tab positioned?

A: Registered in the conversation view's conversation.view slot with order 15, positioned between Trajectory (10) and Prompt Studio (20).

Difficulty Level

Beginner — Edit, Regenerate, and Undo buttons are all visual controls, no configuration needed during conversation; understanding truncate/preserve and version branching takes a few minutes but isn't required for daily use.

Known Issues & Limitations

• Editing images, tool calls, attachments, and other non-text blocks is not supported; only user message body, assistant thinking, and assistant response text blocks can be modified
• Does not restore or modify workspace files, command external effects, or existing artifacts—branch switching does not rollback these side effects
• Does not modify DSH engine, apiproxy, or official UI packages; plugin only collaborates via Host's public services and Browser slots
• Branch operations will fail due to unresolved model routing when historical request header configuration (provider, model) cannot be located
• Old flat version events (missing schemaVersion) can still be read and normalized during projection, but internal schema version has been upgraded to 2

dsh-message-edit（npm · GitHub）为 DeepSeek Harness 补充基于事件溯源的「消息编辑与重生成」能力。插件不改写历史事件，也不修改 DSH 引擎内部；每次编辑、重生成或重试都会从目标回合之前创建一个新会话版本，原会话始终保留并可随时切回。

dsh plugin --profile web add dsh-message-edit

功能

• 编辑消息：可编辑已落定的用户文本、assistant.reasoning 思考块与 assistant.response 回复文本。
• 重生成：从最后一条已落定助手回复所属回合之前分支，使用原用户输入重新生成。
• 重试任意回合：在 Timeline 中选择任意历史回合重新执行。
• 级联策略：
  • truncate（默认）：只重新执行目标输入，删除该点之后的旧后续。
  • preserve：保留后续用户输入，并在新分支中依次重新执行；助手输出与工具链全部重新生成。
• 版本切换：会话标题栏的 ← 撤销当前原子效果，→ 重施加最新直接子效果；Timeline 展示完整已知分支树、操作时间、编辑前后内容与当前版本。
• Timeline 标签页：注册到 conversation.view，order: 15，位于 Trajectory（10）与 Prompt Studio（20）之间。

设计

时间可组合性

插件把完整回合作为效果原子。目标回合的 turn/start、模型请求、工具调用、工具结果与 turn/end 不会被局部复制后拼接；新版本从该回合之前的闭合边界分支：

1. 用户消息编辑、Reroll 与 Retry：回退整个目标回合，再把目标用户输入作为新回合交给 Agent。
2. 助手块编辑：回退整个目标回合，以原用户输入和编辑后的助手内容构造一个新的完整闭合回合；原工具链不进入新版本。选择 preserve 时，后续用户输入再依次交给 Agent，产生新的完整工具链。
3. 每个版本都追加一个不可拆分的 message-edit/version 效果对：effect 记录正向效果，inverse 记录恢复目标。父版本链自动导出组合逆；恢复不是删除事件，而是沿逆链切换到仍然存在的版本。
4. 消息历史变换彼此不交换，因此撤销遵循 LIFO：一次只撤销当前原子效果并保留更早效果；各后继分支始终保留，可从父版本重新施加。

分支与 Agent 接线

旧实现先用短生命周期 Session 暂存分支、落盘、移除 live Session，再用 agents.resume() 重建 Agent。这个过程存在两个分离的生命周期边界：暂存日志已经持久化后，Agent 仍可能创建失败。现实现只使用 AgentRegistry.create() 已公开的 seed + meta 事务缝：

1. 在来源 Agent 的 runMaintenance() 内，从已闭合边界取得不可变 seed；第一回合之前使用空 seed。
2. 用本地等价的纯事件构造器把版本效果对与可选手工助手回合加入 seed，再调用 ctx.agents.create({ seed, meta })。Session 在 Agent 构造前一次性验证完整 seed；任何一步失败都会由 AgentFactory 的结构性逆撤销，外部观察者看不到半成品 Session，Agent 的回合计数也直接从完整历史初始化。
3. 发布后调用 ctx.sessions.flush()，在 HTTP 操作成功前建立耐久性屏障。
4. Workspace 挂接与 child Agent 生命周期分别返回原子逆；操作失败时按相反顺序组合恢复。随后通过 child.agent.followup() 排入需要重新执行的用户输入。

此路径不接触 ReactLoopAgent、AgentLoop 私有方法或 apiproxy 的收窄 fork RPC；分支 seed 仍由同一 Session 公共事件契约验证。

空间可组合性

• Host 只依赖公开的 sessions、agents、sessionPersistence、sessionQuery、workspaceRegistry 与 webServer 服务。
• Browser 只通过 slots、conversation、connection 与 runtime sessions 服务组合。
• Timeline 与标题栏共享一个按 sessionId 建立的值级 Snapshot source；控制器反应式订阅当前 Session 的闭合回合值与 Session 列表中的谱系值，Session 身份替换时重新绑定，不缓存旧 Session 对象。
• 新版本导航等待 runtime Session 列表发布对应 ID 后再执行 ctx.sessions.open()，依赖可用性变化直接驱动导航。

数据模型

每个插件版本在自己的非继承后缀中包含一个 message-edit/version 事件：

interface MessageEditVersionEvent {
  schemaVersion: 2
  effect: {
    id: string
    operation: 'edit' | 'reroll' | 'retry'
    cascade: 'truncate' | 'preserve'
    targetTurn: number
    targetEventSeq: number
    targetBlockIndex?: number
    blockKind?: 'user' | 'assistant.reasoning' | 'assistant.response'
    before?: string
    after?: string
  }
  inverse: {
    kind: 'restore-version'
    sessionId: string
  }
}

会话头的 parentSession 构成版本树，且必须与事件中的 inverse.sessionId 一致；seedLength 区分当前版本自己的元数据与从祖先继承的同名事件。Timeline 通过 ctx.sessionQuery.traceSession() 和 readSession() 生成完整值级投影，并由原子逆链导出 undoStack 与直接 redoSessionIds。旧版平面事件仍可读取，并在投影时规范化为同一效果对。

UI

• conversation.view
  • id: message-edit-timeline
  • order: 15
  • label: Timeline
• conversation.session.header.actions
  • id: message-edit-controls
  • 直接父效果撤销、直接子效果重施加、效果链计数、最后回复重生成

组件使用 CSS Modules 与 --dsw-* 语义 token，不引入 UI 库。所有产品文案为中文，代码注释为英文。

构建

npm install
npm run build

构建基于 npm 发布的 @deepseek-ai/*@0.1.0-rc.6 类型与本地工具链（typescript、tsdown、lightningcss），不再依赖 dsh 源码树。构建生成：

• index.mjs：Host 插件
• client.js：Browser 插件
• client.js.map：Browser source map

安装

dsh plugin --profile web add dsh-message-edit

或本地开发：

dsh plugin --profile web add -w link:/path/to/dsh-message-edit

dsh plugin 是 pnpm 转发器：add 后会自动识别 dsh.bundle 声明并把插件收编进 profile 的 dsh.profile.bundles，重启 dsh 即生效。本地开发建议用 link:（符号链接），改动源码重构建后重启即更新。

HTTP 接口

• GET /message-edit?sessionId=<id>：读取可编辑消息、可重试回合与完整版本树。
• POST /message-edit：执行 edit、reroll 或 retry，返回已发布的新 Session ID。

范围边界

• 不原地改写 Session 事件；历史是 append-only、deep-frozen。
• 不联动恢复或修改工作区文件、命令外部效果与既有产物。
• 不修改 DSH 引擎、apiproxy 或官方 UI 包。