name: lmstudio-log-observability description: "Stream, capture, and inspect LM Studio local server, runtime, and model I/O logs. WHEN: "lms log", "LM Studio logs", "debug local LLM server", "capture model input output", "server log stream"." license: MIT metadata: author: ChatGPT version: "1.0.0"
LM Studio Log Observability
Use this skill to debug LM Studio local server behavior with repeatable lms log stream workflows.
Workflow
Verify CLI access
lms --help lms log stream --helpStart or confirm the local server
lms server start lms server statusChoose the log source
Goal Command Stream HTTP/server events lms log stream --source serverShort form lms log stream -s serverInspect prompt/model I/O lms log stream --source model --filter input,outputSave server logs lms log stream -s server | tee -a lmstudio-server.logSave JSONL logs lms log stream -s server --json | tee -a lmstudio-server.jsonlGenerate traffic from another terminal, client, or test harness.
Correlate failures by timestamp, endpoint, model identifier, response status, and whether the issue appears in server logs, model I/O, or runtime behavior.
Use installed CLI help as authority when sources differ. Some installs may expose extra sources such as
runtime; only use them iflms log stream --helplists them.
When More Detail Is Needed
- Use command recipes for capture, filtering, and replay commands.
- Use troubleshooting for common failure patterns.
- Use automation scripts when the user wants reusable capture commands.
Output Pattern
When responding, provide:
- The exact log command to run.
- The companion command that generates server traffic.
- The expected signal in the logs.
- A minimal next diagnostic step if no logs appear.