@omercnet/paseo-shared-browser 1.2.0-next.214.1 → 1.2.0-next.227.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/OVERVIEW.md +21 -0
- package/package.json +4 -3
package/OVERVIEW.md
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
Shared Browser runs one real Chromium browser per workspace on the daemon host and shows that same live page to every connected Paseo client, so viewers and agents act on one page with one set of cookies and logins. Many viewers can watch, and one human at a time holds control. Open it from the Command Center, the **Shared Browser** composer pill, or, on Paseo 0.11 and newer, the sidebar footer.
|
|
2
|
+
|
|
3
|
+
## How it works
|
|
4
|
+
|
|
5
|
+
- Chromium runs on the daemon host and uses that host's network, including local development servers. Clients receive streamed frames and send input. Phone and tablet presets emulate the screen size and user agent in Chromium, and do not run Safari.
|
|
6
|
+
- Control is taken and released explicitly, and agents cannot take control from a human who holds it.
|
|
7
|
+
- Each workspace keeps a private browser profile in the Paseo data directory, so logins survive disconnects and reloads. It is kept when a workspace is archived and must be deleted by hand if no longer wanted. It does not use your personal browser profiles.
|
|
8
|
+
- Closing a panel keeps the browser running, and archiving the workspace closes it.
|
|
9
|
+
|
|
10
|
+
## Agent access
|
|
11
|
+
|
|
12
|
+
New agents whose provider accepts external MCP servers receive a local MCP server with tools to check status, capture the page, take and release control, navigate, send input and set the viewport. It offers no JavaScript evaluation, profile access or file access. Agents can visit any address the host can reach, so use it with agents you trust.
|
|
13
|
+
|
|
14
|
+
## Setup
|
|
15
|
+
|
|
16
|
+
- Paseo 0.9, 0.10 or 0.11, and Node.js 24 or newer on the daemon host.
|
|
17
|
+
- Chromium is downloaded when the plugin is installed and stored in the Paseo data directory. On Linux ARM64 nothing is downloaded, and you install a non-Snap Chromium at `/usr/bin/chromium` first. `PASEO_SHARED_BROWSER_CHROMIUM_EXECUTABLE` points the plugin at a different Chromium.
|
|
18
|
+
|
|
19
|
+
## Limits
|
|
20
|
+
|
|
21
|
+
Downloads, uploads, clipboard sync, media permissions, extensions and passkeys are not available. Viewers who are paired with the same daemon can see and control the browser, and the browser runs with the daemon user's file and network access.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@omercnet/paseo-shared-browser",
|
|
3
|
-
"version": "1.2.0-next.
|
|
3
|
+
"version": "1.2.0-next.227.1",
|
|
4
4
|
"description": "One real Chromium session per Paseo workspace, shared live across every connected client.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"browser",
|
|
@@ -32,7 +32,8 @@
|
|
|
32
32
|
"scripts/replace-runtime.mjs",
|
|
33
33
|
"server",
|
|
34
34
|
"shared",
|
|
35
|
-
"paseo-plugin.json"
|
|
35
|
+
"paseo-plugin.json",
|
|
36
|
+
"OVERVIEW.md"
|
|
36
37
|
],
|
|
37
38
|
"type": "module",
|
|
38
39
|
"publishConfig": {
|
|
@@ -48,7 +49,7 @@
|
|
|
48
49
|
"test:smoke": "vitest run tests/browser.smoke.test.ts --testTimeout=30000"
|
|
49
50
|
},
|
|
50
51
|
"dependencies": {
|
|
51
|
-
"@getpaseo/plugin": "0.11.0-beta.
|
|
52
|
+
"@getpaseo/plugin": "0.11.0-beta.5",
|
|
52
53
|
"@modelcontextprotocol/sdk": "1.30.0",
|
|
53
54
|
"agent-browser": "0.37.1",
|
|
54
55
|
"esbuild": "0.28.2",
|