Cloud engine · 03

How to connect KaTrain to Read19 cloud KataGo

Keep the KaTrain interface on your computer while Read19 runs KataGo in the cloud, without configuring a local GPU.

1. Create a Read19 account and access token

   Sign in to the account page and create a token used only for KaTrain. The complete token is shown once; save it in a password manager and keep it out of screenshots, game records, and public posts.

   Create a token used only by KaTrain so a problem can be contained without revoking other clients. Name it after the device and purpose, such as “MacBook · KaTrain,” which makes recent-job attribution easier later. Save the token to a password manager as soon as it appears; keep it out of shell history, synced notes, and screenshots. After the connection test, confirm that the token's last-used time changed on the account page.

2. Copy the KaTrain connection URL

   The account page generates a KataGo WebSocket URL beginning with wss://read19.com/v1/katago/. Its final segment contains your token, so treat the entire URL as a credential.

   The WSS URL contains the protocol, Read19 host, KataGo endpoint, and Token, so the entire URL is a credential. Do not lose its final characters or add quotes and spaces while copying. Being able to open read19.com does not prove that the network permits WebSocket traffic; corporate, campus, or proxy networks may block WSS separately. You can compare the host and URL structure during diagnosis, but never paste the complete address into a public issue.

3. Select the remote engine in KaTrain

   The remote engine needs KaTrain 1.18.0 or later; the Homebrew package can lag behind, so download from KaTrain's GitHub Releases. Open General and Engine Settings, switch to the Remote engine tab, paste the complete URL into KataGo WebSocket URL, and choose Update Settings.

   First check the version in KaTrain's window title, such as KaTrain v1.20.0, and confirm it is 1.18.0 or later; older versions have no Remote engine tab. If you would rather keep the key out of KaTrain's configuration file, install Read19 CLI and enter “/absolute/path/read19 engine analysis” in Override Engine Command on the Local engine tab. In the Remote engine tab, replace only KataGo WebSocket URL rather than copying an entire configuration from another machine. Keep your existing rules, model preferences, and per-analysis choices, then verify connectivity with default or light analysis. Menu wording varies by version, but the checks remain the same: the remote engine is selected, the URL begins with wss://, and saving does not immediately fall back to a local process.

4. Verify candidates, jobs, and analysis units

   Load any small game with a dozen moves, select a position, and begin analysis. After KaTrain receives candidates, confirm that a matching recent job appears in your account and that analysis-unit usage changes. Together, these prove the interface received a result, the request reached the cloud, and usage was recorded.

   For verification, load a small game with a dozen moves, select one position, and wait for candidates. Check KaTrain and Read19 recent jobs together: KaTrain proves the interface received a result, while the account page proves the request reached the cloud and generated usage. If the engine says connected but no candidates appear, confirm that analysis was triggered. If a job appears and fails, inspect token state, account units, and service status instead of repeatedly creating new tokens.