feat(tui): add configurable Kitty keyboard protocol mode

[LIHUA919]

Summary

Add user-configurable Kitty keyboard protocol setting to resolve keybind issues on different terminals. Users can now choose between "auto", "enabled", or "disabled" modes based on their terminal's capabilities.

Problem

From issue #4997, users were experiencing inconsistent keybind behavior across different terminals:

• ctrl+m and similar bindings not working on iTerm2/Kitty
• Doubled key events on older terminals
• No way for users to configure the Kitty keyboard protocol mode

Solution

1. Configuration Schema

Added kitty_keyboard field to TUI configuration in packages/opencode/src/config/config.ts:

• Type: "auto" | "enabled" | "disabled"
• Default: "auto" (maintains current behavior)

2. TUI Integration

Modified packages/opencode/src/cli/cmd/tui/app.tsx to:

• Fetch config from server on TUI startup
• Map configuration value to OpenTUI's useKittyKeyboard option
• Include debug logging and graceful error handling

3. SDK Types

Regenerated SDK types to include new tui.kitty_keyboard field.

Configuration Example

Users can now configure Kitty keyboard mode in their opencode.json:

{
"tui": {
"kitty_keyboard": "enabled"
},
"keybinds": {
"model_list": "ctrl+m"// Now works reliably!
}
}

Configuration Values

Value	Behavior	Use Case
"auto"	Use {} (best effort)	Default, works on most terminals
"enabled"	Use true	Modern terminals (Kitty, iTerm2, WezTerm)
"disabled"	Use false	Older terminals or when experiencing doubled keys

Testing

• ✅ TypeScript compilation passes
• ✅ Configuration schema validated
• ⚠️ Runtime testing requires manual verification with different terminals

Resolves

#4997 (Keybinds)

🤖 Generated with Claude Code

Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Potential Duplicate Found:

• PR fix(tui): resolve keybind conflicts and missing defaults (issue #4997) #8786: fix(tui): resolve keybind conflicts and missing defaults (issue #4997)
  • Why it's related: This PR also addresses issue Keybinds #4997 (the same issue referenced in your PR). It directly resolves keybind conflicts and missing defaults, which is the root problem your PR is trying to solve with the Kitty keyboard protocol configuration. These PRs may have overlapping solutions or one may supersede the other.

Related PRs (different but relevant):

• PR fix: support non-Latin keyboard layouts (e.g., Korean IME) for keybindings #5956: fix: support non-Latin keyboard layouts (e.g., Korean IME) for keybindings

  • Addresses keyboard input handling issues in keybindings

• PR feat(keybinds): support physical keycode-based keybindings for non-English layouts #6753: feat(keybinds): support physical keycode-based keybindings for non-English layouts

  • Related to keybinding system improvements

Recommendation: Check PR #8786 first as it directly addresses issue #4997. Verify that your PR's approach complements or doesn't duplicate that fix.

[github-actions]

Closing this pull request because it has had no updates for more than 60 days. If you plan to continue working on it, feel free to reopen or open a new PR.