Experimental. Local inference (Ollama, LM Studio, llama.cpp) is less reliable than remote APIs and depends on your hardware and the model you load. See Local Models guide for trade-offs, hardware sizing, and a "getting reliable results" checklist. VT Code now detects a stopped server or an unloaded model before generating and prints the exact recovery command (e.g.
ollama pull <model>or/local start <provider>).
VT Code manages local LLM inference servers through the /local command. Control Ollama, LM Studio, and llama.cpp directly from the TUI.
/local Open interactive server manager
/local status Check all local servers
/local start ollama Start a specific server
/local troubleshoot Diagnose issues
| Provider | Default Endpoint | Binary | Install |
|---|---|---|---|
| Ollama | http://localhost:11434 |
ollama |
brew install ollama |
| LM Studio | http://localhost:1234/v1 |
lms |
https://lmstudio.ai/download |
| llama.cpp | http://localhost:8080/v1 |
llama-server |
https://llama.app |
llmman serves the Ollama API on port
17434 and works through the ollama provider; see
Using llmman below.
# macOS
brew install ollama
# Linux
curl -fsSL https://ollama.com/install.sh | sh
# Windows
# Download from https://ollama.com/downloadollama serveOr use VT Code: /local start ollama
ollama pull gemma3
ollama pull qwen3.5:7b
ollama pull llama3.1:8bollama run gemma3ollama lsollama psollama stop gemma3curl http://localhost:11434/api/tagscat ~/.ollama/logs/server.log| Variable | Description | Default |
|---|---|---|
OLLAMA_BASE_URL |
Server URL | http://localhost:11434 |
OLLAMA_HOST |
Listen address | 127.0.0.1:11434 |
/local ollama Open Ollama actions in TUI
/local status ollama Check if Ollama is running
/local start ollama Start the Ollama server
/local configure ollama Show environment config
/local troubleshoot ollama Diagnose connection issues
llmman is a local model runner that
serves the Ollama API (alongside OpenAI- and Anthropic-compatible ones) on port
17434. Models are pulled as OCI artifacts or straight from Hugging Face
(hf.co/org/model) and served by upstream llama.cpp, vllm, or mlx-lm.
Because the API is the same, VT Code's ollama provider works unchanged; only
the base URL differs.
# Install and start
curl -fsSL https://raw.githubusercontent.com/llmmanorg/llmman/main/install.sh | sh
llmman serve
# Pull a model
llmman pull gemma4
llmman pull hf.co/unsloth/Qwen3.5-0.8B-GGUF
# Point VT Code's ollama provider at llmman
export OLLAMA_BASE_URL=http://localhost:17434
vtcode --provider ollama --model gemma4Override the listen address on the llmman side with LLMMAN_HOST
([host][:port]), then set OLLAMA_BASE_URL to match.
llmman does not serve /api/embed; embeddings are only available via its
OpenAI-compatible /v1/embeddings route. /local start ollama manages the
ollama binary, not llmman, so start llmman serve yourself.
Download from https://lmstudio.ai/download (macOS, Windows, Linux).
The lms CLI ships with LM Studio. Verify:
lms --helpIf lms is not on PATH, it may be at ~/.lmstudio/bin/lms.
lms server startOr use VT Code: /local start lmstudio
Custom port:
lms server start --port 3000Bind to all interfaces (for network access):
lms server start --bind 0.0.0.0lms server stoplms server status
lms server status --json --quietlms get gemma3
lms get deepseek-r1
lms get qwen2.5-7b-instruct --mlxlms lslms pslms load
lms load openai/gpt-oss-20b --identifier="my-model"lms unload
lms unload --all- Open LM Studio app
- Go to Settings (Cmd+,)
- Enable "Run LLM server on machine login"
- Exit the app -- it runs in the background
| Variable | Description | Default |
|---|---|---|
LMSTUDIO_BASE_URL |
Server URL | http://localhost:1234/v1 |
/local lmstudio Open LM Studio actions in TUI
/local status lmstudio Check if server is running
/local start lmstudio Start the server via lms CLI
/local configure lmstudio Show environment config
/local troubleshoot lmstudio Diagnose connection issues
# macOS (Homebrew)
brew install llama.cpp
# Or download from https://llama.app
# Build from source
git clone https://github.com/ggml-org/llama.cpp
cd llama.cpp
cmake -B build
cmake --build build --config ReleaseThe server binary is llama-server.
llama-server -m /path/to/model.gguf --port 8080Or use VT Code (auto-start): set LLAMACPP_MODEL_PATH and VT Code manages everything.
curl http://localhost:8080/healthcurl http://localhost:8080/v1/modelsDownload .gguf files from https://huggingface.co or https://llama.app/models:
- https://llama.app/models/Qwen3.6-27B
- https://llama.app/models/gemma-4-26B-A4B
- https://llama.app/models/gpt-oss-20b
- https://llama.app/models/Step-3.5-Flash
Set LLAMACPP_MODEL_PATH to a .gguf file. VT Code will:
- Detect the model path
- Start
llama-serverautomatically when needed - Wait for the server to be ready
- Connect and serve requests
export LLAMACPP_MODEL_PATH=/path/to/model.ggufPass additional arguments to llama-server:
export LLAMACPP_EXTRA_ARGS="--ctx-size 4096 --n-gpu-layers 99"| Variable | Description | Default |
|---|---|---|
LLAMACPP_BASE_URL |
Server URL | http://localhost:8080/v1 |
LLAMACPP_MODEL_PATH |
Model file for auto-start | (none) |
LLAMACPP_BINARY_PATH |
Path to llama-server |
search PATH |
LLAMACPP_EXTRA_ARGS |
Extra server arguments | (none) |
LLAMACPP_STARTUP_TIMEOUT_SECONDS |
Startup timeout | 60 |
/local llamacpp Open llama.cpp actions in TUI
/local status llamacpp Check if server is running
/local start llamacpp Start server (requires LLAMACPP_MODEL_PATH)
/local configure llamacpp Show environment config
/local troubleshoot llamacpp Diagnose connection issues
/local
Opens an inline modal showing all providers with status. Select a provider to see actions.
/local status Check all servers
/local status ollama Check Ollama only
/local start ollama Start Ollama
/local start lmstudio Start LM Studio
/local start llamacpp Start llama.cpp
/local stop ollama Stop Ollama
/local configure Show all env vars
/local configure llamacpp Show llama.cpp config
/local troubleshoot Diagnose all servers
/local troubleshoot ollama Diagnose Ollama
/local ollama Open Ollama actions
/local lmstudio Open LM Studio actions
/local llamacpp Open llama.cpp actions
/local ollama status Check Ollama status
lm-studio,lm_studio->lmstudiollama.cpp,llama-cpp,llama_cpp->llamacpp
- Check if binary is installed:
/local configure <provider> - Try starting:
/local start <provider> - Run diagnostics:
/local troubleshoot <provider>
# Check if running
curl http://localhost:11434/api/tags
# Start manually
ollama serve
# Check logs
cat ~/.ollama/logs/server.log# Check status
lms server status --json
# Start server
lms server start
# Open the app
open -a "LM Studio"# Check health
curl http://localhost:8080/health
# Check model path
echo $LLAMACPP_MODEL_PATH
# Check binary
which llama-server- Local Models guide — trade-offs, hardware, reliable-setup checklist
- Ollama Provider Guide
- LM Studio Provider Guide
- llama.cpp Provider Guide