Browsh gives you a text interface backed by Firefox, so JavaScript-heavy pages can render over an SSH session without opening a desktop browser. Firefox is a required part of the setup, which makes Browsh a fit when you need a browser engine on the remote machine.
Check whether Browsh fits the job
Browsh is useful when the browser can run on a Linux machine and you need to view its output through a terminal connection, but it is not a small replacement for a text-only client because Firefox loads and renders the page before Browsh converts the result for your terminal.
That dependency is the first decision. Use Browsh for an SSH or Mosh workflow where a Firefox installation is acceptable, then use a lightweight text browser when you need a browser with no graphical-engine dependency.
Use the supported container route
The maintained Browsh repository documents its container image as the runnable route because it bundles the pieces Browsh needs and avoids separately locating a compatible Firefox executable on the host.
docker run --rm -it browsh/browsh
Run the command in a terminal with Docker installed and an interactive TTY.
Choose a native binary with care
The Browsh downloads page lists static and distribution package builds for several Linux architectures. Check the filename against your machine architecture, then confirm that Firefox is installed and available on your PATH.
The newest GitHub release, 1.8.3, publishes a Firefox extension rather than a native Linux CLI binary. Use the Linux CLI asset from v1.8.2 for your architecture, and inspect release assets before selecting an installation route.
Verify the CLI before you browse
After your installation route places Browsh on PATH, ask it for its version before starting a session. The response confirms that the terminal client can start, not that Firefox can render a page.
browsh --version
If Browsh reports that it cannot find Firefox, install Firefox from your distribution, run the version command again, and use the upstream Firefox path option when your executable has a different name or location.
Open a page and move around
After the version check, start Browsh and enter a URL in its address bar. You can scroll with the arrow keys, Page Up, and Page Down.
- Press Ctrl+L to focus the address bar and type a URL.
- Press Ctrl+R to reload the open page.
- Press Ctrl+T to open a tab, then Ctrl+W to close it.
- Press Ctrl+Q to leave Browsh.
Use the mouse only when your terminal forwards mouse events reliably, with keyboard navigation as the dependable starting point for an SSH session.
Use monochrome mode when colour is the constraint
Browsh can start in monochrome mode when your terminal does not support the colour output it normally uses. This changes the display mode and does not remove the Firefox requirement behind page rendering.
browsh --monochrome
Try monochrome mode after Firefox-backed browsing works in your terminal, and solve the Firefox path or installation issue first if the normal interface cannot start.
Know the support boundary
Browsh remains useful for its narrow remote-browser workflow, but its release assets need inspection before you choose an install route. The official repository and downloads page are the source of truth for the available package, architecture, and container options.
Start with the container when Docker is available. If you choose a native download, verify Firefox discovery and one page load before depending on Browsh for a remote session.