Browser Use Terminal just shipped: a command-line interface that turns your terminal into a full browser agent. Type a task, watch Chrome execute it. No Python script, no GUI, no boilerplate. Just one line to install and a prompt to run.

The project comes from the same team behind the popular browser-use open-source library, which has accumulated nearly 96,000 GitHub stars. The terminal tool is their bet that the best interface for browser automation is not a web dashboard or a Python SDK, but the terminal itself.

One curl, then you're running

Installation is a single command:

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

Browser Use Terminal is a Rust TUI (terminal user interface) for browser agents, combining a new LLM harness, Browser Harness-style CDP control, real Chrome sessions, and a terminal UI you can actually steer. Once running, you control it through slash commands:

• /auth , sign in (supports Codex auth)
• /model , choose your LLM
• /browser , pick local Chrome, headless Chromium, or cloud
• /update , update the app in place

The tool is free and open-source under the MIT license. Running it costs whatever your LLM API calls cost. The terminal itself has no subscription fee.

What's actually under the hood

The architecture is more interesting than the demo suggests. Browser Use Terminal is a browser-first LLM harness: Rust owns the agent loop and durable state, while the browser runtime gives the model direct CDP control over Chrome.

CDP (Chrome DevTools Protocol) is the low-level wire protocol Chrome exposes for programmatic control. Most browser automation tools (Playwright, Puppeteer) wrap it in high-level abstractions. Browser Use Terminal hands it directly to the model, which means the agent can do anything Chrome can do, including things that higher-level wrappers deliberately prevent.