I built a Slack client because:wave: was lagging
A developer created a terminal-based Slack client due to performance issues with the existing desktop app. The new client, named slk, aims to provide a faster and more efficient experience for users who primarily communicate through text. Utilizing modern TUI libraries, the client supports features like real-time messaging, images, and multi-workspace functionality.
- ▪The developer was frustrated with Slack's sluggish performance and decided to build a terminal-based client.
- ▪The new client, slk, leverages the Kitty graphics protocol to render true-pixel images and avatars in the terminal.
- ▪It includes features such as real-time messaging, multi-workspace support, and a user-friendly interface with themes.
Opening excerpt (first ~120 words) tap to expand
Home PostsI built a Slack client because :wave: was laggingMay 15, 2026 · 7 min · Grant AmmonsSlack was having a bad day on my machine. Typing :wave: was taking two seconds to autocomplete. Two seconds to autocomplete an emoji! The fan was spinning. The whole app felt sluggish.I have Slack running pretty much nonstop. Most people do. And the whole time I was watching that emoji dropdown crawl I kept thinking.. man, this is just text.Terminals are great at text. The tools I rely on every day - vim, btop, tig, k9s - are a joy to use. They are incredibly fast and responsive. They feel alive. Meanwhile the app that I have to live in all day, where all my conversations happen, is the slowest thing on my machine.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Grant Ammons.
Discussion
0 commentsMore from Grant Ammons
