anomalyco / anomalyco/opencode

[FEATURE]: Desktop: Ctrl+Tab should cycle sessions by most-recently-used order (VS Code-style), not positional tab order

Open
#44,258 1 comment 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Aug 22, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Problem

In OpenCode Desktop, Ctrl+Tab cycles through open session tabs in their fixed on-screen order (browser-style). In a multi-session workflow this rarely matches what I want: after opening a new session (Ctrl+N) to quickly check something, the natural next step is jumping straight back to the session I was just working in — but that one can be several positions away in the tab bar, so repeated Ctrl+Tab walks past every intermediate tab to get there.

Proposal

Make Ctrl+Tab / Ctrl+Shift+Tab cycle sessions in most-recently-used (MRU) order, like editor tab switching in Visual Studio Code: the most recently focused session comes first, so two presses always bounce between my two currently active sessions, regardless of where they sit in the tab bar. Keeping the current positional order as an option would be fine for those who prefer browser semantics.

This ordering fits agent workflows particularly well, because interleaving is constant: you start a fresh session for a quick question while another session keeps working, then want to return to it immediately — MRU makes exactly that pair adjacent.

Related reports
  • #40557 — same "cycle through recent sessions" idea proposed for the TUI (session_next / session_previous)
  • #37077 — general request for standard tab shortcuts (Ctrl+T, Ctrl+W, Ctrl+Tab) in the desktop/web app
Environment
  • App: OpenCode Desktop 1.18.21
  • OS: Microsoft Windows 11 Education, 25H2, build 26200.8875

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.