Code Mode & Editor

1. Press Ctrl+2, or click the Code icon in the left activity bar.
2. On first launch, a one-time dialog asks whether to use the Dockview layout (drag-to-split panels) or the Legacy layout (fixed CSS grid). You can change this later at Settings → Layout → Layout Engine.
3. Open a project folder with the Open Folder button in the status bar or top bar. The file tree, git status, and the agent's workspace scope all follow this folder.

Dockview is the default layout engine since beta.22. Every panel - Explorer, Editor, Agent, Terminal, Source Control, Search, Preview, Symbol Outline, Map, Fleet - is an independent pane you can drag, tab, split horizontally or vertically, and resize. Layout is saved automatically (500 ms debounce) to the ui.dockview_layout setting.

Default arrangement: Explorer (left, 220 px) + Editor (center, fills remaining space). The Agent panel opens lazily the first time you use it and docks at 380 px on the right.

Reset: Settings → Layout → Reset Layout (only enabled in Dockview mode).

Always-mounted panels (Terminal, Preview, Agent, Fleet) stay in the DOM when hidden - their processes and state survive panel hide/show cycles. Fleet Monitor is not always-mounted.

If the persisted layout is corrupt or empty, Bodega falls back to buildDefaultDockviewLayout() automatically.

The Legacy engine uses a CSS grid with react-resizable-panels. Panels are fixed regions - no drag-to-split. Switch to it at Settings → Layout → Layout Engine → Legacy, or choose it in the first-launch dialog.

Two things only work in Dockview:

• Reset Layout button is disabled in Legacy mode.
• Bodega Map opens as an editor tab in Legacy mode (not a dockable panel).

The editor uses Monaco (@monaco-editor/react) with the custom noizey-dark theme, which reads CSS custom properties on mount and updates automatically when you switch the app theme.

Defaults: Geist Mono, 14 px (Consolas/Courier New as fallback). Syntax highlighting, IntelliSense, bracket matching, minimap, sticky scroll, and smooth cursor animation are all on by default.

Adjust in Settings → Editor: Font Size, Font Family, Tab Size, Word Wrap, Minimap.

All standard Monaco shortcuts work: Ctrl+F (find), Ctrl+H (replace), Ctrl+Shift+P (command palette). Ctrl+G / clicking Ln:Col in the status bar opens the go-to-line dialog.

• Open: click a file in the Explorer panel, or press Ctrl+P for quick-open.
• Save: Ctrl+S. A dot on the tab means unsaved changes.
• Save As: Ctrl+Shift+S.
• Revert to disk: Ctrl+Shift+R - this immediately overwrites unsaved edits, no undo.
• Close tab: Ctrl+W. If the file has unsaved changes, a confirmation dialog appears.
• New file / Open file: click the + button in the tab bar.

After the agent edits a file, Monaco shows colored 3 px bars in the gutter:

Decorations appear after the write completes, not during streaming. While the agent is actively writing, a real-time inline streaming diff overlay replaces them. Decorations clear when you edit the file yourself. Removed lines are not marked - they no longer exist in the file.

1. Toggle blame via the Status Bar (click the git branch name) or dispatch the bodega:toggle-blame window event.
2. Each line shows an inline annotation with the commit author, date, and the first 50 characters of the commit message.
3. To update annotations after a save, toggle blame off and on - it does not auto-refresh.

Requirements: the project folder must be a git repo. Non-git projects show an error.

AI inline completions appear as grey ghost text as you type, similar to GitHub Copilot. Bodega sends the code before and after the cursor to the configured FIM model.

Three modes (Settings → Models → Autocomplete):

• Off - disabled.
• Primary - uses your active chat model with a FIM-capable endpoint.
• Custom - a separate FIM model/provider (URL + model name).

For Ollama, native FIM uses /api/generate with a suffix param. For OpenAI-compatible endpoints, /v1/completions. If the endpoint doesn't support native FIM, a chat-prompt-injection fallback runs instead.

Model resolution order: fim.model → llm.fim_model → auto-detect → llm.code_model → llm.default_model. Ollama's running models are scanned every 60 s to detect FIM-capable options.

1. Select the problematic code in the editor.
2. Right-click → Fix with Bodega (or use the lightbulb that appears on error lines).
3. The floating input pre-fills with "Please fix" - edit it to describe what you want.
4. Press Enter or click Fix. The agent streams the fix directly into the file.

The widget anchors near the selected text via a React portal (rendered to document.body, z-index 200). It hides automatically when a secondary panel like Settings is open.

All four AI context-menu actions require a non-empty selection.

After an agent edit session, you can review changes one hunk at a time:

1. Click Review Changes in the editor tab bar, press Ctrl+Shift+D, or click the Review hunks button (stacked-blocks icon) next to any file in the Agent panel's change list.
2. The split-right view shows the diff, divided into hunks using Myers diff.
3. For each hunk, click Accept (applies the change) or Reject (restores the original lines).
4. Accept All and Reject All buttons handle the whole diff in one click.

Hunks are applied bottom-to-top to keep line numbers accurate. Very large diffs may be slow to compute.

Bodega saves a snapshot of every file before each tool call that modifies it. Snapshots are stored in the checkpoints SQLite table.

To browse or restore a snapshot:

1. Open the secondary panel (Ctrl+Shift+D).
2. Select the checkpoints tab.
3. Click a snapshot to preview it, then click Restore to roll back.

Checkpoints are per-session and per-file. They are not git commits - they won't appear in git history. They clear when the session ends.

Bodega runs typescript-language-server for .ts and .js files. Errors and warnings appear as red/yellow squiggles in the editor and are counted in the status bar.

