All products Lumenlan Kite Product help
Open documentation menu

Troubleshooting

A connected machine stays offline or never appears

Possible cause: the daemon is not running, outbound traffic is blocked by a firewall or network policy, or the machine was reinstalled and now has a different machine code.

What to do:

  1. Confirm the daemon is running on the target. Its system service normally restarts it after an unexpected exit.
  2. Confirm the target has ordinary outbound internet access.
  3. If it still does not appear, run Add machine again from the Fleet page.

An agent says “not signed in” and cannot open a session

Possible cause: Claude Code or Codex uses a third-party gateway whose credentials are outside the default location, or environment variables exist only in a temporary shell profile that the background daemon cannot read.

What to do:

  1. Confirm the agent starts successfully from a command line on the target machine.
  2. For a gateway, set ANTHROPIC_BASE_URL, ANTHROPIC_AUTH_TOKEN, or Codex’s OPENAI_API_KEY as a system- or user-level environment variable. Claude Code can also read env from ~/.claude/settings.json.
  3. Do not rely only on a temporary PowerShell profile. Restart the Kite daemon after changing the setting.

The terminal disconnects, often immediately after connecting

Possible cause: a local proxy in TUN or transparent-proxy mode is intercepting the terminal’s binary stream.

What to do: configure the proxy to connect directly to Kite domains, or temporarily use compatible Base64 transport and reconnect. Switching to an ordinary network or disabling transparent proxy is a quick way to confirm the cause.

Pasting or dropping an image fails

Possible cause: a temporary network problem or unavailable file storage in the current deployment.

What to do: retry once and check the network. If the problem persists, switch networks or ask the administrator to check storage health.

Windows shows a black console window and closing it disconnects the machine

Possible cause: background-service installation failed and the daemon fell back to a foreground process. The black window is the daemon itself.

What to do: update to the latest client and reinstall the background service. Current versions run without a visible console window.

The console shows the wrong version or automatic update did not apply

Possible cause: an older running client could not replace itself, especially on Windows.

What to do: update manually once to the latest version. Automatic updates should resume afterward.