Settings
Open the BIGGI sidebar and select the gear icon. Settings are grouped by the user task they affect.
Main settings
| Section | Controls |
|---|---|
| Providers | Provider credentials, OAuth connections, custom endpoints, and local providers |
| Models | Default chat model and model variants |
| Agent Behaviour | Agents, instructions, MCP servers, and workflows |
| Auto-Approve | Per-tool Allow, Ask, and Deny rules, plus the session cost alert |
| Browser | Optional Playwright browser automation and Chrome behavior |
| Checkpoints | Automatic snapshots before file edits |
| Autocomplete | Inline-completion provider, model, and trigger behavior |
| Context | Compaction, output pruning, file-watcher exclusions, and project memory |
| Indexing | Semantic codebase indexing and embedding provider |
| Display and Notifications | Font size, task timeline, language, sounds, and attention alerts |
Agent Manager also exposes application settings for automatic branch names and branch prefixes.
Where settings are stored
BIGGI combines extension-specific VS Code settings with runtime JSONC configuration.
| Scope | Location | Use it for |
|---|---|---|
| VS Code user or workspace | VS Code Settings | Extension UI, autocomplete, browser, Agent Manager, and notification preferences |
| Runtime global | ~/.config/biggi/biggi.jsonc | Providers, models, permissions, agents, MCP, and shared runtime behavior |
| Project | biggi.jsonc or .biggi/biggi.jsonc | Repository-specific agents, permissions, MCP, instructions, indexing, and Game Loop options |
The settings UI writes the appropriate location for supported controls. Use JSONC for advanced values that are not exposed in the UI.
Reload configuration
Run BIGGI: Reload Config and Skills from the Command Palette after editing agents, skills, or configuration files. Start a new session when you need the updated system instructions to apply from the first turn.
Safety defaults
Permissions are evaluated from most general to most specific, with the last matching rule winning. Review Auto-Approving Actions before allowing broad command or file patterns.
Snapshots protect against accidental file edits, but they do not include every external effect. A command can change databases, cloud resources, generated artifacts, or files outside the workspace.