Checkout <a href="https://github.com/zhravan/vecna" target="_blank" rel="noopener nofollow">https://github.com/zhravan/vecna</a>
I spend a lot of time on servers and bare metals for deployments, containerizing dev environments, self-hosted setups.
That means a lot of SSH sessions. Jumping between servers. Moving files across machines. Running repetitive ops commands.
Even though I do maintain aliases and scripts, but it still takes time and cognitive energy. I have to remember flags, paths, hostnames, sequences. Small friction that compounds.
I revisited my SSH workflows and started thinking about how much friction I quietly tolerate every day. I have to memorize commands, jumping between terminals, relying on aliases, constant context switching.
So instead of memorizing commands, why not solve it to that reduce cognitive load?
<hr>
That led to Vecna (yes, Stranger Things reference, lol yep xD).
<hr>
Note: So the idea is centralize control, reduce friction, make SSH-driven workflows better and more structured. It is still in a very early stage, mostly ideation and foundational building, but if this problem space resonates with you, feel free to explore the repo.

DevOps Daily

Vecna is an early-stage TUI (terminal user interface) tool aimed at simplifying SSH session management. Built out of frustration with the cognitive overhead of managing multiple servers, it seeks to centralize SSH workflows, reduce reliance on memorized commands and aliases, and minimize context switching for developers who frequently work with remote servers, bare metal, and self-hosted setups. The project is in an ideation/foundational phase and the author is inviting early feedback.

Vecna: TUI simplifying SSH mgmt