Skip to content

Hotkeys

Forge has two layers of keyboard shortcuts. Workspace-level bindings are owned by Forge and are listed below. Editor-level shortcuts (Ctrl+S to save, Ctrl+F to find, etc.) come from Monaco when a code tab is focused.

All ten bindings are customizable. Open Settings → Keybindings, click any row, press the new chord, save.

ActionDefault chord
Open command paletteCtrl+Shift+P
Quick-open fileCtrl+P

The command palette filters across commands, tasks, and recent projects. Quick-open filters across files in the current project.

Command palette open with new chat, template scaffolds, pipeline tools, layout toggles, and their bound chords

Quick-open file palette showing all forge-van project files with size and recency metadata

ActionDefault chord
New chat tabCtrl+N
Close active tabCtrl+W
Cycle tabs forward (active pane)Ctrl+Tab
Cycle tabs backward (active pane)Ctrl+Shift+Tab

Tab cycling stays within the active pane. To move between panes, click into the pane you want.

ActionDefault chord
Toggle sidebarCtrl+B
Toggle inspectorCtrl+Alt+B
Toggle terminal panelCtrl+`
Toggle settings viewCtrl+,

When a code or markdown tab has focus, Monaco’s defaults take over. Forge doesn’t intercept these:

ActionChord
SaveCtrl+S
FindCtrl+F
ReplaceCtrl+H
Find and replace across filesCtrl+Shift+F
Go to lineCtrl+G
Add cursor aboveCtrl+Alt+↑
Add cursor belowCtrl+Alt+↓
Comment toggleCtrl+/
Format documentShift+Alt+F

Monaco’s full reference applies. These are from VS Code’s keymap.

Settings → Keybindings shows every workspace binding with its current chord. Click Change on a row, hit the new key combo, confirm. Conflicts (two bindings on the same chord) are flagged before save.

To reset everything, hit Reset all to defaults at the bottom of the panel.

Settings → Keybindings showing the full workspace keymap with browser-reserved warnings inline

Ctrl+N, Ctrl+W, and Ctrl+Tab are conventional browser shortcuts. Forge intercepts them at the window level when running as a desktop app. In the Tauri-packaged build (the MSI you installed), this works reliably.

If you ever run Forge from pnpm dev in plain Chromium for development, these chords may misbehave because the browser claims them first. The Settings panel marks affected bindings with an info badge.

When focus is in a Monaco editor, Monaco wins. Forge’s bindings still fire if the chord doesn’t conflict with a Monaco shortcut. The cleanest example: Ctrl+B (toggle sidebar) is Forge-owned, fires regardless of where focus is. Ctrl+F (find) is Monaco-owned when an editor has focus, and not bound in Forge anyway.