dsh-llm-trace

LIMITATIONS

Known limitations

- **Secrets in bodies are not redacted.** Header redaction covers the credential headers; the request body still carries the full system prompt, every tool schema, and any file content the agent read. Both surfaces sit behind the Web host's loopback bind plus its browser-session cookie check, which is the only access control. - **`path` is not shared with the client.** The tab fetches a constant, so a non-default mount path needs a matching edit in `lib/client.js`. - **The wrapper is process-global and order-dependent.** `@deepseek-ai/dsh-experimental-inspector` wraps the same global; running both nests the wrappers and captures every exchange twice. - **A `fetch` reference cached before this plugin activates is not observed.** `dsh-llm-pi-ai` constructs its provider client per request, so it is covered; another adapter that caches the reference at load would not be. - **Calls made outside a loop carry no session id.** A hand-built `llm.stream()` call without `sessionId` is captured but appears only in the HTTP viewer. - **Binary bodies are byte-counted only.** - **The assembled view decodes OpenAI-style SSE only.** A provider using a different streaming envelope falls back to the raw view, which is always available.