Skip to content

[FEATURE]: Keyboard command to jump to the next session with a pending permission request #29903

Closed as not planned

Description

@athal7

Problem

When several sessions are running, an agent often blocks waiting for me to approve or deny a tool call. Today the only way to find that session is to scan the sidebar for the warning dot and click it. There's no keyboard way to get to it.

The existing session.next.unseen / session.previous.unseen shortcuts (⇧⌥↓ / ⇧⌥↑) cycle by unseen turn-complete/error notifications, not by pending permissions, and only within the current project — so they don't land me on the blocked session.

Proposal

Add a command (e.g. session.next.permission / session.previous.permission) with a default keybind that jumps to the next session that has an actionable pending permission request, ideally across all open projects, not just the current one.

Notes

The data and helpers already exist client-side: store.permission[sessionID] (packages/app/src/context/global-sync/types.ts), and sessionPermissionRequest(...) — the same predicate the sidebar warning dot uses (packages/app/src/pages/layout/sidebar-items.tsx). The implementation could mirror navigateSessionByUnseen (layout.tsx), swapping the unseen-count check for the pending-permission check.

Related: #27772 (pending-attention indicator), #28175 (sidebar status panel).

Activity

  1. github-actions commented on May 29, 2026

    @github-actions
    Contributor

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

  2. athal7 commented on May 29, 2026

    @athal7
    ContributorAuthor

    [ai] Checked the keybinds docs — no existing binding covers this. The only permission keybind is permission.prompt.fullscreen. Worth noting this would fit the existing session-navigation model (session_child_cycle, session_parent, etc.), so it's a natural addition rather than a new pattern.

  3. github-actions commented on Jul 29, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions