Skip to main content
The gateway receives workspace requests, starts the selected provider, streams progress, and returns replies. One installation can run several Agents across several workspaces on the same Kylon account and API server. Each workspace has a separate computer authorization.

​
Connect an Agent

Use the prompt from Kylon’s creation flow or the Agent’s Profile → Connection setup. Paste it into the selected provider on the computer where the Agent should run. See Bring your own agent.

​
Inspect or run the service

gateway status reports daemon, connection, and per-Agent health. gateway run runs the daemon in the foreground using the saved computer connection; it does not accept provider, server, or API-key flags.

​
Repair and upgrade

Repair reinstalls the service and checks for missing provider installations. Add --no-provider-install to repair Kylon without installing providers. kylon upgrade fetches the newest published build for the current channel and updates the running service. To install the build selected by npm’s production tag explicitly:
The normal upgrade waits for active requests to finish before restarting. gateway service cancel cancels an upgrade in progress. gateway service upgrade --force skips that wait and interrupts active work; use it only when that is intended.

​
Automatic updates

Automatic updates are on by default. With several workspaces connected, select --workspace <id> or --all when changing the setting. Manual upgrades remain available when automatic updates are off.

​
Disconnect or change accounts

Select one workspace to leave its other connections running, or disconnect them all. Without a selector, disconnect works only when the target is unambiguous. Add --yes for a non-interactive confirmation; --json requires it. To switch the computer to another Kylon account, run kylon auth logout --computer, then sign in with the intended account. This stops the current account’s Agents and logs its computer connections out. To switch API servers, disconnect all local connections first.

​
Availability and recovery

  • kylon gateway resume --workspace <workspace_id> resumes a computer paused after inactivity, using its owner’s saved workspace login. Run kylon login as that owner first if needed.
  • kylon keep-awake [always|while-busy|off] controls idle sleep prevention on macOS and Windows while on AC power. always is the default; lid-close and battery sleep rules still apply. No argument shows the setting.
  • kylon provider update codex or kylon provider update claude-code updates the provider executable that Kylon actually uses. This is separate from upgrading Kylon.
  • kylon diagnose collects a local diagnostic bundle; see Troubleshooting before sharing it.
  • Credentials are managed through Connections. All gateway secret commands are retired.
To revoke device access, remove it from Settings → Developer tools → Kylon CLI → Authorized devices. Clearing local state does not revoke workspace authorization.