You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
tui: "What's new" advertises desktop-only shortcuts that do nothing in the TUI #61237
The 2.2.5 "What's new" dialog is rendered by the TUI, but it announces shortcuts that only exist in the desktop app, so following it inside the TUI leads nowhere:
Ctrl+Alt+O (choose a worktree) does nothing.
Ctrl+Shift+X (toggle shell mode) does nothing. In the TUI, shell mode is entered with ! and left with Escape / Ctrl+C.
Ctrl+Alt+B scrolls the transcript one page up, because that key is already the default for session.page.up (pageup,ctrl+alt+b), not the announced base-branch picker.
In the binary the lowercase keybind syntax is absent, and the only occurrences are the capitalized prose inside the highlights literal:
$ b=$(readlink -f "$(which opencode)")
$ grep -aoc 'ctrl+alt+o' "$b" # 0
$ grep -aoc 'Ctrl+Alt+O' "$b" # 1, the dialog text
$ grep -aoc 'ctrl+shift+x' "$b" # 0
$ grep -aoc 'Ctrl+Shift+X' "$b" # 1, the dialog text
Also checked: no keymap entry expressed as {key:"o",alt:true}, and no worktree-picker keybind id in the TUI table — the only worktree surface there is dialog.move_session.*.
The bundled highlights list itself has no surface marker: the entries are plain {"title":...,"body":...}, so the TUI cannot tell which bullets apply to it. The desktop path in #60134 filters highlights by a source field, so the scoping concept exists elsewhere but not in this list.
Expected behavior: either these shortcuts work in the TUI, or the dialog does not advertise them to a surface that lacks them (tag each bullet with its surfaces, or filter desktop-only entries when the client is the TUI).
Minor related point: if Ctrl+Alt+B is meant to reach the TUI as a base-branch picker, it collides with the documented session.page.up default, so one of the two has to move.
Thanks for the detailed report. I reproduced this on 2.2.5, and it still happens on the latest dev (ff90ed9).
What I saw on 2.2.5, with a simulated model:
/highlights opens "What's new in 2.2.5". It tells Windows/Linux users to press Ctrl+Alt+O to choose a worktree, Ctrl+Alt+B to choose its base branch and Ctrl+Shift+X to toggle shell mode. The "Send Quotes From the Comment Popup" entry is also about the desktop app.
In a session with a long transcript, Ctrl+Alt+O and Ctrl+Shift+X do nothing.
Ctrl+Alt+B scrolls the transcript up a page, because it is the default for session.page.up.
The recording and screenshots below show this, and the script below reproduces it.
On dev the keys behave the same. Release highlights are still embedded as plain {title, body} entries with nothing saying which app they apply to, so the TUI still can't filter out desktop-only ones. The related work on the desktop side is in #60134 and #60607.
recording.mp4
Reproduction script (drive.ts)
// Reproduces anomalyco/opencode#61237: the TUI "What's new" dialog advertises// desktop-only shortcuts (Ctrl+Alt+O, Ctrl+Alt+B, Ctrl+Shift+X) that do nothing// (or something else) in the TUI.import{Effect}from"effect"import{Llm,OpenCodeDriver}from"opencode-drive"constlong=Array.from({length: 120},(_,i)=>`Line ${i+1} of a long answer.`).join("\n\n")exportdefaultOpenCodeDriver.use({
...(process.env.OC_DEV ? {opencode: {dev: process.env.OC_DEV}} : {}),tui: {recording: true,keypressOverlay: true},},({ ui, llm })=>Effect.gen(function*(){// 1. Show the release highlights dialog (same as after an update).// Source builds (OC_DEV) embed no highlights, so /highlights only exists on release builds.if(!process.env.OC_DEV){yield*ui.submit("/highlights")yield*Effect.sleep("1500 millis")yield*ui.screenshot("01-highlights-dialog")yield*ui.press("escape")yield*Effect.sleep("500 millis")}// Produce a long transcript so paging is visible.// One response for the session title request, one for the answer.yield*llm.queue(Llm.text(long))yield*llm.queue(Llm.text(long))yield*ui.submit("write a long answer")yield*ui.waitFor("Line 120 of a long answer.",{timeout: 30_000})yield*Effect.sleep("1000 millis")yield*ui.screenshot("02-before-shortcuts")// 2. Ctrl+Alt+O: announced as "choose a worktree".yield*ui.press("o",{ctrl: true,meta: true})yield*Effect.sleep("1500 millis")yield*ui.screenshot("03-after-ctrl-alt-o")// 3. Ctrl+Shift+X: announced as "toggle shell mode".yield*ui.press("x",{ctrl: true,shift: true})yield*Effect.sleep("1500 millis")yield*ui.screenshot("04-after-ctrl-shift-x")// 4. Ctrl+Alt+B: announced as "choose base branch"; actually session.page.up.yield*ui.press("b",{ctrl: true,meta: true})yield*Effect.sleep("1500 millis")yield*ui.screenshot("05-after-ctrl-alt-b")}),)
Run it with opencode-drive: opencode-drive run ./drive.ts. It drives opencode from your PATH; set OC_DEV to the path of an OpenCode checkout to run that from source instead.
Activity
opencodejr commentedon Nov 2, 2026
Thanks for the detailed report. I reproduced this on 2.2.5, and it still happens on the latest
dev(ff90ed9).What I saw on 2.2.5, with a simulated model:
/highlightsopens "What's new in 2.2.5". It tells Windows/Linux users to pressCtrl+Alt+Oto choose a worktree,Ctrl+Alt+Bto choose its base branch andCtrl+Shift+Xto toggle shell mode. The "Send Quotes From the Comment Popup" entry is also about the desktop app.Ctrl+Alt+OandCtrl+Shift+Xdo nothing.Ctrl+Alt+Bscrolls the transcript up a page, because it is the default forsession.page.up.The recording and screenshots below show this, and the script below reproduces it.
On
devthe keys behave the same. Release highlights are still embedded as plain{title, body}entries with nothing saying which app they apply to, so the TUI still can't filter out desktop-only ones. The related work on the desktop side is in #60134 and #60607.recording.mp4
Reproduction script (drive.ts)
Run it with opencode-drive:
opencode-drive run ./drive.ts. It drivesopencodefrom yourPATH; setOC_DEVto the path of an OpenCode checkout to run that from source instead.