Settings, Themes & Spending

The Settings panel is a two-column overlay: a left nav listing all sections by group, and the selected section on the right.

Sections are organized into seven groups:

Only two things are hidden by default: the entire Workspace group (Editor, Keybindings, Terminal) and the Experimental item. All other sections - including Agent, Fleet, MCP Servers, Skills, Custom Agents, Privacy & Safety, and Spending - are always visible.

To see the advanced sections, scroll to the bottom of the left nav and click Show advanced settings. The app remembers this preference.

To jump to a specific setting without scrolling: press Ctrl+F inside the panel to focus the search box. It matches across all 24 sections.

Bodega ships with four themes - two dark, two light:

Theme changes apply to the editor, terminal, and all UI components. No restart needed.

To change the theme:

1. Go to Settings → Theme (top of the nav, always visible).
2. Click any card - it previews immediately.
3. Click Apply Theme to save. If you navigate away without clicking Apply, the preview reverts.

The current active theme is shown in the top-right of the Theme section header.

Settings → Profile (Look & Feel group).

Display name (user.display_name) appears in the greeting on the home screen.

Agent name (persona.name, default: Bodega) shows in chat bubbles, the terminal, and the agent's system prompt. Leaving it blank or whitespace-only falls back to Bodega.

Voice input (STT) adds a microphone button to the chat input bar:

• Provider: Local (Whisper-compatible server) or OpenAI cloud
• If using a local server, enter the server URL
• Model: large-v3 (highest accuracy) or base (fastest)
• Language: 10 options

Air-gap mode blocks cloud STT automatically.

This section also includes a VS Code / Cursor settings import utility for migrating keybindings and preferences.

Settings → Models (Models & Providers group) has three tabs:

Discover - browse and download from the curated model catalog.

My Models - assign the 9 model roles that Bodega uses for different tasks:

• Chat, Code, Fast, Smart, FIM, Research, Debug, Advisor, and the architect/editor pair for Dual-Model Mode
• A hardware tier badge (VRAM + Apple Silicon detection) helps match models to your machine
• FIM (fill-in-the-middle, for code completion ghost text) is configured here
• Codebase Embeddings are also here - not in a separate section. Set provider, model, base URL, and whether to auto-index on project open. A "rebuild needed" banner appears when the saved embedding model differs from what the index was last built with.

Providers - 24 preset connection cards (9 local + 14 cloud + 1 custom) covering local providers (llama.cpp, Ollama, LM Studio, etc.) and cloud providers. Switching provider takes effect immediately; switching model presets may trigger a server hot-swap.

A search box at the top-right of the Models section filters within whichever tab is active.

Settings → Cloud Boost (Models & Providers group).

Cloud Boost routes individual messages to a secondary cloud provider. It supplements your primary provider - it does not replace it. You opt into it per-message via the chat interface.

Configuration:

• Pick one of 14 cloud presets: Anthropic, Azure, Cohere, DeepSeek, Featherless, Fireworks, Gemini, Groq, Kimi, Mistral, OpenAI, OpenRouter, Qwen, Together
• Paste an API key, optionally override the base URL
• Click Test Connection to populate the model dropdown, then select a default model
• Set daily and monthly budget limits in USD. 0 means unlimited. Requests are blocked when the budget is exceeded.

Spend tracking for Cloud Boost is inline here: the Cost Tracker card shows session / today / monthly spend and request count. It only appears once the backend starts returning cost data (i.e., after your first boosted message).

Air-gap mode disables the Boost toggle and shows a warning banner.

Settings → Cloud API Keys (Models & Providers group, collapsed by default). Click the header to expand.

This section holds BYOK (bring-your-own-key) API keys for using cloud providers as your primary LLM - not for Cloud Boost (which has its own key). Keys are stored encrypted at rest.

Supported providers:

Keys auto-save as you type.

