Repository navigation
Settings and Configuration
Kamil Maciag edited this page Oct 26, 2026
·
1 revision
Settings covers both the app itself and the underlying CLI config (~/.vibe/config.toml).
Most tabs (agents, MCP, tools, prompts, skills, providers, models, raw config) have a scope switch — Global or Project. Project scope uses the .vibe directory found by walking up from the current working directory (falling back to <cwd>/.vibe), exactly like the CLI.
- Add custom models with display name, provider, pricing — including cached-input pricing — temperature, top_p, max output tokens, context length, thinking levels and auto-compact threshold
-
display_nameis what the UI shows everywhere
- Create custom agents (system prompts, tools, allowed models); project agents live in
<project>/.vibe/agents/ - The agent dropdown merges project + global agents (global ones are marked)
- Add MCP servers with full CLI 3.x support: static auth (headers, API key env/header/format) or OAuth (scopes, client id, redirect port)
- Per-server raw JSON editing for anything the form does not cover; transport misconfigurations are prevented (legacy keys and the auth block are mutually exclusive)
- Startup/tool timeouts and cwd are configurable
- Browse skills with their file trees, read and edit
SKILL.md, create, import and delete skills
- View the CLI built-in tools when nothing is configured; manage custom prompts per scope
- Browse the
.vibeconfig tree and edit any TOML file directly in CodeMirror
- Language (EN/PL/FR/ES/DE/IT), theme, serve credentials — and the Statistics data source never leaves your machine