pi-dispatch sandbox gateway

An optional browser terminal for an existing sandbox of pi-dispatch, which runs the pi coding agent for you in the background. You do not need this package to use pi-dispatch. Install it on the sandbox's host, then enable it with protected configuration. It is off until explicitly started:

npm install -g @edgehero/pi-dispatch-sandbox-gateway
pi-dispatch-sandbox-gateway --config /absolute/path/sandbox-gateway.json

Use the existing runtime account and an explicit Docker or rootless Podman socket. The gateway attaches only to an already running, registered sandbox. It cannot create a container, choose an image, start another shell or end the sandbox. Open in Terminal and the command-copy route remain available.

The browser workspace uses exact-pinned xterm.js and Dockview for up to four terminal tabs with split panes. Adding a terminal selects another existing shell through fresh console authorization. Moving a pane preserves its connection; closing it detaches only that pane. Run context and the return link follow the selected terminal.

A writing operator may enable read-only watching for up to three other attachments. It is off by default per terminal, with a persistent named roster and individual Remove controls. Each watcher verifies their own operator token. Watch attachments have no runtime input stream or resize capability, receive only new output at the driver's dimensions, and end on driver/consent/session loss. Stop watching leaves the driver and shell running.

The gateway needs its own hostname, separate from the console, and HTTPS for public access. Another port on the same hostname does not isolate cookies. Each browser opening requires the original console tab and operator session, fresh same-token verification, a cookie-bound one-use grant and current authorization. Closing the browser detaches and keeps the shell; the console's confirmed End action remains separate. Phones use the native terminal command.

The package contains its executable and self-hosted terminal assets. It requires Node 22.19 or newer. No repository checkout, browser build tool, provider key, forge credential or console token file belongs in the gateway deployment.

See the complete configuration and operator reference and the accepted security boundaries. The runtime socket retains its full authority if the gateway is compromised; the attach-only interface does not reduce the socket's permissions.