![]() |
![]() |
Linux / macOS:
curl -sSL https://raw.githubusercontent.com/shravan20/vecna/master/scripts/install.sh | shWindows (PowerShell):
irm https://raw.githubusercontent.com/shravan20/vecna/master/scripts/install.ps1 | iex- Go:
go install github.com/shravan20/vecna@latest - From source:
make build
./bin/vecna # or bin\vecna.exe on Windowsmake install installs the binary; config is created on first run with default run commands.
Windows: Config lives at %USERPROFILE%\.config\vecna\config.yaml. File transfer and “Open SFTP in new terminal” work when the OpenSSH client is installed (default on Windows 10/11).
vecna # Launch TUI
vecna version # Print versionPath: ~/.config/vecna/config.yaml
Created on first run with default run commands. Edit to add hosts and more commands. Example:
hosts:
- name: prod
hostname: 192.168.1.100
user: admin
port: 22
identity_file: ~/.ssh/id_rsa
tags: [production]
proxy_jump: bastion # optional: name of another host to use as jump/bastion
commands: # optional: saved commands for "Run command" (r)
- label: "disk usage"
command: "df -h"
- label: "memory"
command: "free -m"Issues and PRs welcome. Tag releases with semver (v1.0.0); CI builds and publishes.
About
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?
That led to Vecna (yes, Stranger Things reference, lol yep xD).
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.
MIT


