@deepseek-ai/dsh-session-log-export

@deepseek-ai/dsh-session-log-export

English | 中文

Web Session-log download control over the host-streamed ZIP endpoint owned by dsh-host-apiproxy. The Host half registers /export; the browser half owns a 111×32 Session log action in the Session Header, one download controller, and one modal shared by that button and the slash command. ZIP generation, raw JSONL/zstd reads, descendants, attachments, backpressure, and HTTP error semantics remain owned by the ApiProxy download implementation.

Command contract

Input	Result
/export	Record a human-command lifecycle; the submitting browser receives the local execution acknowledgment and downloads GET /api/session.export?sessionId=&includeDescendants=true.
`/export
`	Return an error. Browser downloads choose their destination through the browser's ordinary download behavior.

The command is mounted only by the Web bundle. The local command/executed acknowledgment triggers the slash download only after a successful /export result in the browser that submitted it; other tabs still render the durable command row without repeating the browser side effect. The Header button calls the same controller directly. Both entry paths issue a HEAD preflight, then hand the GET URL to the browser download manager without buffering the ZIP in JavaScript; they share in-flight collapsing, cancellation of the preflight on plugin disposal, preparation-error handling, browser save behavior, and the same Modal.

The Host download endpoint flushes a live root Session before readRaw, so a slash-triggered ZIP includes the command/run and command/done pair whose acknowledgment started the download. Cold persisted Sessions require no flush.

The modal reports preparation, download start, or failure. Closing it does not cancel an in-flight download and does not reopen it when that operation later settles. One Session admits one active download at a time; repeated gestures share that operation.

Composition

- id: session-log-download
  name: '@deepseek-ai/dsh-session-log-export'

The Web bundle mounts the package beside dsh-host-apiproxy, dsh-commands, dsh-client-ui-commands, and dsh-client-ui-conversation. The package contributes its button and modal to the right-aligned conversation.session.header.utilities list, independently of the title-adjacent mode, Subagent, and Task entries in conversation.session.header.actions; a right margin keeps the button clear of the frame-wide workbench toggle, and Trajectory carries no export control.

Model Experience

Human /export control

What the model sees

Nothing. /export stays on the human-command plane, and the ZIP download does not enter model history.

Token effect

Zero. The command creates no model turn.

KV Cache effect

None. The log-only command lifecycle and browser download do not change the derived request prefix.

Known Limitations and Deferred Work

• The download endpoint requires a persistence backend with a per-Session raw artifact. The shipped JSONL backend supports plaintext and zstd artifacts; SQLite export is not included in this change.
• This is a browser download, not a Host-path writer. The browser chooses the local destination; no Host path or native folder action is returned.
• The preflight reports failures found before ZIP streaming starts. A descendant or attachment failure after the browser accepts the GET is reported by the browser download manager, not by the modal.