Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.plane.com/llms.txt

Use this file to discover all available pages before exploring further.

Use this page when the Plane CLI does not install correctly, cannot authenticate, or fails at runtime.

Installation and PATH issues

plane command not found

If plane is not available after install:
  1. Restart your terminal.
  2. Run terminalwire setup verify.
  3. Re-run the installer:
curl -sSL https://plane.terminalwire.sh | bash
If verification still fails, manually add ~/.terminalwire/bin to your shell profile, then open a new terminal session.

Browser login issues

Browser did not open automatically

plane login prints a URL and code. If your browser does not open, copy the printed URL into your browser manually.

Authentication timed out

If login times out, run plane login again and complete browser confirmation before the code expires.

Authentication was denied

If you see an access denied message, restart login with plane login and complete the full sign-in flow.

API key authentication issues

Blank API key

plane login --api-key rejects blank values. Enter a non-empty key.

Invalid credential

If you see Invalid credential., confirm you are using a valid Plane API key and retry.

Conflicting login flags

Do not run plane login --api-key --browser. Choose exactly one mode.

Non-interactive auth issues

Command still uses old session

When running automation, set PLANE_API_KEY inline or export it in your shell before running plane commands:
export PLANE_API_KEY=sk_live_...
plane workers list

Not logged in

If plane whoami says you are not logged in, either run plane login or set PLANE_API_KEY.

Network and server errors

Unable to reach authentication server

Check local network connectivity, VPN/proxy rules, and then retry plane login.

Invalid response from authentication server

Retry login. If this persists, capture the exact error text and contact Plane support with command context.

Generic runtime error

If you see Something went wrong. Please try again., rerun the command once. If it keeps happening, capture the command and output and contact support.