Public: anyone can read this; the crew can change it.

Machines: configurations crew run in, and a shell in the browser #9418

Closed opened this has it

Landed in pull #9462 · run

opened this

The owner, 2026-11-04: "we could have machines. so claude runs in a sandbox environment for the crew members. lets lean into that. i want to be able to make machine configurations for crew members so like the security crew members could have a machine with the tools they need to investigate preconfigured. then i also want the ability to launch a machine and gain a shell. ghostty lib is what we want to reach for here so that we have a fantastic terminal experience in the browser."

Done when:

3 earlier comments
commented

Research, 2026-11-04 (the sources need rechecking when this starts; some were recalled, not read):

  • Terminal: the owner uses Ghostty daily and wants it. Start with Coder's ghostty-web (@coder/ghostty-web, Ghostty's parser compiled to WebAssembly, xterm.js-compatible API by its own claim, under heavy development) behind a thin interface of write, onData, resize, fit. Test typing, resize and reconnect first. Fall back to xterm.js with WebGL only if it fails, and say why here. Its license and maturity were not confirmed.
  • Shell: Bun.spawn({terminal}) (Bun 1.3.5+, POSIX), tmux inside the machine so a reload reattaches, binary WebSocket frames with a small JSON resize frame, the upgrade authenticated by the forge session, and each session logged and recorded.
  • Machine: an OCI image or Nix-built rootfs plus a small config, run under the existing bubblewrap (src/crew/sandbox.ts), with cgroup limits. No platform change needed. Firecracker needs /dev/kvm; gVisor doesn't. How either behaves with hostUsers: false is unknown, so leave both for later.
  • Riskiest assumption: that ghostty-web is stable enough for daily use.
  • Security machine's first tools: gitleaks, Trivy or OSV-Scanner, Nuclei, ZAP, testssl.sh, nmap, against the forge's own copies only.
commented

Reviewed pull #9462 at its head: ticked A crew member runs in its role's machine, with at least today's sandbox isolation.; Tools in a machine never gain access to the forge's secrets, or to systems the forge doesn't own, unless granted.. left open: A machine is a named configuration in a repository's config: its tools, resources and network reach, chosen for a crew role from a list like the other crew config. — Tools and reach are configurable; resources (memory/CPU) were dropped until the cgroup work.; A person with the right permission launches a machine and gets a shell in the browser, with a terminal built on Ghostty's library, or the fallback the research recommends with a stated reason. — Browser shell not started (#9459).; A shell survives a reload, is resized cleanly, ends when it should, and the session's start, end and owner are recorded. — No shell or session record yet.; A security machine ships preconfigured with the investigation tools chosen from the research on this issue. — The tools are declared and named in the brief but nothing installs them (needs an image, #9460)..

commented

Left open after pull #9462 landed: 4 unticked items remain (A machine is a named configuration in a repository's config: its tools, resources and network reach, chosen for a crew role from a list like the other crew config.; A person with the right permission launches a machine and gets a shell in the browser, with a terminal built on Ghostty's library, or the fallback the research recommends with a stated reason.; A shell survives a reload, is resized cleanly, ends when it should, and the session's start, end and owner are recorded.; …). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

commented

Planner: pull #9462 shipped the catalog, the role mapping and the run in its machine. Each open box is now its own issue: resources #9469; security tools installed #9470; the shell and its session records #9471; the Ghostty terminal page #9472 (after #9471). Closed as split into them.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs