terminal-browser
A real browser inside the terminal with a CLI for the agent: a coding agent opens sites and interacts with them in the same tab
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- The agent interacts with open browsers and web pages
- It can perform actions on sites in open sessions
Install
Manual install
curl -fsSL https://terminal-browser.sh/install | bashmacOS and Linux. Upgrade with terminal-browser upgrade. Also available as brew install terminal-browser.
This is third-party code. Review the repository files before installing.
What it does
terminal-browser is a real chromium-based browser that draws pages right in the terminal through the kitty graphics protocol. Its CLI gives a coding agent web access: the terminal-browser action command is agent-browser compatible and lets the agent interact with open browsers, while ordinary commands open URLs, show the browser in a split pane and list open windows. It works over SSH: the site loads on your device while network requests are proxied through the remote machine, which is handy for viewing sites on the server's localhost. It ships a Claude Code plugin, TUI embedding and element selection on a page to send to the agent.
Who it is for. For developers who work with a coding agent in the terminal and want to give it web access in the same tab.
Good fit when
- You want the agent to open sites and interact with them from the terminal
- You want the site and the agent in one terminal tab
- You want to preview sites from a remote machine over SSH
Not a fit when
- Your terminal does not support the kitty graphics protocol
- You cannot let the agent interact with open browsers
Example request
Open my local site in terminal-browser and check whether the login form worksLimitations
Rendering needs a terminal that supports the kitty graphics protocol, such as ghostty, kitty or vscode. The terminal-browser action CLI lets the agent interact with open browsers, so grant access deliberately. On some systems a background system app is used to read input. Linux is supported, and some features are still planned.
How to disable. Uninstall terminal-browser installed via brew or the script and remove its Claude Code plugin via /plugin.
Security check
- The agent interacts with open browsers and web pages
- It can perform actions on sites in open sessions
README in short
The README describes terminal-browser as a real chromium browser that draws pages in the terminal through the kitty graphics protocol using Electron offscreen rendering. The CLI opens URLs, shows the browser in a split pane, lists windows and, via terminal-browser action, gives the agent web access. Install via a curl script or Homebrew, with a Claude Code plugin. It supports SSH with request proxying, TUI embedding and element selection to send to the agent. The outer UI is built on a Rust engine with a React renderer. MIT licensed.
FAQ
How does the agent get web access?
Through terminal-browser action, an agent-browser compatible CLI for interacting with open browsers.
Does it work over SSH?
Yes. terminal-browser open --ssh loads the site on your device and proxies requests through the remote machine, including sites on its localhost.
Related
CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP
A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief
The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills