Installation and PATH issues
plane command not found
If plane is not available after install:
- Restart your terminal.
- Run
terminalwire setup verify. - Re-run the installer:
~/.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, runplane login again and complete browser confirmation before the code expires.
Authentication was denied
If you see an access denied message, restart login withplane login and complete the full sign-in flow.
Signed-in workspace is not available here
If you seeAuthenticated with Plane, but workspace reference ... is not mapped to a known Plane workspace.,
you signed into a Plane organization or workspace that is not available in this environment. Sign in
to the correct workspace or contact Plane support.
API key authentication issues
Blank API key
plane login --api-key rejects blank values. Enter a non-empty key.
Invalid credential
If you seeInvalid credential., confirm you are using a valid Plane API key and retry.
Conflicting login flags
Do not runplane login --api-key --browser. Choose exactly one mode.
Non-interactive auth issues
Command still uses old session
When running automation, setPLANE_API_KEY inline or export it in your shell before running plane commands:
Not logged in
Ifplane 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 retryplane 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 seeSomething went wrong. Please try again., rerun the command once. If it keeps happening, capture the command and output and contact support.