zerg-cyberdeck

License notice: This package is source-available, not open source. Free company use is limited to purpose-bound evaluation. Commercial development, ongoing company engineering, customer work, and other Commercial Use require a separate commercial license. By exercising a permission in the package license, you accept its conditions; a separate signed agreement controls any commercial rights.

zerg-cyberdeck installs the zcd command-line client for Zerg CyberDeck. It manages workspace-scoped clone decks, checks running clone and Zerg services, and asks the CyberDeck server to run its deployed SDK/API conformance suites.

This beta requires Node.js 22 or later.

Install

Until the first stable release, install the next channel:

npm install --global zerg-cyberdeck@next
zcd --version

Sign in

zcd login

The CLI prints a short user code and opens the CyberDeck authorization page. Sign in through the normal browser flow, choose one of your workspaces, and approve the device. The resulting 30-day personal token is bound to that workspace and stored in a mode-0600 config file.

Useful alternatives:

zcd login --url https://your-cyberdeck.example --workspace "Blue Team"
zcd whoami
zcd logout

For non-interactive automation, set ZERGCYBERDECK_TOKEN to an independently issued scoped token. ZERGCYBERDECK_BASE_URL changes the server, and ZERGCYBERDECK_CONFIG_DIR isolates the local config directory.

Common commands

# The server is authoritative for available targets and conformance support.
zcd catalog

# Create a deck and start explicitly selected clones.
zcd up --clones zlunk,zokta --name "SDK check"

zcd ls
zcd status --deck <deck-id>
zcd check --deck <deck-id>
zcd seed --deck <deck-id> --reset

# Start and poll server-side SDK/API conformance; reports remain local.
zcd sdk --deck <deck-id> --vendor zlunk

zcd down --deck <deck-id> --yes

zcd sdk --clones ... may provision the clones you name. Review the selection and the target CyberDeck before running it; clone environments consume compute. The CLI does not bundle vendor SDKs or a local conformance runner.

Automation and clone discovery

Inventory commands retain their human-readable output by default and expose a stable, versioned form for scripts:

zcd catalog --json
zcd ls --json
zcd ls --deck <deck-id> --json

Each JSON document has "schemaVersion": 1. Catalog targets may advertise a non-secret managedCredential descriptor with its purpose, authorization scheme/header, and display label. Older CyberDeck servers that omit this descriptor remain supported.

Inspect one deployment by a unique vendor name or exact clone UUID:

zcd inspect --deck <deck-id> --clone zlunk
zcd inspect --deck <deck-id> --clone <clone-uuid> --json

The inspection includes normalized runtime URLs and status, published Zerg module fields, artifact qualification, and the non-secret credential hint. If a deck contains multiple clones of the same vendor, pass a clone UUID.

Credential disclosure is a separate, explicit write-authorized POST action:

zcd credentials --deck <deck-id> --clone zlunk
zcd credentials --deck <deck-id> --clone <clone-uuid> --json

Successful credential output contains a secret and should not be logged. Credential and runtime error payloads are redacted from stderr so a malformed or failed server response cannot echo a token through CLI diagnostics.

Run zcd <command> --help for all options.

Licensing

This package is source-available, not open source. Purpose-limited evaluation and the specified personal, educational, research, and nonprofit uses are available under the Zerg Source Available License 1.0. Commercial production, commercial development, for-profit internal use, managed services, governmental operational use, and competing general-purpose platforms require a separate signed license. See commercial licensing or contact [email protected].

Third-party software remains under its own terms; see THIRD_PARTY_NOTICES.md.