Model Configuration
Use a model profile when you need more detailed control over model behavior than auto-discovery provides.
This workflow lets you configure model-specific settings such as:
context_windowtokenizer- tool support
- reasoning support
- image support
- sampling parameters
Use it when you want PrivateGPT to know the exact limits and capabilities of each model, or when you need to override what your provider exposes automatically.
This workflow is supported from the source-based Local with uv install:
- Generate
settings-model.yamlfrom your running LLM server. - Edit the generated profile.
- Start PrivateGPT with
PGPT_PROFILES=model.
Generate a model profile
Generate a profile from the models exposed by your OpenAI-compatible server:
macOS / Linux
Windows (PowerShell)
Windows (CMD)
This creates settings-model.yaml with all discovered models as a starting point for detailed configuration.
Start from Local with uv first. Local tokenizer support requires private-gpt[tokenizer-local] or private-gpt[core].
Edit model settings
Open settings-model.yaml and adjust the fields you care about. This is where you explicitly define how PrivateGPT should treat each model. Example:
Key fields reference
Run with the profile
Once settings-model.yaml exists, start PrivateGPT with PGPT_PROFILES=model.
macOS / Linux
Windows (PowerShell)
Windows (CMD)
PGPT_PROFILES=model tells PrivateGPT to load settings-model.yaml on top of the base config. Profile files follow the naming convention settings-{name}.yaml.

