Keyboard & Command Reference

These work from any screen, including when focus is inside an input.

Ctrl+B does different things depending on mode. In Chat mode it toggles the session list; in Code mode it toggles the file tree. These are the same physical shortcut bound to different actions.

Arrow-key list navigation. The chat session list and the model picker's rows support ArrowUp/ArrowDown/Home/End once focus is inside the list - you don't have to Tab through every row to reach the one you want.

Open specific AI panels in Code mode. All five shortcuts open the Bodega Panel if it's closed, then activate the right tab. They have no effect in Chat mode.

Ctrl+Shift+E opens the Debug panel - not the file explorer. The file explorer has no dedicated shortcut; use Ctrl+B to toggle it.

Files and tabs

In the editor's Review Changes tab every hunk starts undecided; a/r mark the focused hunk and pressing the same key again clears it. Deciding the last hunk applies your choices automatically. Ctrl+Enter and Ctrl+Backspace act on the whole file at once.

Search and navigation

AI editing

Git and source control

Formatting and diagnostics

View

Hunk review - one keyboard vocabulary, both surfaces. j/k/a/r/Ctrl+Enter/Ctrl+Backspace/Esc are identical in the batch Hunk Review panel (Ctrl+Shift+D, one file's hunks as cards) and the in-tab Diff Review panel (editor tab bar's diff icon) - only what Ctrl+Enter/Ctrl+Backspace map to changes per surface, because each has different actions available:

Every hunk starts undecided in both. a/r mark the focused hunk, and pressing the same key again clears it. In the Diff Review tab, deciding the last hunk applies your choices automatically (accepted hunks stay, rejected hunks are reverted); in the batch panel, Apply choices becomes available once every hunk is decided. j/k move focus (and screen-reader focus) between hunks. Close (Esc) never changes the file: it stays as the agent wrote it. If the file was edited after the agent wrote it, nothing is overwritten: you are asked whether to reload the review, overwrite anyway, or cancel. The batch panel's Open in Diff Review button carries its current per-hunk decisions into the in-tab panel, so switching surfaces mid-review doesn't reset any toggling.

Ctrl+P only works in Code mode. Shift+Alt+F/F8/Shift+F8 require a focused editor. Ctrl+Shift+R reverts the file to disk when the editor is focused (undoable - a toast confirms) and opens the Research panel otherwise. Ctrl+F and Ctrl+Alt+F are Monaco native overlays - not intercepted by the app shell. Ctrl+H (Find and Replace) is the default Monaco binding on Windows but collides with "Hide Application" on macOS; use Ctrl+Alt+F instead for consistency across platforms.

Fleet shortcuts only fire in Code mode unless noted.

Ctrl+W closes an editor tab. Ctrl+Shift+W closes the active fleet session - the extra Shift is intentional to prevent accidental session termination.

Ctrl+Shift+U shows or hides Runs: the panel in the left group in Code mode, the Runs tab of the sidebar in Chat mode. (Ctrl+Shift+R is still the Research panel.) Inside the Runs list the keys work like any tree, and you only tab into it once.

Letters typed quickly jump to a run whose title starts with them. A, S and M are commands when they start a word, and ordinary letters from the second character on, so a run called "Search docs" is still reachable.

Settings that belong to the view: ui.runs.collapsed (which sections you collapsed) and ui.runs.pinned (runs you pinned; pinned runs sort first in their section). Both are yours, not the project's.

Fill-in-the-Middle completions appear as inline ghost text in the Monaco editor while you type.

Completions trigger automatically after a short debounce. The FIM model is auto-detected from installed models; assign a specific model at Settings → Models & Providers → Models → My models → Where suggestions come from.

Models with native FIM tokens: qwen2.5-coder, codellama, deepseek-coder, codestral, starcoder, starcoder2, codegemma, stable-code. qwen3-coder uses prompt-injection fallback.

Tab and Ctrl+Right only accept ghost text when a suggestion is visible. When no suggestion is shown, Tab inserts a literal tab.

Panel control (work from any focus point)

When the terminal has focus

Inside the AI Assist overlay (Ctrl+I)

Ctrl+F in the terminal opens terminal output search - distinct from Ctrl+Shift+F (project file search). Ctrl+I and block-navigation only fire when the terminal has focus. The AI Assist generator scopes commands to the current working directory.

Type / in any chat or AI panel input. A autocomplete menu appears with all available commands.

/reset and /model are not registered commands. Typing them shows a toast listing the actual available commands (the same list /help prints).

