wu:sandbox
wu:sandbox
Section titled “wu:sandbox”Run command through hardened WU sandbox backend
Options:
| Flag | Description | Required |
|---|---|---|
-i, --id <wuId> | Work Unit ID. Required except on wu:create, which auto-generates the next sequential ID when omitted. | Yes |
-w, --worktree <path> | Set the local worktree path; claims verify its confined realpath and exact Git registration | No |
--network <posture> | Network posture for the sandboxed command: off, full, allowlist (default full) | No |
--loopback-grant <host:port> | Linux only, with —network allowlist: also reach exactly this host loopback pair, 127.0.0.1:<port> or [::1]:<port> (repeatable, at most 4, default none; no ranges, hostnames or other addresses); requires —loopback-reason | No |
--loopback-reason <text> | The reason recorded with every —loopback-grant (required with it; printable ASCII, at most 200 characters) | No |
--box <name> | Linux only: start a boxed agent session with this box identity (its clone, home and pnpm store persist) | No |
--profile <name> | Box spawn profile: agent (default), generic, test or build | No |
--interactive | Inherit the terminal and keep Ctrl-C directed at the harness (default when stdin and stdout are TTYs) | No |
--no-interactive | Use the noninteractive protocol; Ctrl-C stops the entire session | No |
--at <sha> | build profile: the full 40-hex commit sha the fresh clone checks out | No |
--out <dir> | build profile: absolute host directory the fd-safe copy-out creates from the box’s /lf/out (regular files only) | No |
--check | Print what a box can reach (mounts, env names, egress rules with reasons, sockets, relay policy, credential path, gate path, engine facts), then the posture of one start with argv true | No |
--conformance | With —box <name>: run the real-process suites in a test box against that box’s clone; fails on 0 executed or any skipped. With —engine <id>: run the engine conformance catalogue instead | No |
--engine <id> | With —conformance: run the conformance catalogue against this registered engine (Linux, from a source checkout). Exits 0 only on a pass: a skipped test fails its case, a case with no test is inconclusive, and inconclusive fails. A report grants nothing. With —admit: the engine to admit | No |
--guest-launch <module> | With —conformance —engine lumenflow.microvm: the guest builder’s guest-launch composition module (absolute path). It is trusted code that runs in the catalogue’s processes: it must be a regular file owned by root or the invoking user, not group- or world-writable, with no symlinked path component, and its sha256 is measured into the report. The catalogue runs for the microVM engine through it as a guest-class target, judged by host-side observers, and prints the report the builder signs a version 2 claim over. Without it the microVM engine refuses: LumenFlow ships no hypervisor launch | No |
--guest-artifact <path> | With —guest-launch (required at least once): a guest image file (VM kernel or root filesystem, absolute path) the host measures into the report. Repeat for each file | No |
--json | With —conformance —engine: print the canonical D4 report JSON instead of the summary. With —admit: print the outcome as JSON | No |
--report <file> | With —conformance —engine: also write the canonical D4 report JSON to this file. With —admit —dry-run: the report to evaluate | No |
--admit | Operator engine admission for this host (Linux, as root). Exits 0 only when a verified claim was written | No |
--launch-user <user> | With —admit: the production identity the kernel and agents run as; the catalogue runs as this non-root user | No |
--dry-run | With —admit —report <file>: evaluate an existing report against the signing rules and print the typed reasons; needs no root and no key, and signs nothing | No |
--schedule | With —admit: print a scheduled re-admission unit for the host; installs nothing | No |
--provision-fixtures | Operator admission host only: prepare the admission test fixtures | No |
--remove-fixtures | Operator admission host only: remove the admission test fixtures | No |