Skip to main content

Xiaohe Client

Desktop shell for the same chat UI as the Web UI. It talks to a Session API (local or remote).

Install: Install & update. Short map: Overview.

Chat on this machine (typical)​

  1. Install Agent and Client.
  2. Start Session:
xiaohe server install
xiaohe server start
  1. Mint a Session key (this is for chat — not a Pro license):
xiaohe server pair
  1. Open Client → Settings → Connection → Local (http://127.0.0.1:8110).
  2. Paste the xh_… key into Xiaohe service key → Test key.
  3. Optional: set workspace path (often ~/xiaohe).
  4. New session → send a message.

If the model fails, set a provider on this machine: xiaohe switch provider … or Settings → Assistant.

Settings → Connection → Local service can show status / doctor / restart when the app can reach local xiaohe server.

Remote or hosted Session​

  1. Settings → Connection → Add remote server (or Cloud → https://agent.xiaohe.team).
  2. Paste API base + Session key for that host → Test key → chat.

First launch & Pro​

  • Open the app; macOS may need right-click → Open once.
  • ~7-day trial for desktop Pro features; then activate a license under Settings → Authorization (xh_lic_… from the account center).
  • Chat still needs the Session key under Connection. MCP / Skills Hub uses xh_mcp_… under Authorization.

Chat UI​

Sidebar sessions · composer · approval bar when asked · skills / /skill-name · export when offered.

Optional (Pro)​

Settings → Private network: in-app Tailnet (not the system Tailscale app). Use a Tailnet URL such as http://100.64.x.x:8110 as the API base when Session runs on another machine on that network.

If something fails​

ProblemFix
Offlinexiaohe server status or Local service panel
401 / bad keyxiaohe server pair again; paste the new key
Activation gatePaste Pro license, or use Web UI without desktop Pro
Provider errorConfigure provider on the Session host

Updates: Client via Settings → Updates; Agent via xiaohe upgrade (soak: xiaohe upgrade --beta).