BYOK spend tracking appears at the top of this expanded section as the CloudSpendSummary block - session / today / this month, with a per-provider cost breakdown sorted by spend. It stays hidden until at least one BYOK-charged message has been sent in the current session. Spend figures come from a static pricing table and may differ from your actual provider invoice.

Settings → Spending (Models & Providers group, always visible).

Spending is a dedicated dashboard that consolidates all cost tracking in one place:

• Period picker - switch between 7-day, 30-day, and 90-day views
• Spend chart - a stacked bar chart showing daily spend over the selected period
• Per-provider breakdown - cost and request count per cloud provider
• Per-model breakdown - cost and request count per model
• Data retention control - set how many days of spend history to keep
• Clear All button - wipes all stored spend history

Both Cloud Boost costs and BYOK costs appear here. You do not need to look inside Cloud Boost or Cloud API Keys for cost summaries - Spending is the single place for all billing data.

Settings → Agent (AI Behavior group - always visible).

Controls for the agentic loop:

• Max Iterations (5–100, default 25) - maximum tool-call iterations per message
• Tool Timeout (10–300 seconds, default 30) - how long to wait before timing out a tool call

Dual-Model Mode splits each loop into two stages: an architect model that plans and an editor model that executes. You pick each model independently. If you assign the same model to both roles, the UI warns you.

Dual-Model only applies in Code mode. Once enabled here, the Dual-Model Verify option in Experimental becomes available.

An informational block in this section explains how the loop works: tool result cap (16,384 chars), context auto-compact threshold (75%), and temperature scaling across iterations.

All agent fields save together via Save Agent Settings.

Settings → Prompts (AI Behavior group - always visible).

System prompt templates define the agent's identity, tone, tool policy, and output formatting. The app ships with built-in templates; you can create, edit, and delete custom ones.

• Set separate defaults for Chat mode and Code mode using the two pickers at the top of the section
• The active mode's default applies automatically when you switch modes
• Filter by All / Built-in / Custom
• Export custom templates as JSON; import from JSON
• Built-in templates can be toggled on/off but not edited or deleted

All three are under the Workspace group (requires Show advanced settings).

Settings → Editor

• Font size, font family, tab size
• Word wrap, minimap, line numbers, whitespace rendering
• Bracket pair coloring, font ligatures
• Format on save
• AI completions (FIM ghost text) - enable/disable

Settings → Keybindings Customize keyboard shortcuts for navigation, editing, and terminal actions.

Settings → Terminal

• Font size, cursor style (bar / block / underline), cursor blink
• Scrollback buffer size

Terminal changes take effect for new tabs only. Existing terminal tabs keep the settings they opened with.

Settings → MCP Servers (Integrations group - always visible).

MCP (Model Context Protocol) lets external servers expose additional tools to the agent. Bodega supports multiple simultaneous MCP server connections.

Each server card shows:

• Colored status dot (green = connected, red = disconnected)
• Name, network badge, tool count
• Connect / disconnect toggle and Remove button
• Command string and exposed tool names

The list auto-refreshes every 5 seconds. Errors appear as red text below the server row.

Adding a server:

1. Enter Name, Command, and Arguments.
2. Check Requires network access if the server makes outbound requests.
3. Click Add Server.

Quick-start presets (Filesystem, GitHub, Brave Search, SQLite, Memory, Fetch, Sequential Thinking) fill the form automatically.

Once connected, tools appear in the agent's tool list as mcp_<servername>_<toolname>. Servers marked as requiring network access are blocked when air-gap mode is on.

Settings → Skills (Integrations group - always visible).

Skills are reusable agent workflows. They're triggered by slash commands in the chat bar or automatically when Bodega detects a matching keyword pattern (auto-activation).

• Global auto-activation toggle - turn off if you want slash-command-only invocation
• Filter by All / Built-in / Custom
• Built-in skills can be toggled on or off but not edited
• Custom skills: create via the form (name, description, triggers, tools, invocation type, body), edit, delete
• Reload button rescans the filesystem for skill files

