danmartuszewski/hop

Stop typing long SSH commands. Just hop prod and you're in.
Why hop?
Install
Homebrew (macOS/Linux)
Go
From source
Install with an AI agent
Using Claude Code, Codex, Cursor, or another coding agent? Paste the block below into your agent and it will pick the right install path for your machine, register hop's MCP server, and verify the install.
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
- **Landing directory** - Drop straight into a predefined working directory on connect
- **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
> **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:
**Per-connection** — enable mosh for specific connections:
**One-off** — use the --mosh flag without changing config:
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.
Landing Directory
Set remote_dir to have a connection drop you straight into a specific directory instead of $HOME:
On connect, hop runs cd into the directory and then hands you a normal interactive login shell, so the session behaves exactly like a regular SSH login — just somewhere else. A few details worth knowing:
- **Absolute paths and ~ both work.** ~ and ~user are expanded by the remote shell.
- **Forgiving by design.** If the directory is missing or inaccessible, you still land in a shell (in $HOME) rather than getting bounced off the host.
- **Works in new tabs too.** hop open carries the landing directory into every terminal it launches.
> **Note:** remote_dir is ignored when you pass an explicit command (e.g. hop connect web -- uptime or hop exec), since those aren't 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:
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) |