You know that jarring feeling when you’re flying through a terminal, fingers dancing across keys, and suddenly you have to stop, grab your mouse, and click a link? Kovid Goyal just made that friction a whole lot smoother in Kitty. But before you celebrate, you need to realize what you’re actually giving up.
Kitty’s new level of mouse support is being hailed as a massive accessibility win. And it is. You can now select text, click links, and navigate with unprecedented GUI-like ease. But this isn’t just an upgrade. It’s a fundamental design trade-off disguised as a feature.
The moment you reach for the mouse, you surrender the very speed that brought you to the terminal in the first place.
We’ve spent years building calluses and muscle memory. We learned Ctrl+A, Ctrl+E, tmux splits, and vim motions because the payoff was absolute, unadulterated speed. The terminal was a sanctuary from the point-and-click world. Now, Kitty is bridging the gap, making it dangerously easy to fall back into lazy GUI habits.
For new users, this is brilliant. It lowers the barrier to entry. But for veterans? It’s a cognitive trap. When you can just highlight and drag to copy a block of code, the incentive to learn the keyboard-native way slowly dies. I saw this firsthand when a junior dev on my team gave up on mastering fzf because Kitty’s mouse scrolling and clicking were ‘good enough.’ Good enough is the enemy of greatness.
Accessibility is a feature, but muscle memory is a superpower. You can’t optimize for both without one slowly rotting the other.
If you use Kitty daily, this update changes your relationship with your core tool. It whispers in your ear that taking the easy path is okay. It offers the allure of easier text selection while quietly eroding your hard-won keyboard fluency. Don’t let it. Use the mouse if you must, but never forget why you came to the terminal. The keyboard is what made you fast. The mouse just makes you average.
FAQ
Q: Isn't easier text selection just a better user experience?
A: For casual use, yes. But for deep, sustained workflows, reaching for the mouse breaks your flow state. True terminal efficiency comes from keeping your hands on the home row at all times.
Q: Should I disable mouse support in Kitty?
A: Not necessarily, but you should be hyper-aware of when you use it. Treat the mouse as a last resort, not a crutch, to protect your keyboard muscle memory.
Q: Is mouse support actually ruining modern terminals?
A: It's diluting them. By making terminals behave more like GUI text editors, developers risk losing the unique, keyboard-first culture that makes terminal tools exponentially faster than graphical alternatives.