• Hover a squiggle for the diagnostic message and quick-fix lightbulb.
• Navigate between errors with F8 (next) / Shift+F8 (previous).
• The Problems panel lists all diagnostics for the project.

Other languages get Monaco syntax highlighting but no LSP diagnostics. There may be a brief delay on first file open while the language server initializes.

The Outline panel (Dockview panel ID: outline) shows the active file's symbols - functions, classes, variables - sourced from Monaco's document symbol provider (the LSP when available).

Click any symbol to jump to that line. The panel is in the left column by default, below Explorer. For unsupported languages the outline may be empty or use regex-based fallback parsing.

The status bar runs along the bottom of Code Mode.

Left side (all clickable):

Right side:

The Agent panel (Dockview ID: panelSidebar) is the primary AI interaction surface in Code Mode. It has four sub-panels, each with its own tool allowlist and per-panel iteration limits:

Open with Ctrl+Shift+D or click the Agent tab in the Dockview layout. Type a prompt in the composer and press Enter or Send. Use @ to attach context (files, symbols).

The panel is always-mounted - it stays in the DOM when hidden. Per-type empty states explain each sub-panel when no session is active.

The Run in Background button (clock icon, next to Send) lets you fire off a task and walk away. The agent keeps working; you get a toast and OS notification when it finishes or needs approval.

1. Type your prompt in the Agent composer.
2. Click the clock icon. Optionally check Isolated to run in a throwaway git worktree - recommended for multi-file or risky tasks.
3. The composer clears immediately. A toast confirms the background run started.
4. Monitor progress via the Fleet indicator badge in the top bar.

When the button is hidden: it only appears when a real session exists (sessionId is non-null) and a project folder is set. Isolated mode requires a git repo - the backend returns a clear error if the project isn't one.

All in Settings → Agent:

How the loop runs: each message enters a multi-iteration cycle. The agent calls tools, checks results, and decides whether to continue or respond. Tool results are capped at 16,384 characters. Context auto-compacts at 75% fill and every 3 iterations.

Open via the Activity Bar or by clicking the branch name in the status bar.

Staging and committing:

1. Click + next to a file to stage it.
2. Write a commit message, or click Generate for an AI-generated one (POST /git/suggest-commit, uses your active explain model).
3. Click Commit.

Branches: use the branch dropdown at the top of the panel to switch or create branches.

Diffs: click any file entry to open a split-right diff view.

PR description: click Generate PR Description to get a structured markdown summary based on your commits ahead of main (falls back to master).

Git status polls every 5 seconds, but only while the Source Control panel is open.

The Review button in the Source Control panel runs an AI review of the current git diff.

1. Open the Source Control panel.
2. Stage or modify files (or work on a branch with commits ahead of main).
3. Click Review.

The backend (POST /git/review-changes) checks for uncommitted changes first - staged and unstaged. If the working tree is clean, it reviews the branch diff versus main/master. The diff is capped at 14,000 characters (truncated with a suffix if exceeded).

Review output groups findings under ### Critical, ### High, and ### Suggestions. Empty sections are omitted. If nothing stands out, you get "No significant issues found."

Clicking Review again replaces the previous result. Requires a git repo and an active LLM provider.

The Map panel (Dockview ID: codeMap) is an interactive file dependency graph powered by @xyflow. Nodes represent files; edges represent imports and dependencies. CodebaseGraphScanner builds the graph by merging JS/TS imports, HTML/CSS cross-links, and structural edges.

Interacting with the graph:

• Click a node to open a detail panel showing the file's module summary.
• Click Explain on a node to get an AI-generated summary from GET /codebase/wiki/explain (cached in the wiki_summaries SQLite table).
• Amber dots on nodes mean the AI summary may be stale - the file's content hash changed since the last explanation.
• Zoom with the scroll wheel or the zoom controls. The minimap (bottom-right) gives an overview.

@xyflow is lazy-loaded to keep it out of the main bundle. In Legacy layout mode, the Map opens as an editor tab instead of a dockable panel.

The Terminal panel (Dockview ID: terminal) is a full xterm.js terminal running in your project folder. It is always-mounted - the shell process persists when the panel is hidden.

Click + in the terminal panel for a new terminal instance. Manual terminal commands have no agent security filter; only the agent's ShellTool has the credential-scanning and sandbox restrictions.

Bodega can own the llama-server --embedding process for local Knowledge Base / RAG embeddings, running on port 8081 (separate from the chat server on 8080).

To configure:

1. Go to Settings → Models → Embeddings.
2. In the llama.cpp (Managed) section, check Let Bodega manage the embedding server.
3. If GGUFs are already installed (downloaded via Models → llama.cpp → Discover), pick one from the dropdown. Otherwise, type the full path to a GGUF in the manual path field.
4. Set the port if needed (default 8081).
5. Click Save. The server starts automatically on the next embedding operation.

Requirements: the llama.cpp binary must be installed (Settings → Models → llama.cpp → Install). Recommended embedding models: nomic-embed-text, bge.

The managed server fixes context at 8192 tokens and does not use flash attention. Concurrent start requests coalesce onto a single start promise. Stopping (model change or app quit) aborts any in-flight readiness poll.

The Fleet panel (Dockview ID: fleet) shows active parallel agent runs - multiple agent sessions working concurrently on the same task. Each session's insertions/deletions, status, and winner selection are visible here. Use Accept / Discard to apply or drop a session's changes.

The Fleet Monitor panel (ID: fleetMonitor) shows an aggregate run status table. Unlike other always-mounted panels, Fleet Monitor is not always-mounted - its 5-second poll pauses when the panel is hidden.

Status streams via GET /api/parallel-runs/:runId/status-stream (a dedicated SSE endpoint, not the main chat-stream). The Fleet TopBar badge shows counts of running and awaiting-approval sessions.