Orchestration layer for void-box runtime execution.
If the embedded player does not render in your Markdown viewer, use the direct file link: void-control demo video.
- First public release target:
v0.0.1 - Release artifacts are published through GitHub Releases
- Supported
void-boxbaseline forv0.0.1:void-boxv0.1.1or an equivalent validated production build - Release process and compatibility gate details: docs/release-process.md
void-control is the control-plane side of the stack:
- Launches and manages runs on
void-box. - Tracks run/stage/event lifecycle.
- Provides terminal-first and graph-first operator UX.
- Enforces runtime contract compatibility with
void-box.
spec/: Runtime and orchestration contracts.src/: Rust orchestration client/runtime normalization logic.tests/: Contract and compatibility tests.web/void-control-ux/: React operator dashboard (graph + inspector).
cargo run --bin voidbox -- serve --listen 127.0.0.1:43100cargo test
cargo test --features serdeVOID_BOX_BASE_URL=http://127.0.0.1:43100 \
cargo test --features serde --test void_box_contract -- --ignored --nocapturecd web/void-control-ux
npm install
VITE_VOID_BOX_BASE_URL=http://127.0.0.1:43100 npm run devRun bridge mode in another terminal:
cargo run --features serde --bin voidctl -- serveThen start UI with bridge URL:
cd web/void-control-ux
VITE_VOID_BOX_BASE_URL=http://127.0.0.1:43100 \
VITE_VOID_CONTROL_BASE_URL=http://127.0.0.1:43210 \
npm run devcargo run --features serde --bin voidctl- Dashboard uses daemon APIs (
/v1/runs,/v1/runs/{id}/events,/v1/runs/{id}/stages,/v1/runs/{id}/telemetry). + Launch Boxsupports:- editor/upload launch through bridge (
POST /v1/launch) - path-only fallback launch (
POST /v1/runs) when no spec text is provided.
- editor/upload launch through bridge (
