terminal-browser

A real browser that runs inside your terminal

Installation

curl (macOS & Linux):

curl -fsSL https://terminal-browser.sh/install | bash

Note: Run terminal-browser upgrade to upgrade versions

Homebrew (macOS & Linux):

brew install terminal-browser

Windows

To install on Windows you must be using WSL. Terminals with kitty graphics support are also very limited on Windows, the following are terminals I have tested that terminal-browser will work on inside Windows:

• https://noctty.com/

curl -fsSL https://terminal-browser.sh/install | bash

Claude code plugin

Install instructions here

Usage

terminal-browser # launches the browser
terminal-browser open <url> # opens the browser at a url
terminal-browser --split right # opens the browser in a split pane to the right
terminal-browser open --ssh <user@host> <url> # performs all network requests through a remote server
terminal-browser open --transparent <url> # the terminal background will show through pages without a background color
terminal-browser ls # lists open browsers
terminal-browser action # an agent-browser compatible cli for interacting with open terminal-browsers
terminal-browser upgrade # upgrade to the latest version

Use cases:

• You can have a coding agent and website scoped to the same terminal tab
• Your agent has full access to interact with open terminal-browsers, which gives your agent the capability to use the web
• You can ask an agent to make HTML plans and then open them inside terminal-browser, which will automatically open in a split pane next to your agent
• terminal-browser works over SSH, which allows you to preview websites running on remote machines easily

Shortcuts

How does it work?

Terminals that support the kitty graphics protocol, including ghostty, kitty, iTerm2, cmux, vscode and many more, allow a program running in a terminal to display pixels in your terminal. We use this capability to display pixels generated by chromium.

We use electrons offscreen rendering API to read pixels generated by chromium directly from the GPU. Any time a website visually changes, terminal-browser only sends small patches to the terminal that cover changed regions. These choices allows terminal-browser to render smoothly without dropping any frames.

After the browser engine starts and is displaying pixels in the terminal, it needs to be able to read user input for websites to actually work. terminal-browser listens to mouse clicks, mouse position, and keyboard events from the terminal, and then sends synthetic events to chromium based on that data. For any user input events that are not retrievable from the terminal, we read directly from the operating system using a background swift app to listen for input events (non intrusively). This is what allows terminal-browser to implement smooth scrolling, and listen to trackpad events (websites with infinite canvases work great inside terminal-browser!)

The outer UI of the browser is implemented using a graphics engine built on top of rust. The actual UI is defined inside react with a custom react renderer, which allows us to build the UI for the browser using typescript. The UI of the outer browser and the browser content itself is all drawn to the same shared canvas inside the rust engine, which allows us to layer UI on top of the browser.

The underlying logic described here has been abstracted into a javascript library that you can use to build your own graphical applications in the terminal - pixel

SSH

The recommended way to use terminal-browser over ssh is running terminal-browser --ssh <ssh arguments>.

The alternative is running terminal-browser directly on the machine you are shh'd into. This will work, but:

• requires every single frame drawn by the website to be sent over the network
• all user input must be sent over the network before a website can react
• misses out some extra optimizations

terminal-browser --ssh improves on this by running the website on your local device, and simply proxying all network requests made by the browser via the remote machine over ssh. This means you can load any website running on localhost of the remote machine on your local device.

Embedded mode

terminal-browser supports embedding inside of existing TUIs. See examples/embedded for a reference implementation

Telemetry

terminal-browser collects psuedo-anonymous usage events that gives me the ability to see how many people are using the project, which is extremely helpful information for improving the project.

telemetry can be disabled by any of the following:

• DO_NOT_TRACK=1
• TERMINAL_BROWSER_NO_TELEMETRY=1
• disabling via the settings GUI in general
• terminal-browser config set telemetry.usage off

All data that is sent is appended to ~/.local/state/terminal-browser-*/logs/telemetry.jsonl, which allows you to audit no sensitive or identifying information is leaving your machine.

terminal-browser also collects crash reports if terminal-browser fails to start or unexpected errors occur internally. This can be disabled by any of the following:

• DO_NOT_TRACK=1
• TERMINAL_BROWSER_NO_TELEMETRY=1
• disabling via the settings GUI in general
• terminal-browser config set telemetry.crashReports off

If you are using pixel/, no telemetry is ever active and there is nothing to disable.

Roadmap

• linux support ✅
• design mode ⏳
• chrome extensions ⏳

Contributing

• PR descriptions must be authored by humans and explained well, otherwise we will close them
• When making a PR, the motivation must be clearly defined in the description
• Minimize the size of your PR for the best chance to get it landed

To get a local development setup of terminal-browser, the recommended way is to ask a coding agent.

Terminal support

terminal-browser exposes an API that terminals can implement which will allow terminal-browser to reliably script the terminal it is running inside. This allows terminal-browser to open new panes, split panes, send text to a coding agent, and focus panes. Terminals that implement this API can be used to run terminal-browser in a more integrated way.

Implementing the API in your terminal

A terminal implements the API by listening on a unix socket and telling terminal-browser where it is:

1. On launch, listen on a unix socket (for example $TMPDIR/<your-app-id>.terminal-browser.sock). Only accept connections from the same user.
2. Set TERMINAL_BROWSER_TERMINAL_SOCKET=<socket path> in the environment of every shell you spawn.
3. Handle requests. Whenever terminal-browser needs something from the terminal it connects to your socket, writes a JSON request terminated by a newline, and waits for a JSON reply terminated by a newline. Once you have written the reply, close the connection. Every request gets its own connection, so there is no session state to keep.

A request is a JSON object with the method to run, its params, and who is asking. caller is the process that ran terminal-browser:

{ "id": "<unique string>", "method": "<name>", "params": { ... }, "caller": { "pid": 12345, "cwd": "/path" } }

Reply with the same id and either a result or an error:

{ "id": "<same id>", "result": { ... } }
{ "id": "<same id>", "error": { "message": "..." } }

The first request is always hello. Your reply lists which methods you implement, and terminal-browser disables any feature that depends on a method you leave out:

→ { "method": "hello", "params": { "protocol": 1 } }
← { "result": { "name": "my-terminal", "methods": ["getCurrentPane", "split", "listPanes", "neighbor", "sendText", "pasteKey", "focusPane"] } }

A pane is { "id": string, "tab": string }. id is any stable identifier for the pane, tab is shared by every pane that is visible on screen together

API: