Your browser

Let an agent drive Chrome on your machine, with your logins and your network.

Run a session

The agent acts on your real browser. It can browse, run page scripts, and read that Chrome’s cookies and storage. Prefer a dedicated machine over your primary one.

Stop it with holo local stop in any terminal, which stops every session driving this machine.

Install

pip install "hai-agents[cli,browser]"

It works from the Python SDK and the CLI. Create an agent whose environment sets host to user_device, then run a session with it. In Python there is nothing else to set up. From the CLI, serve your browser with holo local browser and point the agent at the session_id it prints (the CLI example uses the agent the Python example creates).

CLI

# Serve the browser and leave it running; it prints the session_id it serves.
holo local browser

# In another terminal, route the agent's browser environment here.
holo run "Open news.ycombinator.com and summarize the top story" \
  --agent local-web \
  -o 'agent.environments[kind=web].session_id=<printed id>'

The Chrome it drives

The SDK attaches to a Chrome with remote debugging open on port 9222. If none is running, it launches one with its own profile in ~/.hai/chrome-profile. That profile persists across sessions: sign in once and the agent finds you signed in next time. The SDK never touches your everyday Chrome profile (Chrome does not allow remote debugging on it).

To drive a different Chrome, start it yourself before the session. Chrome only opens the debugging port with --user-data-dir, so pick a dedicated directory and keep it for the logins you want the agent to have.

macOS

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
  --remote-debugging-port=9222 --user-data-dir="$HOME/chrome-for-agents"

Behavior and limits

When a session starts, the SDK opens a connection inside your Python process. It receives the agent’s actions, carries them out in your browser, and ties the session to this machine. Watch and steer and changes work as in the cloud.

• A Python process drives one browser at a time. A new session on it takes it over and cancels the earlier session.
• The connection closes when your Python process exits, and the sessions it served are cancelled (Chrome stays open). If the connection drops mid-session, the session is cancelled too.
• Vaults, browser profiles, and proxies are cloud browser fields. Your Chrome’s own logins and network fill that role.

Auto-connect scope

You start the session with	Connection
An agent spec or object passed to run_session, start_session, or create_session	The SDK connects your machine for you.
A registered agent referenced by name, or from the H Platform or another machine	Serve the browser with holo local browser, then set the printed session_id on the user_device environment (see the CLI example above).
HAI_AUTO_BRIDGE=0 set	Auto-connect is off. Serve the browser yourself, as above.