Skip to content

Desktop app

The desktop app includes the chat interface, a local agent-wechat hub and the wx command-line tool. The standalone npm CLI remains available separately.

  1. Download the app for your platform from GitHub Releases.

    PlatformDownloadInstall
    macOS, Apple silicon.dmgDrag AgentWechat into Applications.
    Windows, x64 or ARM64-setup.exe matching your processorRun the installer for your user.
    Ubuntu 24.04, x64 or ARM64.debOpen it with your package installer.
  2. Open AgentWechat and choose Use this device to run a local hub, or Connect to another hub to enter its address and access key.

  3. Add a WeChat profile and follow the sign-in instructions.

  4. Open Settings to configure network access, install the wx command or export an access key for another client.

The app runs under your user account. It uses your system credential store and native file dialogs; network access and opening at login are optional settings. Enabling access from other devices may require allowing the hub through your system firewall.

Connect the CLI

Desktop access keys are saved in your system keyring. Independent CLI installations use protected token files:

Terminal window
wx config servers add desktop --url http://127.0.0.1:6174 --token-file /path/to/exported-key
wx --server-name desktop status

The status response identifies the hub and its native backend. Use the address displayed by the desktop app if you changed its port.

Allow network access

Network access uses HTTPS. The desktop generates its own certificate; you do not need to supply TLS files. Standalone wx serve supports --tls-cert-file and --tls-key-file when you want to use an existing certificate, such as one issued for your hub’s LAN hostname. Publicly trusted HTTPS addresses, including Tailscale Serve addresses, need no extra certificate. For a hub using a private certificate, copy it from the hub’s desktop Settings, then paste it under Advanced → Private certificate (optional) when connecting from another desktop app. A browser uses its own certificate trust settings. The CLI can trust that certificate for an invocation:

Terminal window
wx --server-name desktop --ca-cert-file /path/to/certificate.pem status

Register the HTTPS address as the saved server URL when connecting over the network.