Hyperproxy CLI

The Hyperproxy CLI manages proxies, credential vaults, and secure shares from macOS, Linux, and Windows. It authenticates through the Hyperproxy dashboard's OAuth 2.0 device authorization flow and stores rotating tokens in the operating-system credential store.

Install

Public CLI downloads are not available yet. Until they are, you can do everything below from the dashboard or the REST API.

If you already have the CLI, sign in as shown below and manage its sessions from CLI settings.

Sign in

cifp login

1. The CLI prints a short code and opens /device.
2. Sign in to Proxies.ai, verify that the code matches, and review requested scopes.
3. Approve access. The waiting CLI receives short-lived access and rotating refresh tokens.

For a remote terminal, run cifp login --no-browser and open the displayed URL on another device.

Proxy commands

cifp proxy list
cifp proxy create demo --region sjc --mode auto-auth
cifp proxy pause <proxy-id>
cifp proxy resume <proxy-id>
cifp proxy delete <proxy-id> --yes
cifp connect <proxy-id>

Vault commands

cifp vault create <proxy-id> "OpenAI production"
printf '%s' "$OPENAI_API_KEY" | cifp vault secret set <vault-id> OPENAI_API_KEY --value-file -
cifp vault service add <vault-id> --template openai
cifp vault service list <vault-id>

Secret values are read from a file or stdin and are never echoed. See Credential Vaults for binding behavior.

Secure-share commands

cifp share create <proxy-id> --expire 5m --uses 1 --vault <vault-id>
cifp share list --proxy <proxy-id>
cifp share url <proxy-id>
cifp share remove <share-id>

See Secure Sharing before distributing a capability URL.

Automation output

Add --json to read commands for stable machine-readable output. Use --profile to isolate credentials for multiple Hyperproxy deployments and --api-url to select a control-plane origin.

Manage authorized terminals

Open CLI settings to review device metadata, last use, scopes, and revoke individual refresh-token sessions.