/export shows an info toast instead of exporting when used in Code mode.

Twelve built-in skills ship as SKILL.md files under the app's skills/ directory. Their triggers pass through to the backend LLM as structured workflow invocations - they're not handled client-side.

Built-in and user skills load from the backend at startup. Disabling a skill in Settings → Connections → Skills (Integrations group) removes its trigger from the autocomplete list. You can define custom skills there too; user-created skills live in ~/.bodega/skills/<name>/SKILL.md and are not trust-gated - they're yours.

Project skills require approval. A skill shipped inside a project's own .bodega/skills/ folder - one that arrived via git clone, say - does not load. It is skipped before its frontmatter is even parsed, so it is never registered and never shown to the model. Approval is keyed to the SHA-256 of the entire SKILL.md file, frontmatter and body, paired with that project's resolved path. So editing an approved skill re-prompts, and approving it in one checkout does not approve it in another. Approve at Settings → Connections → Skills → Project Skills (the block only appears when the open project has skills to show), or via the corner chip that appears on project open. From a shell: bodega skills trust to list, bodega skills approve <name> to approve. There is no "deny" - declining is just not approving.

Project skills are re-read on every turn, so the Reload button in Settings → Connections → Skills does not affect them; it rescans the built-in and ~/.bodega/skills directories only.

/review (the skill) is distinct from the Git panel "Review" button. The skill reads a recent project file; the button reviews the current git diff using your LLM.

1. Press Ctrl+Shift+P to open.
2. Type any part of the action name - fuzzy matching works. For example, ter max matches "Toggle Terminal Maximize".
3. Press Enter or click an action to execute. Esc closes without acting.

Actions grouped by category:

• Navigation: Switch to Chat Mode (Ctrl+1), Switch to Code Mode (Ctrl+2), Toggle Settings Panel (Ctrl+,), Show Usage Panel, Show Agents Panel
• Terminal: Toggle Terminal (Ctrl+\``), Toggle Terminal Maximize (Ctrl+Shift+`), New Terminal Tab (Ctrl+Shift+T`)
• View: Toggle Sidebar (Ctrl+B), Reload Window (Ctrl+R), Show Keyboard Shortcuts (Ctrl+/)
• Panels: Debug Panel (Ctrl+Shift+E), Toggle Bodega Panel (Ctrl+Shift+B), Toggle Fleet Panel (Ctrl+Shift+F)
• Editor: Toggle File Explorer (no dedicated shortcut - Ctrl+B toggles the sidebar contextually), Close Active Editor Tab (Ctrl+W, confirms unsaved changes), Go to Line (Ctrl+G), Toggle Split Editor (Ctrl+\\)
• Search: Search in Files (palette action - Ctrl+Shift+F belongs to the Fleet panel), Go to File... (Ctrl+P)
• Source Control: Open Source Control (Ctrl+Shift+G)

Ctrl+Shift+B toggles the Bodega Panel and Ctrl+Shift+F toggles the Fleet panel - the palette's older "File Explorer"/"Search in Files" shortcut labels were corrected in the beta.27 audit. Ctrl+Shift+E is Debug Panel, not File Explorer.

Custom rebinding isn't supported yet - the bindings in these tables are fixed.

Settings → Appearance & Editor → Keyboard shortcuts is a searchable read-only reference of the same bindings. An earlier version of that panel offered a rebind flow, but the combinations it saved were never actually applied by the app - as of beta.27 the panel is honest about being view-only until a real keybinding engine ships.

Shortcuts handled at the OS level (Ctrl+C, Ctrl+V) are fixed by the platform either way.

The Git panel has a Review button that sends the current diff to your LLM and returns a structured review grouped under Critical / High / Suggestions headings.

1. Open the Git panel with Ctrl+Shift+G or click the branch name in the status bar.
2. Click Review (in the panel header actions row, next to Generate and Stage All).
3. Review output appears inline above the file list. Dismiss it with the X button.

The review uses the model assigned to the explain role (the same model used for code explanations in the editor). Large diffs are capped at 14,000 characters; a truncation note appears in the output if the diff is cut.

When the working tree is dirty, the review covers staged + unstaged changes (the pre-commit case). When the working tree is clean, it falls back to the branch-vs-base diff (the PR scope).

Requires an open project folder. Returns an error if the folder isn't a git repository or has no changes.

