Docs
Getting started
Hop reaches every computer you can ssh to: their terminals, files, web pages and app windows. There is a desktop app and a hop command. This page gets both working and shows the first few commands.
hop command, with real output.
RecipesShort stories: get pinged, wait for a server, copy a project.
For programshop api, JSON lines, error codes.
The Hop appThemes, including VS Code's, and add-ons.
For AIGive Claude Code every machine with hop mcp.
Librarieslibhop, hop-mux, hop-vt and how they link up.
Command referenceAll commands, made from Hop's own list.
Install
Hop is in private testing and isn't out yet. When it is, how to install it will be here.
Add your machines
A machine is anything ssh <name> already reaches. Hop reads your ~/.ssh/config, so every Host there is a machine with no setup. local is the computer you are at, and is always there.
Host tower HostName tower.local User me Host studio HostName 192.168.1.20
Nothing has to be installed on the other machine for terminals, files and web pages. Hop runs small shell scripts there over your SSH connection and reads what they print. Two optional helpers do more:
- The Hop daemon (the
hopcommand, on the other machine) holds terminal sessions so they keep running when nothing is looking at them, and watches for changes there. Put it on a machine withhop daemon install toweror the Install daemon button on its card in the app. - The window helper (
hop-windows) lists a machine's app windows, takes pictures of them, streams them and reads their buttons and fields../install.shbuilds it on a Mac; on Linux it needs gamescope, GStreamer, ffmpeg and PipeWire.
Hop never asks for a password itself. If a machine asks for one, the app offers to set up key sign-in: you type the password once and it is not asked again. Web pages, tunnels and file previews need that sign-in; a terminal works with a password too.
To give a machine a shorter name, a different SSH destination, or names for the web services it runs, add it to ~/.config/hop/config.toml:
[machines.tower]
host = "me@tower.local"
services = { ollama = 11434 }
hop status, sessions and events already leave out git hosts such as github.com unless you name them. Other hosts that are not computers you use go in hide = ["backup-box"] at the top of the same file, so lists leave them out too.
First commands
hop ls lists the machines, with the services named for each. The dot marks the current machine, the one commands use when you do not name one.
$ hop ls ● local tower ollama:11434 studio
hop status asks every machine at once whether it answers, and how it is doing. A machine that is off or asleep says so instead of holding up the rest.
$ hop status tower tower up Linux load 0.07/16 helper, windows up 1:15
Then try one machine's sessions, ports or windows, or run a command there:
$ hop run tower uname -a Linux tower 6.12.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 11 Jan 2025 09:12:44 +0000 x86_64 GNU/Linux $ hop wait tower:port/22 --timeout 10 tower:port/22 is open (after 0s)
hop help lists the classic commands, and hop do lists every command Hop has, with its level. hop do <command> --help says how to use one.
The app or the command line
Both reach the same machines in the same way, over SSH, and neither needs the other.
| The app | The hop command |
|---|---|
| Tabs of terminals, folders, web pages and live app windows from every machine | One command at a time, for scripts, other programs and AI tools |
| Picks up sessions held on each machine, and shows when one wants you | Lists, reads, types into and starts the same sessions |
| Streams app windows and games, with sound and a controller | Takes pictures of windows and presses their buttons |
| Open it from Spotlight or your launcher | Works on a server with no screen, over SSH, from cron |
The app can be driven from the command line too (hop app …, or the view.* commands), and the hub (hop hub) serves the app's window to any browser. See The command line.