Kitty CSI-u NumLock key handling in CLI
Cluster 88221 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #90561 on 20 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #90561. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #90561. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug report and two related fixes addressing how the CLI handles kitty terminal CSI-u escape sequences when NumLock is active. The work centers on correctly mapping modifier bits so key combinations are interpreted rather than passed through as raw codes.
Open issues0
Open PRs0
Fixes on record
-
#90561 fix(cli): key combos survive NumLock/CapsLock under kitty CSI-u (salvage #89676 + #90291)
files:
contributors/emails/[redacted:email],hermes_cli/pt_input_extras.py,tests/cli/test_modify_other_keys_aliases.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#88673 fix(cli): map kitty CSI-u sequences with the num_lock modifier bit · merged via another change →
#90561,#89676,#90291
Closed issues · 1
- Closed#88221[Bug]: kitty + NumLock on: CLI inserts raw CSI-u codes ([127;129u) instead of acting on keys
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- hermes cli
- Merged PRs
- #90561
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Aug 2026