Desktop app: keyboard shortcuts to jump directly to pinned Code sessions (Cmd+1/2/3)

Status Fixed / completed
Maintainer reply None cached
Activity 0 comments · opened Jul 20, 2026 · closed Aug 25, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

The desktop app's Code tab lets me pin sessions, but the only way to switch between them is clicking the sidebar with the mouse. I typically have 3 pinned sessions actively developing 3 different features, and I switch back and forth between them constantly. Mouse-only switching breaks flow.

This is distinct from #74124 (back/forward visit-history navigation) and #45690 (next/previous cycling). Cycling doesn't help when the session list has 20+ chats. What I need is a direct jump to a small set of pinned sessions.

Proposed Solution

Bindable shortcuts that jump directly to pinned sessions by position: Cmd+1, Cmd+2, Cmd+3 for the first, second, and third pinned session, matching browser tab conventions. Pinned sessions already have a stable order in the sidebar, so position-based jumping maps naturally.

Next/previous cycling (Cmd+Shift+]/[) would complement this, but direct jump to pinned sessions is the core ask.

Alternative Solutions

Currently I click each pinned session in the sidebar with the mouse. In the terminal CLI this problem doesn't exist because each session runs in its own terminal tab and the terminal provides tab shortcuts, but the desktop app has no equivalent.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

  1. I have 3 pinned sessions, each developing a separate feature.
  2. While a long-running task executes in session 1, I switch to session 2 to review output, then to session 3 to answer a permission prompt.
  3. With Cmd+1/2/3 I could bounce between them without touching the mouse.
  4. This happens dozens of times a day, so the mouse round-trips add up.

Additional Context

_No response_

View original on GitHub ↗