​
Two ways to use the Browser

You can browse beside Rudder. Open a link in the Side Panel, move the same live tab into the main Messenger work area, or send it to your system browser. Moving a tab keeps its history, form state, scroll position, and zoom. An Agent can use controlled tabs. Supported local Runs can navigate, read, click, type, and capture screenshots when Agent Browser access is enabled.

​
Example: check a published page

Before writing a launch note, an Agent opens the public setup page in its own tab, checks the current command, and captures a screenshot. It cannot read the operator’s open tabs or a tab owned by another Run.

​
Website login is shared on one local instance

The operator Browser keeps one website profile for the current operating-system user and local Rudder instance. If you sign in to a site in one organization, the same site can still be signed in after switching organizations. This makes normal browsing convenient, but it also means you should treat the Browser as one shared local identity. Clearing Browser data affects every organization in that local instance.

​
Agent tabs stay isolated

An Agent can use only the browser tabs Rudder opened for that piece of work. It cannot read raw cookies, saved passwords, arbitrary page scripts, or tabs from another Run. Choosing the system browser for your own links does not disable Agent Browser access. Turning off Agent access closes controlled Agent tabs but keeps your operator tabs and website data. Agent Browser is available in Desktop local-trusted mode for supported local Codex, Claude, OpenCode, and Pi runtimes. On macOS, you can import supported cookies from a selected Chrome, Edge, or Brave profile after confirmation. See Permissions and platforms.