Getting started
Install Clout Browser on macOS, Windows or Linux, sign in and prepare your first browser engine.
On this page
Download Clout Browser from Download or Downloads in your account portal. Use the installer for the computer you are setting up.
Choose the right download
| Platform | Current file | Version |
|---|---|---|
| macOS, Apple silicon or Intel | Clout-Browser-0.0.52-universal.dmg | 0.0.52 |
| Windows, x64 | Clout-Browser-Setup-0.0.50.exe | 0.0.50 |
| Linux, x64 AppImage | clout-browser-0.0.52-x86_64.AppImage | 0.0.52 |
| Linux, Debian package | clout-browser-0.0.52-amd64.deb | 0.0.52 |
| Command line, Node 24 or later | cloutctl-0.0.52.zip | 0.0.52 |
The screenshots in this manual show 0.0.52. The redesigned profile form, Browser engines page and MCP & Local API page arrived in 0.0.51; Windows 0.0.50 can show the earlier layout.
The macOS build is signed. Windows and Linux are listed as unsigned. Check the version beside the download: platforms do not always receive a release together.
macOS
- Open the
.dmg. - Copy Clout Browser to Applications.
- Open it from Applications.
- Keep the app open while you complete sign-in in your system browser.
The universal app supports both Apple silicon and Intel. If macOS refuses a downloaded file, download the current installer again before changing security settings.
Windows
- Run
Clout-Browser-Setup-0.0.50.exe. - Follow the installer.
- Open Clout Browser.
The Windows installer is unsigned. The portal explains the “Windows protected your PC” warning and the More info and Run anyway controls. Verify that you downloaded it from Clout before continuing.
Linux AppImage
Open a terminal in the download directory:
chmod +x clout-browser-0.0.52-x86_64.AppImage
./clout-browser-0.0.52-x86_64.AppImageAn AppImage must be executable before it can run. Use the Debian package instead if you prefer installation through your system package manager.
Linux Debian package
sudo apt install ./clout-browser-0.0.52-amd64.debThe desktop needs a graphical session. For a server without a desktop, use cloutctl; that chapter also covers running visible browsers on a virtual display.
Sign in
Press Sign in with your browser in Clout. It opens your system browser at the Clout account portal. Finish there and return to the app. The app receives a session through the return flow; you do not enter your account provider’s password into the Clout window.
Sign-in registers the computer to your account. If the computer is not connected for profile sync, Settings → Runtime preferences → This computer offers Connect. Computers and sync explains the difference.
An account with no plan sees plan selection and a starter profile. Choose the plan you need through Billing. Prices and current allowances are on Pricing.
Complete first-time setup
The first-time flow walks you through the plan, browser engine, bringing profiles across and the tour as needed. The engine is a separate download; installing the app alone does not install every browser version your profiles use.
You can reopen setup from Settings → Runtime preferences → Getting started → Show again. You can also go straight to Browser engines or Importing profiles.
Your first useful check
Create a named profile, set its proxy, then press Check proxy. Review the reported exit before starting the profile. A stored gateway address is not the same thing as the public exit IP.
The full form is covered in Creating profiles. If Start waits for an engine, let that download finish; the pending profile opens after its engine is installed.
Keep the app current
Use Check for updates in Settings. The update dialog shows the staged version and the number of running profiles. Update now restarts the app; running browsers stay open and are picked up again when the app returns. Later defers the prompt for this app session. If this copy cannot update itself, download the current installer.
Read Changelog for release changes. The CLI is upgraded separately by replacing its bundle.
Follow the guide for your operating system
Use Sign-in and first-time setup for every onboarding state. The Desktop reference maps screens and dialogs to their controls.