Skip to content

Feature request: Support Alt+↑ / Alt+↓ to navigate between user commands within the current session #34727

Closed as not planned

Description

@wsaaaqqq

Use Case

In daily workflows, it's common to have multiple sessions running in
parallel
. For example:

  • Session A: Fix a bug, issue a command, wait for AI to execute
  • Session B: Switch to another session to develop a new feature
  • Session C: Open yet another session for code review or refactoring

When frequently switching between sessions — each with potentially long AI
response times — it's easy to forget what command you last gave the AI.
Currently, the only way to find it is by manually scrolling through the message
history, which is slow and error-prone. A shortcut to jump directly to the
previous/next user command would let you instantly recall context and
significantly reduce cognitive overhead.

Expected Behavior

  • Alt+↓ → jump to the next user message
  • Alt+↑ → jump to the previous user message

Only navigate between user-submitted messages (not AI responses), enabling
quick review of your own input history within a long session.

Existing Infrastructure

tui.json already has related keybind options:

  • messages_next (currently defaults to "none")
  • messages_previous (currently defaults to "none")
  • messages_last_user (currently defaults to "none")

Implementation Suggestions

Option A: Add new dedicated keybinds messages_next_user /
messages_previous_user, defaults to alt+down / alt+up.

Option B: Repurpose the existing messages_next / messages_previous
so they navigate only user messages, with alt+down / alt+up as defaults.

Activity

  1. github-actions commented on Jul 1, 2026

    @github-actions
    Contributor

    This issue does not fully meet our contributing guidelines.

    What needs to be fixed:

    • The issue body is empty — only the ## Use Case section header was submitted with no actual content. Please describe the feature, why it is needed, and any relevant context.
    • Feature request titles should start with [FEATURE]: (e.g. [FEATURE]: Support Alt+↑ / Alt+↓ to navigate between user commands within the current session).

    Please edit this issue to address the above within 2 hours, or it will be automatically closed.


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

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

    If you believe this was flagged incorrectly, please let a maintainer know.

  2. github-actions commented on Jul 1, 2026

    @github-actions
    Contributor

    Thank you for updating the issue with detailed content — the description, use case, and implementation suggestions are now clear and helpful.

    However, one requirement is still missing:

    • Title format: Feature request titles must start with [FEATURE]:. Please update the title to something like: [FEATURE]: Support Alt+↑ / Alt+↓ to navigate between user commands within the current session

    You can edit the title directly from the GitHub issue page. Once that's done, the issue will be fully compliant.

  3. github-actions commented on Jul 1, 2026

    @github-actions
    Contributor

    This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

    Feel free to open a new issue that follows our issue templates.

  4. Nowaker commented on Oct 8, 2026

    @Nowaker

    For anyone landing here: I built this for my own use on the v1 TUI: #53333 binds messages_previous / messages_next to ctrl+up / ctrl+down and makes them stop on every prompt (they used to skip prompts near the top of the view). You can rebind them to alt+up / alt+down in tui.json.

    v1 is maintenance-only, so it's there for anyone who wants it; a v2 version will follow.

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