Chrome

chrome operates your own Chrome, the one already logged into everything, not a throwaway browser in a sandbox. That is its entire value, and the reason it needs a full confirmation policy.

Activation

profy-chrome is user_selectable: true with requires: { chrome_connected: true }. Enable it in the plugin panel and keep the Chrome extension online.

Routing: only the desktop path works today

The manifest declares the extension’s local MCP server (ws://localhost:19532/mcp). By design there are two routes: desktop sidecar first, direct WebSocket as a fallback.

Known limitation: the direct WebSocket route is not implemented (marked P2 future in the code). In practice there is only the desktop sidecar path: agent-runtime → sidecar stdio → Electron → extension. Without the desktop app you get:

Error: Chrome extension not connected. The chrome tool '<name>' requires
either Desktop (sidecar) or the Chrome Extension to be active.

So using chrome currently requires Profy Desktop to be running.

Tab lifecycle

list_tabs → claim_tab → interact → (released when the session ends)

You must claim_tab before operating. Navigating without claiming does nothing — the claim is the explicit signal that the expert is now driving this tab, and it is what makes the activity visible to you in the browser.

The 13 actions

Action	Parameters	Notes
`list_tabs`	—	All open tabs (id / url / title)
`claim_tab`	`tab_id` (required)	Take control; missing it returns `'tab_id' is required for claim_tab. Use list_tabs first.`
`navigate`	`url`, optional `new_tab`	Defaults to `about:blank` if no url
`snapshot`	optional `selector`	Accessibility tree with element refs — do this before interacting
`screenshot`	optional `full_page`	`full_page` captures the whole scrollable area
`click`	`ref` or `selector` (one required)	Prefer `ref`
`type`	`ref`/`selector` + `text`	Keystroke by keystroke; fires the page’s key listeners
`fill`	`ref`/`selector` + `text`	Sets the value directly, faster than `type`
`extract`	optional `selector` (defaults to `body`)	Extract page content
`scroll`	`direction`, `amount` (default 300px)	—
`press_key`	`key` (e.g. `Enter`, `Tab`)	—
`execute_js`	`code`	Runs JS in page context, 15s timeout (other actions get 30s)
`browser_auth`	`auth_action`, optional `auth_uri`	See below

Choosing between type and fill: use type when the page’s JS needs to see the keystrokes (search suggestions, live validation, character counters); use fill when you just need the value in place. browser_auth takes one of three auth_action values: get_credentials / store_credentials / clear_session.

Credentials and cookies are never returned to the model. browser_auth runs through the extension’s secure channel — the expert can trigger a credential fill but cannot read the plaintext.

The four-tier confirmation policy

Because this drives your real logged-in browser, write actions are tiered by sensitivity:

Tier	Behavior	Typical cases
Hand back to you	The expert stops and asks you to do it	Password changes, bypassing security warnings, financial operations
Confirm each time	Asks before every execution	Captchas, irreversible deletes, installing unknown content, creating credentials
Pre-authorizable	Proceeds after a one-time grant	Saving passwords, signing up, non-sensitive settings
No confirmation	Runs directly	Read-only browsing, dismissing cookie banners, low-sensitivity permission prompts

The tiers live in two places: the tool docstring (which constrains the model) and the extension’s permission gate (which constrains execution). Even if the model tried to skip a confirmation, the extension would stop it — enforcement sits in the extension, not the prompt.

Workflow reuse (AT2T)

Repetitive browser tasks can be frozen into templates and replayed at zero LLM cost. Three companion tools:

Tool	Purpose	Timeout
`chrome__match_workflow`	Query the extension’s IndexedDB template cache by intent; a hit returns `template_id` + confidence + step summary	10s
`chrome__execute_workflow`	Run the template through the hybrid executor, with self-healing	120s
`chrome__save_trajectory`	Save the interaction just performed as a template	30s

The recommended rhythm: match first → hit means execute (zero LLM) → miss means operate normally → save when done. The second time you do the same thing is dramatically faster. Templates live in the extension’s IndexedDB — local data in your own browser.

Failures and what to do

Error	Meaning	Fix
`Chrome extension not connected`	Desktop not running, or extension offline	Start Profy Desktop; confirm the extension is installed and enabled
`'tab_id' is required for claim_tab`	Skipped `list_tabs`	List tabs first to get an id
`'selector' or 'ref' is required for click`	click/type/fill without a target	Take a `snapshot` first to get refs
`'key' is required for press_key`	Missing `key`	Supply the key name
`'code' is required for execute_js`	Missing code	Supply it
`execute_js` times out	Script ran past 15s	Split into several calls, or use `extract`
A ref no longer clicks	The page changed; the ref is stale	Re-`snapshot`, then click
Chrome missing from the plugin panel	`chrome_connected` is false	Install the extension and keep it online

How it divides work with browser and computer

Dimension	`chrome`	`browser`	`computer`
Browser	Your own Chrome	Isolated Chromium in the sandbox	Any — the whole desktop
Sessions	Yes (all your accounts)	None	Whatever is open on your desktop
Addressing	CSS selector / ref	ARIA selector	element_token / coordinates
Prerequisite	Desktop + extension	None	Desktop
Best for	Sites requiring login, repetitive flows	Public web research, parallelizable	Native applications

The rule is simple: use chrome when your session is needed, browser for public content. browser runs in the sandbox, does not tie up your browser, and never exposes your accounts to the expert.

Keep reading

Browser

The isolated sandbox browser

Computer Use

Desktop-level control

Record and replay

The other way to freeze a sequence of actions

Plugin catalog

All 28 built-in plugins and their activation conditions

Get Started

Core Concepts

Guides

Platform & Account

Deep Dive

Activation

Routing: only the desktop path works today

Tab lifecycle

The 13 actions

The four-tier confirmation policy

Workflow reuse (AT2T)

Failures and what to do

How it divides work with browser and computer

Keep reading

Browser

Computer Use

Record and replay

Plugin catalog

​Activation

​Routing: only the desktop path works today

​Tab lifecycle

​The 13 actions

​The four-tier confirmation policy

​Workflow reuse (AT2T)

​Failures and what to do

​How it divides work with browser and computer

​Keep reading

Browser

Computer Use

Record and replay

Plugin catalog

Activation

Routing: only the desktop path works today

Tab lifecycle

The 13 actions

The four-tier confirmation policy

Workflow reuse (AT2T)

Failures and what to do

How it divides work with browser and computer

Keep reading