HugoAir Dev
765b972a00
app.clipboard.pasteImage dead-ended with a status message when the clipboard held text, which made the chord useless on hosts that only deliver that one keypress (VS Code's integrated terminal forwarding Ctrl+V, Windows clipboard history via Win+V simulating Ctrl+V). - handleImagePaste now pastes clipboard text through the editor's paste semantics when no image is available; an empty clipboard reports 'Clipboard is empty'. - readTextFromClipboard reaches the Windows clipboard through host PowerShell under WSL (mirroring readImageFromClipboard), with CRLF normalization and UTF-8 output encoding. - handleClipboardTextRawPaste's empty-clipboard status message moved to the actual empty branch (was shown after successful pastes). - Clipboard reads are constructor-injectable for tests. Implements proposal 1 of #1628.
4.5 KiB
Keybindings
Run /hotkeys inside an omp session to see the active chords for your current build. The list reflects any remaps loaded from disk and any bindings added by extensions.
Customize keybindings
User remaps live in ~/.omp/agent/keybindings.yml. The file is a YAML mapping whose keys are keybinding action IDs and whose values are either one chord string or an array of chord strings. It is not read from ~/.omp/agent/config.yml, and there is no nested keybindings object.
app.model.cycleForward: Ctrl+P
app.model.selectTemporary: Alt+P
app.plan.toggle: Alt+Shift+P
Chord names are case-insensitive and use the same notation shown in the UI, such as Ctrl+P, Alt+Shift+P, Shift+Enter, and Ctrl+Backspace.
Set an action to an empty array to disable it:
app.stt.toggle: []
Common action IDs
| Action ID | Default | Meaning |
|---|---|---|
app.model.cycleForward |
Ctrl+P |
Cycle role models forward |
app.model.cycleBackward |
Shift+Ctrl+P |
Cycle role models in temporary mode |
app.model.selectTemporary |
Alt+P |
Pick a model temporarily for this session |
app.model.select |
Alt+M |
Open the model selector and set roles |
app.plan.toggle |
Alt+Shift+P |
Toggle plan mode |
app.history.search |
Ctrl+R |
Search prompt history |
app.tools.expand |
Ctrl+O |
Toggle tool-output expansion |
app.thinking.toggle |
Ctrl+T |
Toggle thinking-block visibility |
app.thinking.cycle |
Shift+Tab |
Cycle thinking level |
app.editor.external |
Ctrl+G |
Edit the draft in $VISUAL / $EDITOR |
app.message.followUp |
Ctrl+Q, Ctrl+Enter |
Queue a follow-up message |
app.message.dequeue |
Alt+Up |
Dequeue a queued message back into the editor |
app.display.reset |
Ctrl+L |
Reset terminal display |
app.clipboard.copyLine |
Alt+Shift+L |
Copy the current line |
app.clipboard.copyPrompt |
Alt+Shift+C |
Copy the whole prompt |
app.clipboard.pasteImage |
Ctrl+V (Alt+V fallback on Windows) |
Paste from the clipboard (image preferred, text fallback) |
app.stt.toggle |
Alt+H |
Toggle speech-to-text recording |
On Windows Terminal, Ctrl+V may be handled by the terminal paste command before omp sees it; use the Alt+V fallback when clipboard image paste appears to do nothing. When the clipboard holds no image, app.clipboard.pasteImage pastes the clipboard text instead, so hosts that deliver only this chord (VS Code's integrated terminal when configured to forward Ctrl+V, Windows clipboard history via Win+V) work for both payload kinds. Windows Terminal also swallows Ctrl+Enter, so the follow-up shortcut also binds Ctrl+Q — the same chord GitHub Copilot CLI uses. If your existing keybindings.yml already assigns Ctrl+Q to another action, that user remap wins and follow-up keeps Ctrl+Enter unless you explicitly bind app.message.followUp.
Terminals that implement OSC 5522 enhanced paste can send clipboard MIME data directly to omp; image pastes are attached as [Image #N], while text/plain paste events keep normal paste behavior. When OSC 5522 is unavailable, bracketed paste still handles text, and a pasted single image-file path is loaded as an image when the file is readable from the omp host.
Older unqualified action names are migrated when keybindings.yml is loaded, but new docs and new configs should use the namespaced action IDs above. Existing keybindings.json files are still accepted and migrated to keybindings.yml; keybindings.yaml is also accepted.