dsh-har-triage
为 DeepSeek Harness 提供离线 HAR 诊断和最少证据
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:po-et/dsh-har-triage#12a95b54513553dabc8dabc1661362226bf6d004
Har Triage 以 dsh-har-triage 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Offline network evidence for DeepSeek Harness. Find failed and slow browser requests without handing the agent your URLs, cookies or response bodies.
浏览器网络排障插件：读取本地 HAR，生成可回查原始请求索引的离线诊断报告。默认不把网址、请求头、Cookie、参数值或正文带进报告和 AI 工具结果。
Synthetic HAR diagnosis: signals, source indexes and timing evidence
The screenshot uses the bundled synthetic scenario, not real browser traffic.
Request #43 corresponds to log.entries[42] in your original HAR. Endpoint aliases deliberately do not reveal names. Keep the original capture private and use its index to look up the actual request locally.
Node 22.19+ is required. Install the prebuilt bundle into your chosen profile:
dsh plugin --profile YOUR_PROFILE add https://github.com/po-et/dsh-har-triage/releases/download/v0.1.0/dsh-har-triage-0.1.0.tgz
dsh --profile YOUR_PROFILE --dump-config
The configuration should contain the har-triage row. Start that profile, put your HAR inside its session workspace, and ask:
Inspect capture.har with har_triage. Save reports in a new har-review directory. Explain the measured evidence and cite the original HAR entry indexes. Do not guess root causes.
Tool arguments:
{"input":"capture.har","outputDir":"har-review","slowMs":2000}
The tool uses Harness filesystem and sandbox services. It requires write permission to create the reports and refuses input/output paths outside the session workspace. Existing report files are never overwritten. Uninstall with dsh plugin --profile YOUR_PROFILE remove dsh-har-triage.
The CLI and analysis/report modules use Node built-ins only. From a source checkout:
node src/cli.js capture.har --out new-report-directory --slow-ms 2000
Open new-report-directory/report.html. The output directory must not exist. The original capture is unchanged.
For a reproducible synthetic example:
npm run demo
This creates a new directory under artifacts/ with a deliberately synthetic capture and its report. It is not evidence of real browser traffic or real users.
503 means the capture records a server-error response. status: 0 means it did not record a valid HTTP response. Neither identifies a failing service, proves CORS, or proves an expired token. A high wait/TTFB share is an observation, not proof that the backend or database is slow.
Unknown phase timings and byte sizes remain -1, displayed as “Unknown.” TLS is part of the HAR connection timing and is not added a second time. Contradictory phase durations are flagged; the report hides misleading proportions.
Retained: source entry index, sequential endpoint alias, controlled method/status/content classes, relative offsets, numeric durations/sizes, and fixed diagnostic codes. Aliases group the same method/origin/path within one capture; query strings and fragments do not affect grouping.
Removed: complete URLs including origins and paths, query values, headers, cookies, request/response bodies, page titles, initiator data, IP addresses, absolute timestamps, extension fields, raw error text, and the original file digest. The report ID hashes only the retained projection. Arbitrary source strings are not copied to reports or tool evidence.
This is a minimal diagnostic projection, not a scrubbed HAR, an anonymization guarantee, or a replacement for reviewing an artifact before sharing it. Status patterns, sizes, timing, request counts and grouping can still identify an application. See SECURITY.md.
1.2, UTF-8, at most 16 MiB and 10,000 entries. Invalid supported entries fail with fixed errors rather than silently truncating the evidence.npm ci --ignore-scripts
npm test
npm run smoke:host
npm pack --dry-run
48 tests passed on Node 24 and 26. They cover actual CLI subprocesses, controlled output and failure text, input limits, phases, original-file preservation, and real Cordis tool dispatch/filesystem/sandbox/Loader integration. smoke:host is a real service composition, not a CLI profile boot or a live-LLM test.
The packed bundle was separately installed through the actual CLI into fresh temporary Profiles on Harness 0.2.0-rc.2 and 0.2.1-alpha.2, then booted with runProfile and exercised through har_triage. Source bytes were unchanged; output omitted the synthetic canary; overwrite and workspace-escape attempts were refused. HMR was disabled only in those temporary Profiles. The alpha host emitted three unrelated Typert activation warnings; rc.2 did not. No LLM or real credentials were used.
Browser checks covered status filtering, signal-to-request navigation, correct source locators, no console errors, and a 390-pixel layout without page-level overflow. The demo and regression captures are synthetic; real-user usefulness is not yet validated.
net-debug is an existing Harness HTTP client with history, replay and HAR export. harlite already offers extensive HAR analysis, SQL, waterfall and HTML reporting. This plugin does not replace those tools: its narrower purpose is a Harness-native, no-external-binary, allowlisted evidence path for agent-assisted debugging.
MIT licensed.