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.
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.
Give each client a separately revocable token. The interface keeps only its prefix; the complete Token appears once at creation. 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.
The encrypted connection runs from KaTrain to Read19. Because the Token is in the path, redact the whole credential in screenshots. Select the remote engine in KaTrain
Open KaTrain's engine settings, choose WebSocket Remote Engine, and paste the complete connection URL. Labels can vary slightly by KaTrain version; update to a release with WebSocket remote-engine support if the option is absent.
After choosing WebSocket Remote Engine in KaTrain, replace only the connection 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.
The settings task has three parts: select the remote engine, paste the WSS URL, and watch connection state after saving. Verify the connection and usage
Load a small game and begin analysis. Once candidate moves return consistently, check recent jobs and analysis-unit usage on the Read19 account page. If it fails, check for a complete URL, a revoked token, or a network that blocks WSS.
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.
The complete evidence chain is: remote engine online, candidates returned, matching Read19 job present, and analysis units changed by actual work.
Signs the connection works
- KaTrain reports a connected remote engine
- Candidate moves and variations keep arriving
- A matching recent job appears in your account
- Analysis units change with actual work