In this article
A local desktop conversation establishes model loading and supplied context; editor serving and optional tools remain separate integrations.
Start LM Studio by proving one complete local conversation before connecting an editor or adding tools. The useful first result is a repeatable assistant on your computer, with a known model source and a conversation you can reopen.
The concrete application boundary
The desktop starting point combines model discovery, loading, and a chat interface. These operations have a useful order: a file must be available before the runtime can use it, and the conversation must select the intended model before its answer can be assessed. The first exercise should therefore stay within the application window. Uploading documents, connecting MCP servers, or configuring an editor would add independent behavior to a task that has not yet established its baseline. Keep the supplied text short enough to read beside the answer. You should be able to point to the source of each asserted fact without relying on the model’s confident tone (LM Studio application guide) (LM Studio, llmster, and lms).
A practical route
Download or import a supported model through the application, select it, and wait for loading to finish. Ask for a short explanation of a harmless text. Follow with a question referring to that answer. Keep the initial conversation free of document retrieval, external tools, and remote providers so that an unexpected result has fewer possible owners.
A worked example
Use a fictional meeting note: a review is postponed because its author is absent. Ask the assistant to produce an action list, then ask who owns the unresolved decision. The second response tests whether the conversation supplied the relevant context. It does not establish factual knowledge beyond the note or demonstrate reliable autonomous planning.
| Check | Record |
|---|---|
| Input | The fictional note and both questions, with personal information excluded. |
| Selection | The actual model identifier and the application version used for this conversation. |
| Result | The action list, the follow-up answer, and any assumptions introduced by the assistant. |
Reading the failure correctly
If loading fails, solve the model loading problem before changing prompts. If the response invents a participant, inspect the supplied text and record the unsupported assumption. If an editor later fails, preserve this successful desktop baseline: replacing the model immediately would discard useful evidence about which layer changed (LM Studio developer documentation).
What completes the check
Reopen the conversation and repeat the task in a fresh chat with the same selected model. A concise setup note should let you explain where generation happened, what remained local, and which optional network features were absent from this particular check. Give the conversation a recognizable name for reopening.
Related background: llama.cpp server: a local API from a GGUF model, VRAM for LLMs: why model size is only part of the calculation.