Codeman/.changeset/newline-capability-key-tester.md at fa53a5751ec29fd7ca0ddca5b85e01fb35a584c5

mirror of https://github.com/Ark0N/Codeman.git synced 2026-10-08 16:39:42 +02:00

Files

T

DevvynandClaude Sonnet 5.5 2cf37529e9 fix(terminal): address review: Key tester isolates shortcuts, Codex stays on line feed

- app.js: the shortcut dispatcher returns early for events aimed at a data-raw-keys
  field, so Ctrl+W / Ctrl+L / Escape / Alt+1 / Ctrl+K pressed in the Key tester no
  longer kill the session, clear the terminal or close Settings
- stock.ts: drop Codex's esc-enter (a line feed works); no stock CLI declares a chord.
  The esc-enter path is tested through a clis.json override
- tests: unused port (3194), Ctrl+Enter asserts no keypress, shortcut-isolation test
  (verified to fail without the guard)
- docs/comments point at capabilities.newline; set-input class, trailing whitespace

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

2026-10-03 11:19:42 +08:00

537 B

Raw Blame History

aicodeman

aicodeman
patch

Shift+Enter's newline chord is now registry data (capabilities.newline: line-feed by default, esc-enter available for a CLI whose composer ignores a bare line feed; no stock CLI changes) instead of being chosen in the send-key route. Adds a Key tester under Settings → Terminal & Input that shows the keydown/keypress/keyup events a browser reports, to diagnose a device where a shortcut behaves differently. Keys pressed in the tester no longer trigger app shortcuts (Ctrl+W, Ctrl+L, Escape, ...).

537 B Raw Blame History

537 B

Raw Blame History