[BUG] Ctrl key broken in external editor (joe) via Ctrl+G since v2.1.84

Resolved 💬 2 comments Opened Mar 27, 2026 by maziggy Closed Apr 18, 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?

Since upgrading to v2.1.84 (Mar 26), Ctrl key combinations no longer work when using Ctrl+G to open an external editor. Raw escape sequences appear as literal text instead of being interpreted as control characters.

Ctrl key sequences produce raw CSI escape codes as literal text, e.g.:

;5;121~;5;101~

These are kitty keyboard protocol CSI-u sequences (;5 = Ctrl modifier) that joe doesn't understand. It appears Claude Code enables the kitty keyboard protocol but doesn't disable
it when handing off to an external editor via Ctrl+G.

What Should Happen?

Control keys should work when starting external editor from claude code.

Error Messages/Logs

Steps to Reproduce

  1. Configure to use joe as your editor
  2. Open Claude Code
  3. Start joe via [Ctrl]+g
  4. Type in some text
  5. Use Ctrl-Key to move to line start

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.81

Claude Code Version

2.1.85 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

iTerm2

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