Beta support

Use Skerry with a recovery path

Skerry is beta software. It can disconnect, lose local presentation state, or send unintended input when a bug occurs. Use a non-critical server or least-privilege test account and keep another trusted SSH client available.

Contact

Support is best-effort during beta; there is no service-level agreement. Include the Skerry version/build, device and OS version, keyboard type, network category, orientation, and reproducible steps.

Redact before sending. Do not email passwords, private keys, recovery codes, hostnames, IP addresses, full fingerprints, terminal output, customer data, or uploaded files.

Current requirements

Current limitations

Before reporting a connection failure

  1. Confirm the server is reachable from another trusted SSH client.
  2. Confirm the username and authentication method.
  3. Verify the displayed host-key fingerprint out of band. Never approve an unexpected fingerprint just to continue.
  4. State whether the connection uses Wi-Fi, cellular, VPN, or Tailscale.
  5. Retry once and report whether Skerry reconnects to the existing tmux session or opens a new client.

Severity

Critical

Possible credential or terminal disclosure, wrong-host trust, upload to the wrong destination, destructive unintended input, or repeated crash/data loss. Stop the affected workflow and report privately.

High

Cannot connect or recover, black or unusable terminal, input sent to the wrong pane, or upload/dictation cannot be completed safely.

Normal

Layout, scrolling, keyboard, copy/search, performance, or clarity issue with a safe workaround.

Contact support Read the privacy policy