@agentconnect.md/computer 2.16.0-rc.3 → 2.17.0-rc.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/README.md CHANGED
@@ -28,8 +28,8 @@ published with each release too (see [Run in Docker](#run-in-docker)).
28
28
  - `setup` / `doctor` on macOS, Linux (X11 and GNOME Wayland) and Windows; a macOS LaunchAgent
29
29
  (`.app` mode), a Linux systemd user unit, and a Windows service that runs the daemon as SYSTEM in
30
30
  the signed-in session, so UAC prompts can be answered as the Computer's setting says.
31
- - A Docker image (Xvfb + Xfce + Chromium + LibreOffice) that registers from its environment, amd64 and arm64.
32
- - Form filling in the Docker image's Chromium (design: `docs/designs/computer-form-fill-and-vault.md`): a
31
+ - A Docker image (Xvfb + Xfce + Google Chrome + LibreOffice) that registers from its environment, amd64 and arm64.
32
+ - Form filling in the Docker image's Google Chrome (design: `docs/designs/computer-form-fill-and-vault.md`): a
33
33
  force-installed extension that discovers forms without reading values and fills them for agent sessions under
34
34
  the control lease. The extension dials `127.0.0.1:7682`, a port fixed in the image's policy; `FORM_FILL_PORT=` (empty) turns it off, and any other value disconnects the extension, and the daemon
35
35
  accepts a socket only when `/proc` attributes it to a desktop's browser. `pnpm test:image` with
@@ -292,14 +292,17 @@ downloads Cua Driver and a pinned static ffmpeg (6.0, libx264).
292
292
  ## Run in Docker
293
293
 
294
294
  The `computer` image (`ghcr.io/agentconnect-md/computer`, amd64 and arm64, published with each release) is a
295
- Debian trixie desktop with Xvfb, a lean Xfce, Chromium, LibreOffice, Noto CJK fonts, the pinned Node.js (with npm),
295
+ Debian trixie desktop with Xvfb, a lean Xfce, Google Chrome (from Google's apt repository, under Google's terms),
296
+ LibreOffice, Noto CJK fonts, the pinned Node.js (with npm),
296
297
  Debian's Python, Go and Rust toolchains, and the daemon
297
298
  with Cua Driver preinstalled. ffmpeg (GPL) is not in the image: the daemon downloads the pinned, sha256-checked
298
299
  build on first start into the volume, and the viewer polls screenshots until it is there. The entrypoint starts Xvfb on `:1` (`RESOLUTION`, default
299
300
  `1280x800x24`), a session D-Bus, Xfce and a maximized browser, then runs `run` in the foreground as user
300
- `desktop`. The browser is restarted when it exits or crashes (`BROWSER`, default `chromium`; `none` turns it
301
- off; `BROWSER_URL` opens a page). `docker stop` stops the daemon, closes the browser, then the session, with exit
302
- code 0. `/home/computer` is a volume: the Computer key, config, audit log, and the browser profile survive a new
301
+ `desktop`. The browser is restarted when it exits or crashes (`BROWSER`, default `google-chrome`; `none` turns it
302
+ off; `BROWSER_URL` opens a page). Every start of it, the dock's, `xdg-open`'s and an agent's included, goes through
303
+ the daemon's launcher on the profile `browser/main` in the data directory; a volume from the Chromium image has its
304
+ `~/.config/chromium` copied there, open tabs included, on the first start. `docker stop` stops the daemon, closes
305
+ the browser, then the session, with exit code 0. `/home/computer` is a volume: the Computer key, config, audit log, and the browser profile survive a new
303
306
  container. A `HEALTHCHECK` runs `doctor --json --daemon` inside the running daemon.
304
307
 
305
308
  Register it as a Computer: create a token in the console under **Computers → Add Computer** (its **Docker** tab