Skip to main content
This command is not implemented in v0. Use the local control plane for development.

​
Overview

The login command will authenticate your CLI with Wormkey using OAuth device flow. This feature is planned for a future release.

​
Usage

wormkey login

​
Current Behavior

In v0, running this command displays: 
$ wormkey login
Login not implemented in v0. Use local control plane.

​
Planned Functionality

In future versions, the login command will:
  1. Initiate device flow - Display a code and URL
  2. Open browser - Direct you to authenticate in your browser
  3. Store credentials - Save authentication tokens locally
  4. Enable account features - Access to dashboard, analytics, and tunnel management

​
Expected Flow

$ wormkey login

To authenticate, visit:
https://wormkey.run/device

And enter code: ABCD-1234

Waiting for authentication...
✓ Successfully authenticated as [email protected]

​
Workaround for v0

While login is not implemented, you can still use Wormkey by:
  1. Running the local control plane for development
  2. Using the --local flag with wormkey http
  3. Setting WORMKEY_ENV=local environment variable

​
Local Development Setup

wormkey http 3000 --local

​
Authentication in v0

Currently, Wormkey v0 operates without user accounts:
  • Anonymous tunnels - No authentication required to create tunnels
  • Owner claim URLs - Claim tunnel ownership via one-time URLs
  • No dashboard - Tunnel management through CLI only

​
Future Enhancements

When login is implemented, you’ll gain access to:

Persistent Sessions

Tunnels associated with your account

Web Dashboard

View and manage all your tunnels

Analytics

Traffic stats and usage metrics

Team Features

Share and collaborate on tunnels

​
See Also

Build docs developers (and LLMs) love

Get started for freeTalk to us