gordonlu/dsh-context-lens
Request Context Profiler for DeepSeek Harness — see what changed between model requests, and how cache reuse c
dsh-context-lens is a Request Context Profiler that answers one question continuously: what did the harness send the model this time, and what changed since the last request? For every real LLM request it records a compact card: request identity (turn:step, provider, model, context window, status), the committed request context (canonical fingerprints of system prompt, tool set with per-tool schema hash and estimated tokens, request config, tool declaration order — only state actually committed to a real request is compared), a cache-reuse readout computed strictly from the provider's disjoint usage buckets (uncached input + cache reads + cache writes = billed input; missing fields stay absent, never zero), and a diff vs the previous request (model/provider/config/system/tool set +added/−removed/~modified, order, estimated surface delta, cache-reuse boundary in percentage points). A drop alarm fires across a threshold with a ranked list of coincident changes — correlation, never causation, with an explicit disclaimer. The change-first view adds a session status strip, a recent-requests list (up to 100), and an inspector with a line-by-line comparison; accuracy boundaries are explicit about what it never claims (internal cache keys, KV-causality breakpoints).
Install
dsh plugin --profile web add dsh-context-lensnpm dsh-context-lens 0.2.2 verified 2026-09-02 (repository field → github.com/gordonlu/dsh-context-lens; README EN primary). Install per README: dsh plugin --profile web add dsh-context-lens. The plugin is an npm package with a single runtime dependency (zod); all @deepseek-ai/* references are type-only. Open any conversation, switch to the Request Context tab, and watch every model request get one line.
Compatibility
DSH web profile (server unit + client view slot conversation.view, zh/en); pure observer — reads the session log, adds nothing, never touches a model call.
Details
- Repo: gordonlu/dsh-context-lens
- Category: Agent Capabilities
- Stars: 1
- Version: npm dsh-context-lens 0.2.2
- Last push: 2026-09-14
- First seen: 2026-08-13
Recent updates
Per-request context fingerprint + diff; cache-reuse readout from usage buckets; drop alarm with correlation-only attribution; Request Context tab; zh/en view; pure observer.
FAQ
- Does it modify requests or calls?
- No — it is a pure observer: it reads the session log, adds nothing to it, and never touches a model call; only state committed to a real request is compared.
- How is cache reuse measured?
- Strictly from the provider's disjoint usage buckets — uncached input + cache reads + cache writes equals billed input; missing fields stay absent rather than reading as zero.
- Does it claim which change caused a cache drop?
- No — the drop alarm lists coincident changes ranked by correlation with an explicit disclaimer; it never claims causation or the provider's internal cache-key construction.
Alternatives
ArtificialNotImbecile/dsh-context-taxonomy · EvilIrving/dsh-context-proxy · GooodWei/context-vista