<p align="center"> <img src="assets/icon.png" height="128"> </p> <h1 align="center">hop</h1> <p align="center"> Stop typing long SSH commands. Just <code>hop prod</code> and you're in. </p> <p align="center"> <img src="hop.gif" alt="hop TUI dashboard"> </p>

Why hop?

# 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

Install

Homebrew (macOS/Linux)

brew install danmartuszewski/tap/hop

Go

go install github.com/danmartuszewski/hop/cmd/hop@latest

From source

git clone https://github.com/danmartuszewski/hop.git && cd hop && make build
./bin/hop

Features

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
Export - Export filtered connections to YAML for sharing or backup
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
MCP server - Let AI assistants manage your servers — search connections, run commands, check status across projects
Mosh support - Use mosh instead of SSH for roaming and unreliable connections
Zero dependencies - Single binary, works anywhere

See all features in action: Demo recordings

Raycast Extension

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

Install from Raycast Store

Configuration

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

version: 1

defaults:
  user: admin
  port: 22
  # use_mosh: true             # Uncomment to use mosh for all connections

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

  - id: remote-dev
    host: dev.example.com
    user: dan
    use_mosh: true               # Use mosh instead of SSH

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.

Mosh Support

Mosh (mobile shell) is useful for connections over unreliable networks — it handles roaming, intermittent connectivity, and high latency gracefully.

Global default — enable mosh for all connections:

defaults:
  use_mosh: true

connections:
  - id: remote-dev
    host: dev.example.com

  - id: legacy-server
    host: old.example.com
    use_mosh: false              # Override: use SSH for this one

Per-connection — enable mosh for specific connections:

connections:
  - id: remote-dev
    host: dev.example.com
    user: dan
    use_mosh: true

One-off — use the --mosh flag without changing config:

hop connect myserver --mosh
hop myserver --mosh

Per-connection use_mosh: false overrides the global default. SSH options (port, identity file, proxy jump, agent forwarding) are automatically passed to mosh via its --ssh flag. Mosh requires both the local mosh-client and mosh-server on the remote host.

Note: hop exec always uses SSH regardless of use_mosh, since mosh is designed for interactive sessions.

TUI Dashboard

Launch with hop or hop dashboard.

When you connect to a server from the dashboard (by pressing Enter), the SSH session starts, and the dashboard automatically returns after the session ends. This lets you quickly hop between servers without restarting the TUI each time.

For one-shot connections that exit to your terminal, use:

hop <query>           # fuzzy match and connect
hop connect <id>      # connect by exact ID

Keyboard Shortcuts

| Key | Action | |-----|--------| | ↑/k | Move up | | ↓/j | Move down | | PgUp/PgDn | Move by page | | g | Go to top | | G | Go to bottom | | / | Filter connections (supports multi-keyword AND search) | | 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 | | x | Export connections to YAML | | y | Copy SSH command | | ? | Show help | | q | Quit |

Filtering Connections

Press / to filter connections by typing keywords. The filter supports multi-keyword AND logic - separate keywords with spaces to find connections matching all terms.

Examples:

prod - matches connections containing "prod"
prod web - matches connections containing both "production" AND "web"
kaf staging - matches connections with both "kafka" AND "staging"

The filter searches across connection IDs, hosts, projects, environments, and tags.

Quick Add with Paste

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).

Exporting Connections

Export a subset of connections to a YAML file for sharing, backup, or transferring to another machine.

From the dashboard: Press x to open the export modal. Only currently filtered connections are shown — apply text or tag filters first to narrow the selection. Toggle items with Space, then press Enter to save.

From the CLI:

hop export --all                          # Export all to stdout
hop export --all -o backup.yaml           # Export all to a file
hop export --project myapp -o myapp.yaml  # Export by project
hop export --tag database                 # Export by tag
hop export --env production               # Export by environment
hop export --id web-1,web-2              # Export specific connections

At least one filter flag or --all is required. Filters combine with AND logic.

CLI Commands

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 export --all             # Export all connections to stdout
hop export --project <name>  # Export filtered connections
hop export --tag <tag> -o f  # Export to file
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 mcp                      # Start MCP server (read-only)
hop mcp --allow-exec         # Start MCP server with remote exec
hop version                  # Show version

Targeting

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

Named group — an explicit list of connection IDs defined under groups: in config
Project-env pattern — matches connections by project and env fields (e.g. myapp-prod matches all connections with project: myapp and env: prod)
Glob pattern — wildcard matching on connection IDs (e.g. web*, *-prod-*)
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

Hop

Install / Use

README