docs(llm): document LM Studio / remote GPU box as an LLM backend - #174
Open
BrettKinny wants to merge 1 commit into
Open
docs(llm): document LM Studio / remote GPU box as an LLM backend#174BrettKinny wants to merge 1 commit into
BrettKinny wants to merge 1 commit into
Conversation
A recurring support question: "can I run the LLM in LM Studio on my Windows GPU box?" The answer is yes with no code changes — OpenAICompat already speaks that wire format — but nothing in the docs said so concretely, and the CUDA block in docker-compose.yml.template reads as if a GPU on the Docker host were a prerequisite for the LLM. - docs/llm-backends.md: new "LM Studio (or any inference box on another machine)" subsection under the OpenAI-compatible backend, with a worked config and the three failure modes that account for most "it won't connect" reports (loopback vs LAN IP, LM Studio's localhost-only default binding, host firewall). Adds the /v1/models curl as the pre-flight check and notes that `make doctor` does not validate the model id. - docs/llm-backends.md: state explicitly that the Docker host needs no GPU for this, and distinguish compose.local.override.yml (Ollama on the Docker host's own GPU) from serving models off a second machine. - docs/llm-backends.md: note that switching off PiVoiceLLM makes the docker.sock + docker CLI mounts unnecessary, and that they should be removed — the socket mount is root-equivalent on the Docker host. - docs/llm-backends.md: comparison table's "Runs where" / "Privacy" rows no longer imply the OpenAI-compatible backend is cloud-only. - docker-compose.yml.template: mark the CUDA block ASR-only. Docs only — no behaviour change. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A recurring support question from new users: "Can I run the LLM in LM Studio on my Windows PC that has the GPU?"
The answer is yes, with no code changes —
OpenAICompatalready speaks that wire format — but the docs never said so concretely.docs/llm-backends.mdmentioned LM Studio only in a passing list, and every worked example was OpenRouter / Anthropic / llama-swap. Worse, the CUDA block indocker-compose.yml.templatereads as though a GPU on the Docker host were a prerequisite for the LLM, when it only ever governed WhisperLocal ASR. Users were also conflatingcompose.local.override.yml(Ollama on the Docker host's own GPU) with serving models off a second machine.What changed
Docs only — no behaviour change, no code touched.
docs/llm-backends.md.config.yamland the three failure modes behind most "it won't connect" reports:curl http://<GPU_BOX_IP>:1234/v1/modelsas the pre-flight check; it doubles as the way to get the exact modelid. Noted thatmake doctordoes not validate that value, so a typo surfaces at runtime as "My brain returned an error" from the robot.compose.local.override.ymlfrom the remote-inference case.PiVoiceLLMmakes thedocker.sock+ docker CLI mounts unnecessary, and that they should be removed — the socket mount is root-equivalent on the Docker host, so dropping it when nothing uses it is a real reduction in blast radius.docker-compose.yml.templatedocs/llm-backends.md.Notes
Last verified:at the foot ofllm-backends.mdis deliberately unchanged — only theOpenAICompatmaterial was re-checked against the code this pass, not the llama-swap or PiVoiceLLM sections.custom-providers/openai_compat/openai_compat.pyand.config.yaml.template; the mount advice againstcompose.all-in-one.yml.AI assistance
Drafted with Claude Code in response to a user support question; reviewed by @BrettKinny before merge. See
AI_TRANSPARENCY.md.🤖 Generated with Claude Code
https://claude.ai/code/session_01Pqs9dxTt13WHG1GynHTXax