Linux terminal text selection is a total mess

Selecting text in a standard Linux terminal feels like fighting a losing battle. Most of us are stuck in this loop where you can't just hit a single hotkey to grab user input; instead, you're forced into awkward mouse movements or those clunky, multi-step keyboard shortcuts that break your flow. It’s one of those "small" friction points that ends up ruining your entire productivity rhythm when you're deep in a dev workflow.

I eventually found Warp, which actually solves this by wrapping the shell in a remappable text input field. It's easily the only terminal on Linux that treats the command line like a proper text editor. The problem? Warp is absolutely bloated. It's covered in "Sign In" buttons, aggressive AI prompts, and constant cloud integration nagging. It felt hideous to use a tool that constantly asks for my credentials just to run a shell.

When the source code was released, I decided to fork it and strip out everything that didn't belong. The result is Kaden Terminal.

What actually changed in this fork

The goal wasn't to add bells and whistles, but to remove the noise. If you are looking for a clean, focused environment, here is how Kaden differs from the original Warp:

• Zero AI or Cloud Bloat: I stripped out all the AI features, cloud drive prompts, and the constant "Sign In" popups. It’s just a terminal.
• Privacy-First Deployment: There is zero telemetry. No background network requests, no auto-updates pinging a server, and no data being sent to a cloud. It stays local.
• Optimized Build: I refactored the codebase into a more modular structure. This makes the development cycle much faster and significantly cuts down on compile times.
• Better Defaults: I implemented contextual copy/kill bindings to Ctrl-C by default, which makes handling processes and clipboard management feel much more natural.

How to get started

If you want to try it out, I've made it pretty straightforward to test without a complex setup. You can grab a pre-compiled AppImage to get running immediately, or if you want to see how the modular architecture works, you can dig into the source.

If you are doing a deep dive into the code, here is the repository link:

https://github.com/glitcher255/Kaden-Terminal

I'm looking for people to break this. If you use it for your daily AI workflow or just as a standard shell, I need to know where it stumbles. I'm specifically interested in how the text selection holds up under heavy load and whether the modularity affects any specific shell integrations you rely on.