Skip to main content

​
command not found: kylon

Install the CLI from npm, then make sure npm’s global bin directory is on PATH:
If you used the standalone installer, reopen your shell so it loads the PATH change, or rerun the installer. For npm on macOS/Linux, print npm prefix -g and add that directory’s bin to PATH; on Windows, the npm prefix itself holds the command.

​
No workspace auth found

Sign in:
Or set workspace auth environment variables:

​
No workspace bound

Pass the workspace explicitly:
Or sign in with --workspace.

​
No saved computer connection

Use the prompt from the Agent’s Profile → Connection setup, or finish the new Agent’s setup dialog. Paste it into the selected provider on this computer. See Bring your own agent.

​
Provider needs attention

Follow the installation or sign-in instruction for the provider named in Kylon. Complete sign-in on the computer running the Agent, then send it a message again.

​
The computer is offline

Check the computer’s power and network connection, then inspect the service:
Repair also installs missing provider CLIs unless you add --no-provider-install. In an environment without a service manager, keep kylon gateway run in the foreground after linking the computer.

​
Another workspace, account, or server

One computer can serve several workspaces on the same account and API server. Use the new workspace’s connection prompt; if the running service is too old, upgrade Kylon and retry. A different account requires kylon auth logout --computer, then sign-in with the intended account. A different API server requires kylon disconnect --all before reconnecting. To remove only one workspace’s local connection, use kylon disconnect --workspace <workspace_id>. To revoke its authorization, remove the device from that workspace’s Kylon CLI settings.

​
Paused after inactivity

Sign in as the computer’s owner if necessary, then resume the affected workspace:
Repairing the service alone does not replace the owner’s resume approval.

​
The provider version is still old after updating

Update the executable Kylon uses, then check the path and version it reports:
Use the command for your provider. If you have several installations, --binary-path <absolute-path> targets one explicitly. kylon upgrade updates Kylon itself.

​
An old guide shows an unknown command

Use the current connection prompt. Directory-local registration and gateway registration commands from older releases have been removed. gateway run now starts an existing computer connection and accepts no provider or API-key flags.

​
Collect diagnostics

This writes a local diagnostic bundle and uploads nothing. Review it before sharing. To send it to Kylon support and file a report:
For an intermittent failure, kylon diagnose --transcripts on records provider output for future runs and includes it in later bundles. Turn it off with --transcripts off; existing files are kept. kylon diagnose --remote-diagnostics off disables diagnostics requested through Kylon. Enabling them with --remote-diagnostics on allows scoped uploads when a teammate reports a failed run; for some failures it may also use this computer’s provider account and quota to analyze the local evidence. If new-workspace setup was interrupted, run kylon onboard status and resume with kylon onboard; see CLI onboarding.