Each skill card shows its triggers, tools, and invocation type.

Settings → API Server (Integrations group - always visible).

Enables a local server that accepts OpenAI-compatible requests, so tools like Claude Code or Continue can route through Bodega's local models.

Three endpoints when enabled:

• GET /v1/models
• POST /v1/chat/completions
• POST /v1/agentic/completions

Default port: 1337. An optional API key enforces Bearer token auth.

The Quick Setup block shows pre-filled environment variable snippets for Claude Code and other clients.

Requires an app restart to take effect. The base URL and API key can be copied via the buttons in the section.

Settings → Privacy & Safety (Privacy & Safety group - always visible).

Air-Gap Mode - blocks agent web tools (web_fetch, web_search), shell network commands, auto-updates, cloud STT, Cloud Boost, and MCP servers requiring network access. It does NOT block LLM provider traffic. If a cloud provider is set while air-gap is on, a warning banner appears.

Guardrails:

• Content filtering master toggle
• Custom blocked patterns (one regex per line, with per-line validation)
• Shell command sandbox level:
  • Off - every command requires approval
  • Moderate - safe commands auto-approve with a 30-second timeout
  • Strict - only read-only commands auto-approve

The sandbox setting only applies in Ask mode.

Rate limits:

• Max Input Length (100–100,000 chars)
• Messages Per Minute (1–200)
• Session Token Budget (1,000–1,000,000 tokens)

Save all fields together via Save Safety Settings.

Both are under the AI Behavior group (always visible).

Settings → Session Memory

• Toggle memory persistence (whether long-term memories survive restarts)
• Short-term capacity: 100–50,000 entries (cleared on restart)
• Long-term capacity: 100–100,000 entries (persisted to SQLite)
• Current entry count shown live
• Add topic/fact pairs manually; browse, search, and delete stored memories

Settings → Knowledge Base

• Add entries by URL (Bodega fetches and stores stripped text) or raw Text (large content is auto-chunked)
• Tags organize entries; click a tag to filter
• Search by title, content, tags, or URL
• Expand any entry to read its full content; delete via the X button
• Knowledge & Embeddings: enable embedding-based semantic search for knowledge entries, choose embedding model and provider, adjust hybrid search weight (0 = keyword only, 1 = semantic only)
• The agent searches knowledge automatically via the query_knowledge tool

You can also add knowledge from the chat + menu (Add URL) or from the Context Inspector (Add Knowledge button) without opening Settings.

Settings → Accessibility (Look & Feel group - always visible).

Focus Style: Default / Bold (3px outline) / High Visibility (yellow outline)

The section also documents keyboard navigation patterns and ARIA / screen reader support.

Settings → Experimental (About & Support group - requires Show advanced settings). All features carry a yellow warning banner.

Smart Auto - routes Code mode iterations to the right model tier automatically: fast model for reads, code-specialized model for writes, smart model for planning. Requires the fast, smart, and code model slots to be filled in Settings → Models. No effect in Chat mode or single-model setups.

Dual-Model Verify - after each agentic loop iteration, the architect model reviews the editor model's output. Requires Dual-Model Mode to be enabled in Settings → Agent - the toggle is disabled if it isn't.

Language Server Protocol (LSP) - enables typescript-language-server for TypeScript/JS diagnostics, go-to-definition, and refactoring in the editor. Requires the binary on your PATH. Status shows as a colored badge (Running / Starting... / Error / Stopped). The binary check runs once when you open this section.

Settings → About (About & Support group - always visible, no Show advanced settings required).

• App version info
• Export Diagnostics Bundle - writes a redacted system snapshot to a text file. Includes version, hardware, settings (secrets stripped), recent sessions, recent errors, network activity, and backend logs. Useful for bug reports.
• Reset to Defaults - wipes all settings. This cannot be undone.