Skills, MCP and API

Browser

Give an account its own private browser that the agent can drive, and take over yourself when a page needs a human.

Open Browser in your account area for the sessions your agent runs and your saved profile. Live viewing and takeover happen in the owning conversation's enlarged tile.

Private by account

Each account has its own Chrome profile and its own browser process. Sign-ins and cookies stay between sessions, and closing a session does not erase them.

To remove them, open Browser in your account area and select Clear browser data. The button stays disabled while any of your sessions is running.

Browser tools work only for a linked account in a private conversation. A managed Project does not change which account owns the browser, and shared rooms and delegated sub-agents cannot use the tools.

Watch a session and take over

Every session this conversation opened shows a small tile above the composer. Select it to enlarge the live view, and use Take control when the agent asks you to finish a sign-in or check something yourself.

The tile, the takeover lease and the behavior on a phone are described in Watch and take over a browser session.

What the agent can do

The agent reads a page, clicks and fills fields by element reference, and can collect console, network and performance diagnostics. Every action returns a fresh snapshot of the page.

The tools and their limits are listed in Browser tools.

Install and grant access

Check the registry for the plugin's current version and the minimum Chetty version.

Install browser from Settings → Available plugins.
Open Users, select the account and choose Manage under Granted plugins.
Select browser and save.

Note: There is no administrator bypass, so an administrator needs the same grant as anyone else. Tool permissions can still restrict what the agent does.

Installing, enabling, disabling or saving browser settings restarts Chetty. The settings screen says the change is saved and Chetty is restarting; if work is still running, the restart waits for it to settle.

Session settings

The instance-wide settings are in Settings → Plugins → browser. Every field is optional and falls back to a default.

Defaults, allowed ranges and the dependency checks in the Status panel are listed in Browser session settings.

What the host must provide

The host needs Chrome or Chromium, the browser-control library, Xvfb and x11vnc, writable profile storage and the network proxy. A missing piece blocks new sessions.

By default, each account can keep two sessions open while up to four accounts use Chrome at once. Sessions end at the idle timeout or the hard lifetime limit, and the profile stays.

When a page is blocked or a session will not start

A page loads partly or shows a failed tunnel: the proxy refused a destination. See Browser network access.
A session never starts: open Settings → Plugins → browser → Status for the blocked dependency and its fix.
Only the live view fails: read the connection error in the enlarged tile. The agent's tools may keep working.

Example: check a local preview

Ask an administrator to add the preview's hostname to the private network allowlist.
Ask the agent to open that address and check one element on the page.
Follow the page in the conversation tile and take control if you need to finish a sign-in.
Remove the allowlist entry when you no longer need local access.

Proxy limits

Each account's proxy allows 96 concurrent connections and 3,000 requests per minute by default. Administrators change both in Settings → Plugins → browser, between 1 and 200 connections and between 30 and 6,000 requests per minute.

Reaching either limit makes a page load partly or shows a failed tunnel. The reason goes to the daemon log, at most once per reason per minute for that account.

The proxy also always blocks ports 22, 25, 111, 135, 137–139, 445, 2375–2376, 3306, 5432, 6379, 9200 and 11211. Allowlist entries do not open them.