Local Agent Browser CLI is now part of Agent Browser CLI. The
gologin-local-agent-browser-cli npm package is deprecated: install gologin-agent-browser-cli and use --runtime local. Scripts that call gologin-local-agent-browser keep working, see Migrate from Local Agent Browser CLI.cloud runtime runs sessions in Gologin Cloud Browser. The local runtime runs them in Orbita, the Gologin browser, on your own machine. This page covers the local runtime. Snapshots, refs and other commands work as described on the Agent Browser CLI page.
When to use local vs cloud
Requirements
- Node.js 20 or later. The local runtime starts Orbita through the Gologin Node.js SDK, which needs Node.js 20.
- A Gologin API token in
GOLOGIN_TOKEN. See Get a token. - A profile ID for every session. Unlike the cloud runtime, the local runtime doesn’t create temporary profiles.
- Orbita. If it isn’t installed yet, the Gologin SDK downloads it to
~/.gologin/browseron first launch. If Orbita is somewhere else, setGOLOGIN_EXECUTABLE_PATH.
Install
gologin-agent-browserruns browser sessions in the cloud unless you choose local.gologin-local-agent-browseris a compatibility alias that runs commands in the local runtime.
Choose the local runtime
Pass--runtime local to a command, or set the runtime once for the whole shell:
--local and a leading local work too: gologin-agent-browser local open https://example.com --profile your_profile_id.
Gologin API commands such as
api, browser and proxy always call the API directly, whatever the runtime.
Environment variables
The local runtime keeps its config, profile list and job history in
~/.gologin-local-agent-browser/, the same folder the old CLI used.
Quick start
--visible (or --headed) and --headless (or --background) choose the window mode for one open. open-visible and open-background are shortcuts for them.
Browser commands
Session commands are the same as in the cloud runtime:snapshot, click, type, fill, find, wait, press, scroll, tabs, cookies, storage-export, eval, screenshot, pdf, upload and more. See the command reference. back, forward and reload work only in the cloud runtime for now.
find locates an element on the live page and acts on it in one step. Use it when refs go stale on dynamic pages:
Profile commands
These commands run in the local runtime even without--runtime local:
profile-create and profile-update take a use-case template and a proxy. --proxy-country us adds a Gologin proxy, --proxy-host with --proxy-port sets your own.
Runbooks and batch jobs
A runbook is a JSON file with a list of CLI steps:targets.json lists the profiles:
jobs and job <jobId>. --status takes running, ok, partial or failed:
Migrate from Local Agent Browser CLI
- Scripts that call
gologin-local-agent-browserkeep working. The command now comes fromgologin-agent-browser-cli. - Profiles, config and job history in
~/.gologin-local-agent-browser/stay where they are. - For AI agents, install the Agent Browser skill. It covers both runtimes, and the separate Local Agent Browser skill is deprecated.
Related
- Agent Browser CLI — full command reference and the cloud runtime
- Gologin Web Access CLI — scraping and browser commands in one CLI
- AI Skills — skills for Claude Code and other agents
- Node.js SDK — run profiles from your own code
npm package
gologin-agent-browser-cli
Source code
GologinLabs/agent-browser