@yunyv/dsh-message-edit
为 DeepSeek Harness 对话提供基于分支的编辑、重新生成、重试和版本导航功能（兼容 DSH 0.1.0-rc.6 / rc.7+）
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @yunyv/dsh-message-edit@0.2.8Message Edit 以 @yunyv/dsh-message-edit 发布，当前版本为 0.2.8。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Event-sourced message editing, rerolling, retrying, and version navigation for DeepSeek Harness. The plugin never rewrites history events and never touches the DSH engine internals: every edit, reroll, or retry forks a new session version before the target turn, while the original session is always preserved and can be switched back to at any time.
message-edit/version) carry ignorable: true on the event
envelope: newer DSH builds skip unknown event types marked ignorable instead
of refusing the entire log, so session history stays loadable across DSH
upgrades.assistant.reasoning thinking blocks,
and assistant.response reply text are all editable.truncate (default): re-execute only the target input, dropping the old
tail after that point.preserve: keep the following user inputs and re-execute them in order on
the new branch; assistant outputs and tool chains are fully regenerated.← in the session title bar undoes the current atomic
effect, → re-applies the latest direct child effect; the Timeline shows the
full known branch tree, operation time, before/after content, and the
current version.conversation.view, order: 15, between
Trajectory (10) and Prompt Studio (20).# npm
dsh plugin --profile web add @yunyv/dsh-message-edit
# or GitHub
dsh plugin --profile web add github:yunyv/dsh-message-edit
# or local development (link mode)
dsh plugin --profile web add -w link:/path/to/dsh-message-edit
dsh plugin is a pnpm forwarder: after add, the dsh.bundle declaration is
recognized and the plugin is adopted into the profile's dsh.profile.bundles;
restart dsh for it to take effect.
The plugin treats a complete turn as the atomic effect. The target turn's
turn/start, model request, tool calls, tool results, and turn/end are never
partially copied and spliced; a new version forks from a closed boundary before
that turn:
preserve, the following user inputs are re-executed in order, producing a
fresh tool chain.message-edit/version effect pair:
effect records the forward effect, inverse records the restore target.
The parent chain derives composite inverses automatically; restoring is not
event deletion but switching along the inverse chain to a version that still
exists.runMaintenance(), take an immutable seed from
the closed boundary; before the first turn, use an empty seed.ctx.agents.create({ seed, meta }).
The Session validates the whole seed once before Agent construction; any
failure is structurally reverted by AgentFactory, so observers never see a
half-built Session and the Agent's turn count initializes directly from the
full history.ctx.sessions.flush() after publishing, establishing a durability
barrier before the HTTP operation succeeds.child.agent.followup().This path never touches ReactLoopAgent, AgentLoop private methods, or
apiproxy's narrowed fork RPC; branch seeds still pass through the same public
Session event contract.
sessions, agents, sessionPersistence,
sessionQuery, workspaceRegistry, and webServer services.slots, conversation, connection, and runtime
sessions services.sessionId; the controller reactively subscribes to the current Session's
closed turns and the lineage values in the Session list, rebinding on
Session identity replacement without caching stale Session objects.ctx.sessions.open(); availability changes drive
navigation directly.Each plugin version contains one message-edit/version event in its own
non-inherited suffix:
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
}
}
The session header's parentSession builds the version tree and must match
inverse.sessionId; seedLength separates the current version's own metadata
from same-named events inherited from ancestors. The Timeline derives the full
value-level projection via ctx.sessionQuery.traceSession() and
readSession(), and exports undoStack and direct redoSessionIds from the
atomic inverse chain. Legacy flat events remain readable and normalize to the
same effect pair in the projection.
conversation.view
id: message-edit-timelineorder: 15label: Timelineconversation.session.header.actions
id: message-edit-controlsconversation.chat.assistant-actions
id: message-edit-assistant-actionsmessageId dispatch); user messages have no such slot and are
covered by DOM injectionComponents use CSS Modules and --dsw-* semantic tokens with no UI library.
Product copy is Chinese; code comments are English.
GET /message-edit?sessionId=<id>: readable messages, retryable turns, and
the full version tree.POST /message-edit: run edit, reroll, or retry; returns the newly
published Session ID.npm install
npm run build
Source lives in src/ (host at src/index.ts, browser at src/client/); the
build script is scripts/build.mjs on top of esbuild + lightningcss:
src/index.ts → index.mjs (ESM, @deepseek-ai/* external)src/client/index.ts → client.js + client.js.map
(window.__ModuleLoader__.load closure factory; CSS Modules are compiled by
lightningcss into a hashed class map plus idempotent <style data-plugin>
injection)npm run typecheck (tsc --noEmit) validates types; npm run build emits
both halves.
MIT — see LICENSE.