The coordinated release of the cross-edition work, and its headline is remote execution.
run_bash takes a host. The command runs there over ssh, key-based login required. sudo on that
machine behaves exactly like local sudo: explicit sudo plus elevated=true, a password prompt that
names the host, and delivery through a single-use SUDO_ASKPASS helper on the remote side, so the
password never appears in a command line, in a process argument, or in the command's environment.
Passwords are cached per host for the run and never offered to another host. A failed sudo
authentication discards the cached password instead of replaying it. Stop kills the remote command and
cleans up its askpass directory. On the web UI the sudo prompt is back, restored from the worker
event, with the host named in it.
That is the product direction: an agent on your desk driving the machines you administer, with the privilege path as tight as it can be on a machine you do not control.
The rest is architectural, and it is the reason the editions can keep shipping in step. The web
worker is refactored into an embeddable class (WebWorker / pengy::WebWorker /
pengy::web_worker), so the same worker powers the desktop's web front end and a standalone
pengy-web. The C++ web UI, which had been a raw-socket prototype, is retired in favour of a real
HTTP server (httplib) with SSE, and that brings with it the CSRF and origin checks the other editions
already had, a real tool-approval UI, and a web worker with no Qt dependency.
Also in here: pengy-cli as a Rust entry point with --list-models and /endpoint, per-model
context_window, tool-confirmation policy on the CLI with yolo_mode, a 64 MB upload guard, and the
"server overloaded" HTTP 429 help string.