Skip to content

bug(desktop): tab-cycle shortcuts can follow route history #46852

Closed as not planned

Description

@antivixen

Description

On the Desktop app on recent macOS and Linux releases, next/previous tab navigation does not consistently cycle the visible session tabs. It can appear to follow previously visited routes instead.

Plugins

None reported.

OpenCode version

Recent Desktop releases; exact build versions pending.

Steps to reproduce

  1. Enable the V2 titlebar and reset custom keybindings.
  2. Open three session tabs and reorder them to C, A, B.
  3. From A, use Ctrl+Tab / Ctrl+Shift+Tab or the platform arrow shortcut.
  4. Observe the selected route and tab.

Expected: cycling follows visible titlebar order with wrap: C → A → B → C.

Actual: the shortcut can traverse previously visited routes rather than the visible tab order.

#39241 implemented visible-order cycling; this may be a Desktop shortcut-delivery or effective-keybinding regression.

Screenshot and/or share link

None.

Operating System

macOS and Linux (reported; exact versions pending).

Terminal

Not applicable (Desktop app).

Activity

  1. github-actions commented on Sep 2, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of or related to existing issues. Please check:

    For keybind-related issues, please also check our pinned keybinds documentation: #4997

  2. opencodejr commented on Oct 28, 2026

    @opencodejr
    Contributor

    Thanks for the report! To look into this we need a few more details:

    1. The exact Desktop version (shown in Settings / About) and your macOS and Linux versions. On the current code, the next/previous tab shortcuts walk the visible tab order rather than route history (that's what fix(app): follow visual tab order #39241 changed), so it matters whether your build includes that change.
    2. Does it happen every time with these steps, or only sometimes? If only sometimes, does anything seem to trigger it, for example after using back/forward navigation, or after closing and reopening tabs?
    3. Which shortcut and where the focus was: Ctrl+Tab, or Cmd/Ctrl+Option+Arrow? Was the focus in the chat or prompt, or in the side panel (file tabs)? The same keys also cycle side-panel tabs while that panel has focus.
    4. The tab order you actually got for the C, A, B case, e.g. starting from A, Ctrl+Tab went to ….

    You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know when you're done.

    Closely related:

  3. opencodejr commented on Oct 31, 2026

    @opencodejr
    Contributor

    Closing this for now, since we haven't heard back. We needed the exact Desktop version and a few repro details before we could investigate. On current builds, the next/previous tab shortcuts already follow the visible titlebar order rather than route history (see #39241), so we couldn't tell whether this is a regression or an older build.

    If you still see this, please reply with your Desktop version, your OS versions, which shortcut you used and where the focus was, and the tab order you actually got. We'll gladly take another look. Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions