Coldvio CLI
Use Coldvio from a terminal, a script, or as the process behind an MCP client.
Run without a global install
The recommended customer path uses npx so each invocation resolves the released package. A global install can be pinned by enterprise teams after validation.
npx -y @coldvio/[email protected] login
npx -y @coldvio/[email protected] --helpCommon commands
npx -y @coldvio/[email protected] status
npx -y @coldvio/[email protected] voice
npx -y @coldvio/[email protected] contacts list --q "Acme" --limit 10
npx -y @coldvio/[email protected] campaigns get <CAMPAIGN_ID>
npx -y @coldvio/[email protected] posts list --status draft --limit 10
npx -y @coldvio/[email protected] trends --limit 5Commands that change state
CLI approval, rejection, and generation commands require --yes. For approval, export and read the current text, then pass that exact reviewed file back to the command. Coldvio returns 409 if the action changed between review and approval. Approval may queue an external LinkedIn action; generation spends Coldvio credits.
npx -y @coldvio/[email protected] actions review <ACTION_ID> --output reviewed-action.txt
# Open and read reviewed-action.txt before approving
npx -y @coldvio/[email protected] actions approve <ACTION_ID> --yes --reviewed-text-file reviewed-action.txt
printf '%s' 'Email thread' | npx -y @coldvio/[email protected] draft email --subject "Follow-up" --yesAutomation and headless environments
Hosted and headless use is not supported in v0.1 because the CLI intentionally cannot export its stored bearer token. Use interactive login on a customer-controlled machine. Wait for Coldvio's audited, scoped, revocable provisioning flow; never copy or scrape credentials.json into a CI secret.
# Supported v0.1 path: interactive login on the customer-controlled device
npx -y @coldvio/[email protected] loginEnvironment variables
- COLDVIO_API_TOKEN — runtime override reserved for an audited provisioning flow; it is not a v0.1 token-export mechanism.
- COLDVIO_API_URL — approved API origin; a custom origin also requires an environment token.
- COLDVIO_APP_URL — approved browser-login origin for development.
- COLDVIO_CONFIG_DIR — alternate local credential directory for tests or managed devices.
Revoke access
Normal logout revokes the token server-side before removing the local credential. Use --local-only only if the API is permanently unreachable, then revoke the token from the Coldvio account as soon as possible.
npx -y @coldvio/[email protected] logout