Seth/kitty-workbench
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix: actively recommend kitty for desktop users, warn about SSH and password prompt caveats

Browse Source
This commit is contained in:
Mortdecai
2026-03-29 20:27:55 -04:00
parent f5dd2a6f58
commit 26c9d2cd77
1 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
INSTALL.md
+15 -6
View File
@@ -96,16 +96,25 @@ Based on what you detected, determine:
Based on your evaluation, present the user's options conversationally. Be specific about what they have and what each option gives them. Based on your evaluation, present the user's options conversationally. Be specific about what they have and what each option gives them.
**If over SSH:** **If over SSH:**
Tell the user tmux is their only practical option. If tmux is installed, recommend it. If not, recommend installing it (`apt install tmux` / `brew install tmux`). Mention that images will work if their local terminal supports sixel. Tell the user tmux is their only practical option. If tmux is installed, recommend it. If not, recommend installing it (`apt install tmux` / `brew install tmux`). Mention that images will work if their local terminal supports sixel. Do NOT recommend kitty for SSH users.
**If native/remote desktop with tmux available:** **If native/remote desktop (sitting at the machine or RDP/VNC):**
Present tmux as the ready-now option. Optionally mention kitty as an upgrade for better image quality if they want to install it later. **Recommend kitty** — it gives the best experience (native splits, best image quality via kitty graphics protocol). Present it as the primary recommendation, with tmux as the quick-start alternative if they don't want to install anything new.
**If native/remote desktop in kitty:** However, warn about this caveat:
Great — they get the best experience. Just need `allow_remote_control yes` in kitty.conf. > **Note:** If you install kitty and use it as your terminal, be aware that some AI CLIs (like `gemini`) may prompt for passwords or authentication tokens during setup. Kitty uses its own keyboard protocol which can interfere with password prompts in some CLI tools. If you hit issues with password/auth prompts not working in kitty, switch to your regular terminal for that step, then come back to kitty.
Installation:
- Linux: `curl -L https://sw.kovidgoyal.net/kitty/installer.sh | sh /dev/stdin`
- macOS: `brew install --cask kitty`
- After install: add `allow_remote_control yes` to `~/.config/kitty/kitty.conf`
- Launch your AI CLI from within kitty to get the full experience
**If already in kitty:**
Great — they get the best experience. Just need `allow_remote_control yes` in kitty.conf. Note: existing kitty windows must be restarted for config changes to take effect.
**If no tmux and no kitty:** **If no tmux and no kitty:**
Recommend installing tmux (simplest) or kitty (best experience). Plain backend works but has no split panes. Recommend kitty (best experience) or tmux (simplest install). Plain backend works but has no split panes — the TUI opens in a separate window.
## Step 4: Execute Setup ## Step 4: Execute Setup