claude-code - 💡(How to fix) Fix [FEATURE] Option to disable Up/Down arrow input history recall in VS Code extension

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fix / Workaround

No workaround exists. The behavior is not exposed via any setting or configuration.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

Problem Statement

Up/Down arrows in the VS Code extension chat input recall previous messages when the cursor reaches the top or bottom of the input.

Proposed Solution

Add a VS Code extension setting like claudeCode.inputHistoryNavigation that controls whether Up/Down arrow keys trigger history recall at the input boundary. When disabled, Up/Down should only move the cursor within the text.

Alternative Solutions

No workaround exists. The behavior is not exposed via any setting or configuration.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

Writing a multiline prompt in the VS Code extension chat input, pressing Up to navigate within the text, and accidentally recalling a previous message - losing what I was typing.

Additional Context

No response

extent analysis

TL;DR

Implement a new VS Code extension setting to control the Up/Down arrow key behavior for input history recall.

Guidance

  • Introduce a boolean setting claudeCode.inputHistoryNavigation to toggle the history recall feature on/off.
  • Update the input handling logic to respect the new setting and only move the cursor within the text when the setting is disabled.
  • Consider adding a default value for the setting to maintain the current behavior for existing users.
  • Verify the fix by testing the Up/Down arrow key behavior with the setting enabled and disabled.

Example

// Example setting registration
const claudeCodeSettings = {
  'claudeCode.inputHistoryNavigation': {
    type: 'boolean',
    default: true,
    description: 'Enable input history recall on Up/Down arrow keys'
  }
};

// Example input handling logic update
if (claudeCodeSettings['claudeCode.inputHistoryNavigation']) {
  // Recall input history on Up/Down arrow keys
} else {
  // Move cursor within text on Up/Down arrow keys
}

Notes

The proposed solution requires updates to the VS Code extension's settings and input handling logic. The example code snippet is a simplified illustration and may need to be adapted to the actual implementation.

Recommendation

Apply workaround by implementing the proposed claudeCode.inputHistoryNavigation setting, as it provides a flexible solution for users to control the Up/Down arrow key behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [FEATURE] Option to disable Up/Down arrow input history recall in VS Code extension