Thanks to visit codestin.com
Credit goes to docs.wavedash.com

Skip to main content
The wvdsh auth commands manage your authentication with Wavedash.

​
Login

wvdsh auth login
This opens your default browser to complete OAuth authentication. Once you authorize the CLI, your API key is stored locally.

​
Manual token entry

If browser-based login isn’t available, you can provide an API key directly: 
wvdsh auth login --token YOUR_API_KEY
You can generate API keys in the Developer Dashboard at wavedash.com.

​
How it works

  1. The CLI starts a local HTTP server on a random available port
  2. Your browser opens the Wavedash authorization page
  3. After you authorize, Wavedash redirects back to the local server with your API key
  4. The CLI stores the key in your credentials file

​
Logout

wvdsh auth logout
This removes your stored API key from the local credentials file.

​
Status

wvdsh auth status
Check your current authentication status. If logged in, this displays a masked preview of your API key (first 6 and last 3 characters). Example output: 
✓ Authenticated
API Key: wd_abc...xyz

​
Credentials file

Your API key is stored in a JSON file with restricted permissions: 
~/Library/Application Support/gg.wavedash.cli/credentials.json
Never share your credentials file or commit it to version control.