Fast Mode turns off extended thinking globally for models that support it (currently the Anthropic preset's models). It does not change the model - it removes the extended-thinking pre-pass so replies start sooner.

Enable: Fast in the composer's ⋯ More options menu. It only appears when the active model supports extended thinking.

The per-message reasoning control in the composer still wins. If you set reasoning to Low / Medium / High for a specific message, that overrides Fast Mode for that message only.

The setting key is llm.claude_fast_mode (boolean, default false). It has no effect on models that do not do extended thinking.

You can define named agents with a custom system prompt, pinned model, tool allowlist, read-only filesystem flag, and iteration cap.

Create an agent:

1. Go to Settings → Agent → Custom agents.
2. Click New Agent.
3. Fill in: name, optional description, system prompt, model override (blank = active model), tool allowlist, read-only filesystem toggle, max iterations.

Activate an agent:

• In Code mode, the Agent panel header shows a profile picker (robot icon with the current agent name).
• Click it to see a dropdown with Default and your custom agents.
• Select one - it applies to the next message and persists until you switch back to Default.
• The picker is hidden when you have no custom agents.

The tool allowlist narrows available tools - it cannot grant access to tools not available to the default agent. Custom agents are distinct from the built-in skills (/commit, /debug, etc.), which are managed via Settings → Connections → Skills (Integrations group).

Bodega One can run as an ACP (Agent Client Protocol) server so external editors - like Zed - can drive it as an AI agent over stdio.

Start the server:

bodega --acp

Bodega starts in headless JSON-RPC mode on stdio. No Electron window appears.

Protocol methods: initialize (advertises capabilities + tool list), session/new (creates a session, confines the working directory), session/prompt (runs one agentic turn), session/cancel.

Connecting external ACP agents to Fleet: Settings → Connections → External coding agents (Integrations group). Each agent needs its binary installed and an API key (or subscription login for Cursor). The section shows install hints and key fields for each supported agent.

CWD confinement is enforced - session/new validates that the requested working directory is within your allowed projects directory.

Bodega can manage the llama-server --embedding process automatically (port 8081), and the Embeddings settings show a dropdown of your installed GGUFs so you don't have to type a path.

Set up managed embeddings:

1. Go to Settings → Prompts & Memory → Knowledge base → Advanced → Embeddings → Codebase index (or search "embeddings").
2. Select llama.cpp as the provider.
3. Enable Let Bodega manage the embedding server.
4. Pick a GGUF from the dropdown - it lists everything installed via Models → llama.cpp → Discover. Or type a manual path in the text field below.
5. Set the port (default 8081).

Bodega starts the server lazily on the first index build. If the model path is empty with managed mode on, Bodega points at any server you're already running.

Recommended embedding models: nomic-embed-text, BGE series.

The llama.cpp binary must be installed (Settings → Models & Providers → Models → My models tab → llama.cpp models) for managed mode to work. The embedding server (port 8081) and the chat llama-server (port 8080) are separate processes.

Bodega Map is an interactive dependency graph of your codebase. Nodes are files; edges are imports. It runs in Code mode only.

Open the Map:

• Activity Bar (left sidebar) → Map icon
• Command Palette → "Open Codebase Map"
• Type /map in any AI panel input

Requires the Dockview layout engine (Settings → Appearance & Editor → Layout → Dockview). In Legacy layout, the Map falls back to an editor tab.

Interactions:

• Click a node to open the detail drawer (imports, exports, relationships).
• Explain this module in the drawer - your LLM writes a plain-English summary, cached by file content hash.
• Toolbar model picker - choose which model writes explanations (blank = active model).
• Generate Map button - bulk-explains all visible files (4 concurrently, with live progress and a cancel button).
• Ask the Map bar at the bottom - free-form questions answered via RAG over your codebase embeddings.

Staleness: amber dots on nodes mean the cached explanation is out of date (file content changed since last generation). The drawer badge shows the stale count.

"Ask the Map" uses two models: a chat model for the answer and an embeddings model for retrieval. Configure the embeddings model at Settings → Prompts & Memory → Knowledge base → Advanced → Embeddings → Codebase index. The first question triggers the index build, which may take a few seconds.

The CLI has its own, separate reference: 30 slash commands in the REPL (/help or /? for the cheat-sheet) and a distinct set of bodega run/REPL flags (--mode, --model, --effort, --tier, --dual, --fallback, and more). None of the app's keyboard shortcuts here apply to the CLI, and none of its slash commands apply to the app - they're two different interfaces to the same backend, each with its own reference.