suya hw
suya hw drives hardware validation through BitCrucible. Validation runs execute
against real targets via registered agents, and you can review the history of past
runs. Agents bridge your physical hardware to the Subaya backend.
Agents — suya hw agent
Section titled “Agents — suya hw agent”Manage the agents that connect your hardware to Subaya.
suya hw agent register
Section titled “suya hw agent register”Register a new agent.
suya hw agent register --name bench-01| Flag | Description |
|---|---|
--name <n> |
Display name for the agent. |
suya hw agent list
Section titled “suya hw agent list”List registered agents.
suya hw agent listsuya hw agent revoke
Section titled “suya hw agent revoke”Revoke an agent by id.
suya hw agent revoke <agent-id>suya hw agent run
Section titled “suya hw agent run”Run the agent process (the bridge that services validation runs).
suya hw agent runsuya hw run
Section titled “suya hw run”Start a hardware validation run against a target.
suya hw run --target <target> --test-plan plan.yaml| Flag | Description |
|---|---|
--target <t> |
The validation target to run against. |
--test-plan <file> |
Optional test plan file driving the run. |
suya hw history
Section titled “suya hw history”Show the history of hardware validation runs.
suya hw historysuya hw history --project <project-id> --limit 20| Flag | Description |
|---|---|
--project <id> |
Scope history to a project. |
--limit <N> |
Maximum number of entries to return. |
See also
Section titled “See also”- Core concepts — where hardware validation sits in the phases.
suya sim— simulate before you validate on hardware.