Enable trusted plugins on the target Paseo daemon, then install from npm:
\npaseo plugin install npm:@omercnet/paseo-shared-browser\npaseo plugin ls\nWhen Paseo acquires the npm package, it runs the npm run prepare:runtime build hook automatically. The\nhook installs the pinned browser runtime, builds both supervisor.cjs and shared-browser-mcp.cjs\nunder a versioned directory in $PASEO_HOME/plugin-data/shared-browser, then atomically updates the\nruntime-current pointer. Existing processes keep using their immutable runtime during an update.
The build requires Node.js 24 or newer and npm on the daemon host. On Linux x64, macOS, and\nWindows, runtime preparation installs and stages the platform's Chrome for Testing distribution. On\nLinux ARM64, where that download is unavailable, the installer automatically uses native Chromium\nfrom /usr/bin/chromium. Install a non-Snap Chromium build with the system package manager before\nadding the plugin. Set PASEO_SHARED_BROWSER_CHROMIUM_EXECUTABLE to an absolute path when Chromium\nis installed elsewhere. The plugin does not emulate x64 Chromium on Linux.
On Windows, the upstream installer retains its Chrome download cache under the OS user profile.\nBefore upgrading the plugin on Windows, close active Shared Browser sessions and stop the Paseo\ndaemon; Windows does not allow the installer to replace runtime executables that are still running.
\nOpen a workspace, search the Command Center for Open Shared Browser, or …
","readmeText":"# Shared Browser\n\nA Paseo plugin that runs one real Chromium browser per workspace on the daemon host and shares its\npages with connected Paseo clients and workspace agents. Version 1.0 replaces the previous browser\nruntime in place with a plugin-owned, pinned `agent-browser` runtime; existing installations keep\nthe `shared-browser` plugin ID and upgrade without installing a second plugin.\n\nEach browser tab is a real page in the same Chromium profile, so tabs share site logins and cookies.\nEach client and agent selects a tab independently. Viewers of the same tab share its live page,\nnavigation and control state. Human control remains server-authoritative and takes priority over\nagent input on that tab.\n\n## Demo\n\nhttps://github.com/user-attachments/assets/37d09fff-0750-440d-983d-426150b0724d\n\n## Screenshots\n\nBoth PNGs show the same isolated Chromium session from a dedicated Paseo test daemon. They were\ncaptured at 2× pixel density after browser DevTools verified the rendered page contained no private\norganization names.\n\n### Wide desktop\n\n\n\n### Compact client\n\n\n\n## Runtime model\n\n- The plugin server runs beside the Paseo daemon and starts one `agent-browser` session and Chromium\n process per open browser workspace. Browser execution, profiles, IPC, and network access are on the\n daemon host, not on the viewing phone, browser, or desktop app.\n- A workspace can have up to eight tabs. Each tab has its own page, capture stream, viewport and\n controller. Selecting a tab affects only the selecting viewer or agent. Closing a tab removes it\n for every participant viewing it; the last tab stays open until the browser is closed.\n- Viewers can select a browser action while observing. A dialog offers control, names the current\n controller when a takeover is needed, and continues the selected action after control is granted.\n Closing a tab or browser still requires its own confirmation. Actions that need a fresh frame wait\n for one before sending input.\n- The plugin owns `agent-browser` version `0.39.1`, its IPC directory, and the Chromium executable.\n It strips inherited `AGENT_BROWSER_*` variables and sets `AGENT_BROWSER_SOCKET_DIR`,\n `AGENT_BROWSER_IDLE_TIMEOUT_MS=0`, `AGENT_BROWSER_STREAM_PORT=0`, and\n `AGENT_BROWSER_NO_AUTO_DIALOG=1` itself.\n- By default every client receives JPEG frames from CDP `Page.startScreencast` or bounded\n screenshots, and no capture extension is loaded into Chromium. When the daemon is started with\n `PASEO_SHARED_BROWSER_VIDEO=1`, desktop/web clients with usable WebCodecs receive encoded\n workspace-tab video instead; other clients keep JPEG.\n Remote input supports mouse hover, wheel scrolling, continuous dragging, native touch pan/pinch,\n tap, double-tap, right-click, text, and special keys.\n- Device presets for Desktop Chrome, iPhone 15 Pro, Pixel 7, and iPad Pro 11 change Chromium's\n viewport, device pixel ratio, touch behavior, platform, and user agent. A phone can view and\n control the shared browser, but the rendered browser remains Chromium. An iPhone preset is mobile\n emulation, not WebKit, iOS, or real Safari.\n\n## Lifetime and persistence\n\nThe browser runtime is held by a detached supervisor rather than by a particular Paseo client or\nplugin subprocess. Closing a panel, disconnecting a client, or losing the plugin bridge invalidates\nthat client's viewer/control tokens but does not immediately close Chromium. A replacement plugin\nbridge can reclaim the existing workspace runtime. If no bridge reconnects, the supervisor closes\nall orphaned runtimes after a 120-second grace period. A missed heartbeat fences the old bridge after\n30 seconds; the bridge sends heartbeats every 10 seconds.\n\nThe browser actions menu has **Close shared browser**. After confirmation,\nit stops that workspace's Chromium process and ends every viewer and agent connection to it, even\nwhen their panels are active. Background reconnects cannot reopen a deliberately closed browser.\nA person can select the prominent **Open shared browser** button in the closed panel to start a new runtime with the\nretained profile. Closing the browser does not remove saved cookies or site data.\n\nEach workspace gets a private profile under\n`$PASEO_HOME/plugin-data/shared-browser/profiles/