terminal-browser

Why it's ranked here

MIT licensing and a clean split into separate command line, renderer, and storage packages make this a real piece of engineering rather than a demo wrapped around someone else's browser view. It talks to Chromium directly through the debugger protocol instead of screen scraping, injects its own page script to let you grab an element and hand it to an agent, and keeps every open session tracked in a local database instead of ad hoc files. That level of plumbing, done for a genuinely underserved workflow, running a live page beside a terminal session, earns the spot more than the idea alone would.

What's good

The element-picker feature is well thought out: it drops a script into the page that listens for a selection, quietly hides its own overlay artifacts, and hands the copied content back to the host process over a debugging channel, which is a more reliable path than clipboard polling. Recording works the same way, capturing frames, clicks, and a pointer trail with an enforced ten-minute ceiling so nothing runs away and fills a disk. Remote use over an encrypted connection is handled by running the browser locally and proxying only network requests through the remote host, not by shipping every frame over the wire, which keeps it responsive.

Tradeoffs

This is a heavy way to get a browser: a full Chromium and Electron install runs behind the scenes for something a plain terminal command usually handles line by line. It only works in terminal emulators that implement a specific pixel graphics protocol, so plenty of setups will not display anything at all. Only macOS and Linux are supported, and the two platforms are not treated identically. Input handling in particular relies on a separate helper process only on macOS, a sign that the terminal-input story is not yet uniform across operating systems.

How to use it well

This earns a place in a workflow where a coding agent needs to see and click through a real, rendered page next to the terminal it is working in, for example verifying a UI change or walking through a flow before calling a task done. It is also a solid pick for previewing a site running on a remote machine without setting up local networking. It is not the right tool for headless testing, continuous integration, or any terminal that cannot display images, where a conventional headless browser library remains the better choice.

Observed

License

MIT license

Packaging

TypeScript codebase organized as a pnpm workspace of three packages: browser, cli, and store

Persistence

Persists local session and settings state in SQLite via drizzle-orm

Interfaces

Ships as a standalone CLI plus a token-authenticated local bridge used by an editor and agent plugin integration

Platform

Supports macOS and Linux only, with separate code paths for Chromium sandbox setup on Linux and dock and clipboard behavior on macOS

Structural

Depends on an external library for the terminal graphics and input layer rather than implementing that layer in this repository

Structural

Root package.json defines no test script

Architecture

Renders by driving Chromium through Electron and displaying frames via a terminal graphics protocol supported by a specific set of terminal emulators