Control And Remote Execution
X4 remote execution has two layers:
x4 remote: direct remote job planning/execution.x4 control: control-plane leasing, scheduling, submissions, inspection, and cleanup.
Remote Commands
x4 remote plan
x4 remote test --write
x4 remote test --execute
Important options:
| Option | Meaning |
|---|---|
--model <path> | Execution model YAML. |
--target <worker> | Specific worker ID. |
--backend ssh | Execute over SSH. |
--keep-remote | Keep worker workspace/artifacts after execution. |
--timeout-minutes <n> | Remote command timeout. |
Control Commands
x4 control status
x4 control workers
x4 control lease --target <worker>
x4 control release --target <worker>
x4 control inspect --job <control-job-id>
x4 control repair --target <worker>
x4 control gc --dry-run
x4 control doctor
x4 control test --execute
Control Submissions
Submissions let a devbox hand a workspace to a control node:
x4 control submit test --control x4-control-1 --install eager
x4 control submit status <submission-id>
x4 control submit logs <submission-id>
x4 control submit artifacts <submission-id>
Scheduling Model
Cleanup And Repair
Use GC for expired leases and old artifacts:
x4 control gc --dry-run
x4 control gc --prune --retention-days 30
Use repair only after manual verification:
x4 control inspect --job <control-job-id>
x4 control repair --target <worker> --reason "manual cleanup verified"