[Bug] Shift+Insert not bindable in keybindings.json (insert key unmapped)

Open Beginner friendly
  • Is something wrong?
#108,201 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
83/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
cli

Research direction

Start by locating the function that maps parsed key names to keybinding names; the issue identifies its supported names and says insert is missing. Check how it handles up, down, and the other named keys, then add insert to the bindable names. Done when the provided shift+insert binding fires for the standard ESC[2;2~ sequence.

Written by the indexing model from the issue text.

Description

area:tui bug keybindings platform:linux

Bug Description
Shift+Insert can't be bound in keybindings.json

I want Shift+Insert to paste images (chat:imagePaste), as an
alternative to Ctrl+V. This binding loads without an error but never
fires:

{ "context": "Chat", "bindings": { "shift+insert": "chat:imagePaste" } }

Version: 2.1.319, Arch Linux, Wayland.

The terminal sends the standard sequence ESC[2;2~, and the input
parser turns it into key.name "insert" with shift set. The function
that maps keys to binding names only knows up, down, left, right,
pageup, pagedown, home and end, so "insert" never matches. Ctrl+V
works fine in the same session with an image in the clipboard.

Request: add insert to the bindable key names. Shift+Insert is the
usual paste key on Linux.

Environment Info

  • Platform: linux
  • Terminal: rex
  • Version: 2.1.319
  • Feedback ID: 5e9d1890-27be-4194-9b06-56b94ab3113f
Dominant language
TypeScript
Stars
154k
Forks
25.6k
Avg merge
12h 27m
Merged PRs (30d)
4

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anthropics/claude-code

All issues in anthropics/claude-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.