[BUG] /keybindings generates invalid config

Status Fixed / completed
Reported on v2.1.91
Maintainer reply None cached
Activity 4 comments · opened Apr 3, 2026 · closed Apr 5, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

  • Run /keybindings
  • Claude generates keybindings.json with defaults
  • Save the file _without changing anything_
  • Immediately see " Found 1 keybinding error · /doctor for details"
  • Run /doctor
  • See └ [Error] Unknown context "Scroll"

What Should Happen?

/keybindings should generate valid keybindings

Error Messages/Logs

Steps to Reproduce

  • Run /keybindings
  • Claude generates keybindings.json with defaults
  • Save the file _without changing anything_
  • Immediately see " Found 1 keybinding error · /doctor for details"
  • Run /doctor
  • See └ [Error] Unknown context "Scroll"

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.91 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] · 6 months ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/42450

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

rcorre · 6 months ago

It is not a duplicate of #42450. The issue isn't that it's writing the file prematurely, but rather that the generated contents are wrong.

rcorre · 6 months ago

Realized #42450 does mention that the generated schema is incorrect

github-actions[bot] · 6 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.