danmartuszewski/hop: Fast, elegant SSH connection manager with a TUI dashboard


Stop typing long SSH commands. Just hop prod and you’re in.

hop TUI dashboard 

# Before: remembering and typing this every time
ssh -i ~/.ssh/work_key deploy@app-server-prod-03.us-east-1.example.com -p 2222

# After
hop prod
hop prod                         # fuzzy match any server
hop exec production "uptime"     # run command on all prod servers
hop import                       # import your existing ~/.ssh/config
hop                              # launch the TUI, manage everything
go install github.com/danmartuszewski/hop/cmd/hop@latest

Or build from source:

git clone https://github.com/danmartuszewski/hop.git && cd hop && make build
./bin/hop
  • Fuzzy matching – Type hop prod to connect to app-server-prod-03
  • TUI dashboard – Browse, add, edit, delete connections with keyboard or mouse
  • SSH config import – Already have servers in ~/.ssh/config? Import them in one command
  • Multi-exec – Run commands across multiple servers at once
  • Groups & tags – Organize by project, environment, or custom tags
  • Jump hosts – ProxyJump support for bastion servers
  • Zero dependencies – Single binary, works anywhere

Coming Soon: Raycast Extension

Launch connections directly from Raycast. Fuzzy search, tags, environments – all at your fingertips.



Config file location: ~/.config/hop/config.yaml

version: 1

defaults:
  user: admin
  port: 22

connections:
  - id: prod-web
    host: web.example.com
    user: deploy
    project: myapp
    env: production
    tags: [web, prod]

  - id: prod-db
    host: db.example.com
    user: dbadmin
    port: 5432
    project: myapp
    env: production
    tags: [database, prod]

  - id: staging
    host: staging.example.com
    user: deploy
    project: myapp
    env: staging

  - id: private-server
    host: 10.0.1.50
    user: admin
    proxy_jump: bastion          # Connect via jump host
    forward_agent: true          # Forward SSH agent

groups:
  production: [prod-web, prod-db]
  web-servers: [prod-web, staging]

Security note: forward_agent: true exposes your SSH keys to anyone with root access on the remote server. Only enable this for servers you fully trust. Consider using proxy_jump instead when you just need to reach internal hosts through a bastion.

Launch with hop or hop dashboard.

Key Action
↑/k Move up
↓/j Move down
g Go to top
G Go to bottom
/ Filter connections
t Filter by tags
r Toggle sort by recent
Enter Connect to selected
a Add new connection
i Import from SSH config
p Paste SSH string (quick add)
e Edit selected
c Duplicate selected
d Delete selected
y Copy SSH command
? Show help
q Quit

Press p and paste any of these formats:

user@host.com
user@host.com:2222
ssh user@host.com -p 2222
ssh://user@host:port

The connection form opens with fields pre-filled.

Importing from SSH Config

Import existing connections from your ~/.ssh/config file:

From the dashboard: Press i to open the import modal, select which connections to import, and press Enter.

From the CLI:

hop import                   # Import from ~/.ssh/config
hop import --dry-run         # Preview what would be imported
hop import --file ~/.ssh/config.d/work  # Import from custom path

What gets imported:

  • Host alias becomes the connection ID
  • HostName, User, Port, IdentityFile
  • ProxyJump for jump host connections
  • ForwardAgent setting

What gets skipped:

  • Wildcard patterns (Host *, Host *.example.com)
  • Entries without a HostName (alias is used as hostname)

Conflict handling: If a connection ID already exists, the imported connection is renamed with -imported suffix (e.g., myserver → myserver-imported).

hop                          # Open TUI dashboard
hop query>                  # Fuzzy match and connect
hop connect id>             # Connect by exact ID
hop list                     # List all connections
hop list --json              # List as JSON
hop list --flat              # Flat list without grouping
hop import                   # Import from ~/.ssh/config
hop import --file path>     # Import from custom path
hop import --dry-run         # Preview without importing
hop open target...>         # Open multiple terminal tabs
hop exec target> "cmd"      # Execute command on multiple servers
hop resolve target>         # Test which connections a target matches
hop version                  # Show version

Commands like exec and open accept a target that resolves to one or more connections. The target is matched in this order:

  1. Named group — an explicit list of connection IDs defined under groups: in config
  2. Project-env pattern — matches connections by project and env fields (e.g. myapp-prod matches all connections with project: myapp and env: prod)
  3. Glob pattern — wildcard matching on connection IDs (e.g. web*, *-prod-*)
  4. Fuzzy match — falls back to fuzzy matching a single connection ID

You can also filter any target by tag with --tag.

Use hop resolve to preview which connections a target will match before running anything:

hop resolve production              # see what "production" resolves to
hop resolve "web*"                  # test a glob pattern
hop resolve myapp-prod --tag=web    # combine target + tag filter
# Fuzzy connect
hop prod                # matches "prod-web", "prod-db", etc.
hop web                 # matches first *web* server

# Multi-exec with different target types
hop exec production "uptime"           # named group
hop exec myapp-prod "df -h"            # project-env pattern
hop exec "web*" "systemctl status"     # glob pattern
hop exec --tag=database "psql -c '\\l'" # tag filter

# Open multiple tabs
hop open production                    # named group
hop open web1 db1 api1                 # specific IDs
hop open myapp-prod -- "htop"          # with initial command

# List connections
hop list --flat
# Bash (Linux)
hop completion bash | sudo tee /etc/bash_completion.d/hop > /dev/null

# Bash (macOS with Homebrew)
hop completion bash > $(brew --prefix)/etc/bash_completion.d/hop

# Zsh (add to ~/.zshrc)
source hop completion zsh)

# Fish
hop completion fish > ~/.config/fish/completions/hop.fish
-c, --config path>    # Use custom config file
-v, --verbose          # Verbose output
-q, --quiet            # Suppress non-essential output
    --dry-run          # Print SSH command without executing
make build          # Build binary to ./bin/hop
make test           # Run tests
make test-docker    # Run tests in Docker (isolated)
make install        # Install to $GOPATH/bin
make docker         # Build Docker image
# Build image
docker build -t hop .

# Run interactively
docker run -it --rm hop

# Run tests in container
docker build --target tester -t hop-test .
hop/
├── cmd/hop/           # Main entry point
├── internal/
│   ├── cmd/           # CLI commands (cobra)
│   ├── config/        # Configuration loading/saving
│   ├── fuzzy/         # Fuzzy matching
│   ├── picker/        # Connection picker (promptui)
│   ├── ssh/           # SSH connection handling
│   ├── sshconfig/     # SSH config parsing
│   └── tui/           # TUI dashboard (bubbletea)
├── Dockerfile
├── Makefile
└── README.md

MIT License – see LICENSE for details.



Source link

Leave a Reply

Your email address will not be published. Required fields are marked *