Command line
vaicoa-run accepts --json on every command. The user manual (docs/handbuch.md) shows each command with
its expected output.
vcx and vaicoa-run
Section titled “vcx and vaicoa-run”vcx is the command line for people: pair a device, propose, approve or deny, sign rosters and catalogs, read and
export the audit, open tunnels. vaicoa-run is the client inside an agent session: redeem the session’s ticket, list
the allowed actions, explain, propose, wait, report, or serve all of that as a local MCP server (vaicoa-run mcp).
Generated on 2026-11-07 from vaicoa-core 0f756db.
usage: vcx <command> [flags] access-review Access reviews: vcx access-review list | show <id> | confirm <id> [--except kind:id,...] | lapse <id> [--out draft.json] (owners) approvals List pending approvals approve Approve a pending approval after reviewing it: vcx approve <id> audit Show and verify the audit log; audit export --from --to [--out f]; audit verify-export f catalog Sign a catalog YAML with a release key: vcx catalog sign --key ref [--out env.json] file.yaml; an internal layer with an owner's device: vcx catalog sign --layer org.<name> [--countersign env.json] [--pin-draft draft.json] file.yaml; draft a layer from an MCP server: vcx catalog import-mcp --server <command…|url> --layer org.<name> --provider <p> --out DIR deny Deny a pending approval: vcx deny <id> device Devices: vcx device list [--mine] | suspend <keyId> --reason lost|stolen|compromised|not-mine|other [--note t] [--yes] | lift <keyId> emergency Emergency changes: vcx emergency list [--all]; vcx emergency review <opId> [--concern] [--note …] (owners) image Resolve an image tag to a digest-pinned reference: vcx image digest docker.io/library/nginx:1.27-alpine incidents List incidents: vcx incidents [--state open|closed] key Create, show or delete a device key: vcx key new|show|delete [--key file:…|pkcs11:…|se:…] [--curve p256|p384] [--se-access presence|biometry|password] keys Alias of vcx key member Members: vcx member suspend <memberId> --reason idp-disabled|left|compromised|other [--note t] [--yes] | lift <memberId> op Show an op's state, steps and result: vcx op <id>; end an unknown op (owner): vcx op resolve <id> --outcome done|failed|voided --reason … ops List ops: vcx ops [--env E] [--state S] pair Pair this device with a core: vcx pair --code … --member … --ca-fingerprint sha256:… <core-url> propose Propose an action: vcx propose <action> --env E --param k=v report Print a stored report (e.g. a postmortem): vcx report <reportId> roster Sign or push the roster: vcx roster sign [--in draft.json|draft.json|--countersign env.json] [--push]; vcx roster push env.json; vcx roster draft [--from-core|--from env.json] [--out draft.json]: the next serial of the roster this device verified run Agent session runs: vcx run end <runId> [--reason …] (the member the run acts for, or an owner) sign vcx sign roster|catalog|trigger … (same as vcx roster sign, vcx catalog sign, vcx trigger sign) slo Show the error budgets: vcx slo status Show this device's standing and the roster's expiry: vcx status trigger Sign a trigger YAML (release key or owner device): vcx trigger sign --key ref file.yaml trust Pin what vcx trusts: vcx trust release-key <pub.pem> [--replace] | vcx trust list tunnel Forward a local port to a node service over the TLS tunnelvaicoa-run: usage: vaicoa-run <redeem|pair|task|actions|explain|propose|status|wait|report|review-next|review-decide|mcp|version> [flags]vaicoa-run exit codes: 0 fine (also pending_approval and needs_approval), 1 error, 2 wrong usage, 3 refused,
4 failed, 5 wait timed out.
vaicoa-core
Section titled “vaicoa-core”vaicoa-core runs on the core’s host. It prints no command list; these are the commands it accepts (most take
--config core.yaml or read VAICOA_CORE_CONFIG):
| Command | What it does |
|---|---|
init [--profile starter|standard|strict] | create keys, CA, catalog, policy and the config |
init --quickstart --public-url URL | the one-step setup of the quickstart, solo mode on |
serve | run the core |
check | everything that is weakened, relaxed, missing or pending: profile, readiness, updates, MCP drift, access reviews |
audit-verify | verify the audit chain in the core’s store |
pairing-code [--mobile --qr] | a pairing code or QR for a new device |
join-token --environment E [--node N] | a one-time enrolment token for a node |
node add | the one-liner for enrolling a node |
secret put --slot … --kind … | seal a credential into a slot |
ipsec render|apply | the strongSwan configuration between core and nodes |
member-suspend, member-lift | suspend a member (for example when the identity provider disabled them) |
backup, backup verify, restore | the core’s encrypted backup |
report dora|toil|oncall|kpis|drill … | reports from the audit |
updates status|import | the signed release feed |
usage report|casestudy|remind|reset-id | the voluntary usage report and case study (feedback) |
demo | a demo mode with sample data |
vaicoa-node runs as a service on each host and reads /etc/vaicoa/node.yaml; it has no subcommands for operators.