dsh-request-flight-recorder

Debugging model requests inside DeepSeek Harness creates a tension: you need to inspect structural details of every request without leaving prompt text, tool arguments, or variable values in any log. dsh-request-flight-recorder resolves this by observing official Agent Loop requests through Cordis, correlating request assembly with stream completion, and retaining a bounded in-memory flight history that contains no message content.

The plugin delivers capability in three layers. Diagnostics: it records session, turn, and step coordinates alongside provider, model, generation settings, structural message counts, tool schema sizes, time-to-first-chunk, total duration, token usage, finish reason, and structured failure state. Privacy: an explicit field allowlist retains only structural names and counts; raw error messages, stacks, and thrown values are discarded. The bounded Ring Buffer clears on process exit and never writes to disk. Interaction: when the active profile exposes the Commands service, a /flight command lets you inspect the latest record, list retained entries, run an implicit diff between the two newest, and view session-scoped stats, with output capped at 4,096 UTF-16 code units.

It is aimed at Harness administrators and integration engineers who need to profile streaming latency, verify the structural impact of prompt changes, or audit request lifecycles across multiple profiles. The plugin registers no Tool, Skill, prompt section, or context provider, and does not alter Agent Loop semantics, offering a minimally invasive, process-local, read-only flight recorder.