CompShare CLI

Manage CompShare GPU compute and MiniMax H3 from the terminal with the compshare command.

Operating rules

Use compshare --json ... for automation. Parse the single JSON document instead of terminal tables.
Run compshare --json COMMAND --help before using an unfamiliar command or option. JSON help returns the current command, parameter and subcommand structure without requiring credentials.
Put global options before the command group, for example compshare --json --profile production instance list --all.
Inspect resources and prices before changing them. Use instance create --dry-run before a real create operation.
Add --yes only when the user has authorized the mutation. Deletion, stopping, reinstalling, resizing and similar operations can require confirmation.
Use explicit timeouts for creation, lifecycle waits and remote jobs. After a timeout, inspect the resource before retrying because the remote operation may still be running.
Keep sensitive output redacted. Do not use --show-sensitive unless the user explicitly needs the raw password, IP, access URL or login command.
Do not print, log or commit API credentials. Prefer an existing profile or environment variables over passing a private key on the command line.