Browser Use Terminal Explain Like I'm 5 Wiki

Pages

1. Explain It SimplyWhat this repo does in plain language, the simplest useful analogy, and the few ideas the reader should remember.
2. Install, Run, and Pick a BrowserHow the repo turns shell commands into Rust binaries, where state lives, and why the browser choice can be local Chrome, headless Chromium, or Browser Use cloud.
3. The Terminal WorkbenchThe TUI is the steering wheel: it renders the current work, accepts keys and slash-style choices, starts agent runs, and keeps the screen usable while work is live.
4. The Agent Loop and Its ToolsThe agent loop is the careful helper: it asks a model provider for the next move, exposes browser and filesystem tools, records events, and stops only when a done, failure, or cancellation path is reached.
5. The Browser DriverThe browser layer is the remote-control box: Rust owns CDP connections and browser lifecycle, while Python helper code runs page scripts, collects artifacts, and reports browser events without forcing one model vendor.
6. Remember This MapA closing recap: the TUI is the steering wheel, the agent loop is the helper, the browser driver is the remote-control box, and the store plus tests are how the repo remembers and proves what happened.