The CLI

There is no super CLI yet. It is a planned work package and no package has been published, so anything you read elsewhere describing super deploy as something you can install today is describing the intent rather than the state.

This page exists rather than being omitted because a missing page reads as an oversight, and an agent that assumes the command exists will spend a while working out why it does not.

What to use instead

Everything the CLI would do is already one HTTP request, and both paths are documented:

• An agent with a shell posts to /deploy directly. That is what the skill installs and what the pairing brief teaches.
• An agent without a shell — a hosted chat assistant reaching tools through a connector — uses the MCP endpoint, which wraps the same call.

Neither is a workaround. The endpoint is the interface; a CLI would be a convenience over it.

Why an endpoint and not a bucket

The alternative design was direct S3-style multipart upload to storage. It lost for a reason that outlived the convenience argument: no S3 access keys exist for the storage account, and with an endpoint none ever need to. The worker already holds a native binding to the bucket, so the only credential in play authorises deploying rather than raw bucket access — a much smaller blast radius for no loss at artifact sizes.