Skip to content

OpenGrokBot v0.4.0: teammates' computers without Docker

Choose a tag to compare

@wolfqing wolfqing released this 30 Oct 23:17
· 96 commits to main since this release

Teammates' computers without Docker: on macOS and Linux each teammate can get a browser and a folder of its own on your machine, with commands off by default and sandboxed when on — plus @hono/node-server 2 to clear a security advisory, WebSockets on its built-in support, and croner 11.

Security

  • The gateway runs on @hono/node-server 2.1.5, which clears GHSA-rmxm-3fg6-px4f (serveStatic decoding a path twice). The gateway never used serveStatic, so it was not exploitable here, but no 1.x release fixes it.

Added

  • Local computers — no Docker needed. When Docker is not running (or OPENGROKBOT_COMPUTERS=local), each teammate gets a browser of its own on your machine — your Chrome, Edge or Chromium, else a Chrome for Testing downloaded once into the data dir (OPENGROKBOT_BROWSER, OPENGROKBOT_BROWSER_MIRROR) — with its own profile, and a folder of its own that read_file/write_file cannot leave. The panel shows which kind of computer a teammate has and streams a local browser's screen over CDP. ask_for_login reopens the browser as a real window on the page the teammate was stuck on; I'm done signing in (or the next message) puts it back in the background. macOS and Linux; Windows keeps Docker.
  • Commands on a local computer, off by default. Each teammate has a switch in its computer panel. On, commands run under Seatbelt (macOS) or bubblewrap (Linux), confined to that teammate's folder and a private tmp, with the data dir and your key folders unreadable; the switch refuses to turn on until the sandbox passes a self-check. Off, the shell tool is not even offered to the model.
  • pnpm --filter @opengrokbot/gateway run smoke:local exercises a local computer against a real browser and the real sandbox.

Changed

  • WebSockets — the live stream and each bot's screen — use node-server's built-in support instead of @hono/node-ws, which only declares support for node-server 1.x. Upgrades still pass the gateway's token and origin checks first, and screen frames are relayed byte for byte as before.
  • Routines are scheduled with croner 11. Around daylight-saving changes this follows cron's usual behaviour: a routine set for a time that the clocks skip runs at the first valid time after the jump, and one that repeats through the day keeps running through the repeated hour.

Full changelog: v0.3.1...v0.4.0