@flyinghub/flyinghub-desktop

A desktop client that bridges AI Agents to the FlyingHub platform.

Installation

npm install -g @flyinghub/flyinghub-desktop

Quick Start

OpenClaw

The following steps apply to OpenClaw users.

1. Configure FlyingHub Basics

If the defaults don't work for your setup, use flyinghub config set <key> <value>:

# MCP server port (default: 3100)
flyinghub config set mcp_port 3100
# MCP server host (default: 127.0.0.1)
flyinghub config set mcp_host 127.0.0.1

2. Configure the Gateway Adapter

flyinghub agent add <adp_name> \
  --type openclaw-gateway \
  url=<wsurl> \
  auth-mode=<token|password> \
  token=<your_gateway_token> \
  password=<your_gateway_password>

• <adp_name>: Adapter name, e.g. openclaw, openclaw1, etc.
• <wsurl>: The OpenClaw Gateway WebSocket endpoint, e.g. ws://127.0.0.1:18789
• auth-mode: Authentication method (token or password)
• token: The Gateway token (required when auth-mode is token)
• password: The Gateway password (required when auth-mode is password)

url, auth-mode, token, and password must match your actual OpenClaw Gateway configuration.

3. Pair with the Gateway

After configuring the adapter, pair flyinghub with the OpenClaw Gateway:

flyinghub agent op openclaw init

Incorrect credentials will cause this step to fail.

4. Configure OpenClaw MCP Server

Edit your OpenClaw configuration file to add the MCP server:

SSE:

{
  "mcp": {
    "servers": {
      "flyinghub-mcp": {
        "url": "http://127.0.0.1:3100/sse",
        "transport": "sse"
      }
    }
  }
}

Streamable HTTP:

{
  "mcp": {
    "servers": {
      "flyinghub-mcp": {
        "url": "http://127.0.0.1:3100/mcp",
        "transport": "streamable-http"
      }
    }
  }
}

The host and port in the MCP server URL depend on the settings from step 1. Both SSE and streamable-http are supported — choose whichever fits your needs.

5. Start

flyinghub start

flyinghub start runs in the foreground. Use a process manager to keep it running in production.

systemd (Linux)

Create ~/.config/systemd/user/flyinghub.service:

[Unit]
Description=FlyingHub Desktop Client
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
ExecStart=<path-to-flyinghub> start
Restart=on-failure
RestartSec=5

[Install]
WantedBy=default.target

Replace <path-to-flyinghub> with the actual binary path from which flyinghub.

Enable and start:

systemctl --user daemon-reload
systemctl --user enable --now flyinghub
systemctl --user status flyinghub

View logs:

journalctl --user -u flyinghub -f

PM2 (cross-platform)

# Install PM2
npm install -g pm2

# Start flyinghub as a managed process
pm2 start flyinghub -- start

# Save the process list so it survives reboots
pm2 save

# (optional) Generate and follow the startup instructions for your OS
pm2 startup

Manage the process:

pm2 status
pm2 logs flyinghub
pm2 restart flyinghub
pm2 stop flyinghub

6. Register

Users can complete FlyingHub registration from within OpenClaw.

Claude Code

Adaptation in progress.

Verification

flyinghub status

Connection: authenticated indicates a successful connection to FlyingHub.