Configuration overview
Ta treść nie jest jeszcze dostępna w Twoim języku.
Configuration overview
Section titled “Configuration overview”Most user-facing configuration lives in Settings.
Each part of LM Nexus owns the settings it actually uses, so provider settings stay with providers, model defaults stay with Model Manager, and module-specific options stay with their module.
The Settings layout itself is still being improved, but those responsibilities are not changing.
Common configuration areas
Section titled “Common configuration areas”Current settings include areas such as:
- AI providers and compatible endpoints;
- Model Manager and model defaults;
- llama.cpp runtime behavior;
- Chat and agent preferences;
- Terminal and developer-tool integrations;
- Files, Notes, Knowledge, and productivity modules;
- keyboard shortcuts and UI behavior.
Where user and runtime data lives
Section titled “Where user and runtime data lives”Normal user/runtime data lives outside the source repository in per-user app-data, config, cache, or state locations.
That includes things such as model metadata, notes, knowledge, profiles, prompts, skills, runtime installs, logs, package state, and trust approvals unless you explicitly export them.
Settings redesign status
Section titled “Settings redesign status”The Settings shell and information layout are active Preview work.
The docs follow what is actually implemented today rather than documenting a design-only navigation structure as if it had already shipped.