On this page
Task guides
Browsers and control sessions
To reuse a sign-in, connect to the browser where you’re already signed in. For an isolated test, launch a separate instance.
Choose a connection
Mearl discovers connected browsers and reports each instance’s browserId and connection state.
- Chrome extension: use the current Chrome profile and its signed-in pages.
- CDP: connect directly to Chrome or launch a separate managed instance.
- Cloud access: Cloud Server relays requests through a Connector on the host that runs the browser. The host uses its configured browser connection.
- Browser Provider: connect another browser platform or device. Supported actions and lifecycle operations depend on the Provider.
mearl browser_listHow a command reaches your browser
With the extension connection, actions run in the selected Chrome profile. If you pick a direct CDP connection, the Native Host sends commands to Chrome over CDP instead.
- CLI / SDK / MCPSubmit a browser action and its target.
- Native HostResolve the browser and session over local IPC.
- Mearl extensionReceive the action over Native Messaging.
- Chrome tabRun the action in the selected profile and return the result.
Keep actions on the same target
Use the returned browserId to select an instance and the tabId for subsequent page actions. A control session pins routing and task ownership while keeping that browser profile’s existing cookies and storage.
mearl tab_open --browser '<browserId>' --session new --payload '{"url":"https://example.com","reuse":"prefer"}'Hand control to a person
Pause the control session for login, a verification prompt, or manual inspection. After the person hands it back, read the page again before continuing. Releasing the session normally leaves the result tabs open.