Xilous Bridge

Set up a client machine

Paste this into Claude Code on the machine you want to set up. Its agent downloads, verifies and installs the client, then walks you through pairing. You approve the pairing in Xilous Bridge Host on the host machine.

Client 0.4.2 · SHA-256 B10DF9D6533EC1F8…
Set up the Xilous Bridge client on this Windows machine. Use PowerShell, do the steps in order, and stop and tell me if any step fails or doesn't match what's described.

1. Download the client build:
   Invoke-WebRequest -UseBasicParsing -Uri "https://xilous-bridge.ucsh.cloud/download/xilous-bridge-client-0.4.2.zip" -OutFile "$env:TEMP\xilous-bridge-client-0.4.2.zip"

2. Verify it. This must print True. If it prints False, delete the file, stop, and tell me:
   (Get-FileHash "$env:TEMP\xilous-bridge-client-0.4.2.zip" -Algorithm SHA256).Hash -eq "B10DF9D6533EC1F86E3D5D6A451504CA816E91A41F1CAF33E316ABFEAB2B4E06"

3. Extract it to a fresh folder:
   Remove-Item -Recurse -Force "$env:TEMP\xilous-bridge-client-0.4.2" -ErrorAction SilentlyContinue; Expand-Archive -Path "$env:TEMP\xilous-bridge-client-0.4.2.zip" -DestinationPath "$env:TEMP\xilous-bridge-client-0.4.2"

4. Install it:
   & "$env:TEMP\xilous-bridge-client-0.4.2\xbridge.exe" install --broker "https://xilous-bridge.ucsh.cloud"
   This installs to %LOCALAPPDATA%\XilousBridge\Client\app, turns on start at login, registers the "xilous-bridge" MCP server with Claude Code (user scope), and opens the Xilous Bridge Client window, which requests pairing with the host.

5. Read the pairing code:
   & "$env:LOCALAPPDATA\XilousBridge\Client\app\xbridge.exe" status
   Tell me the 6-digit code under "pending". Ask me to approve this machine in Xilous Bridge Host (Pairing tab) on the host machine, checking that the code shown there matches exactly. Then wait until I say it's done.

6. Run the status command again and confirm "paired" is true and "host_online" is true. Report what you see.

7. Tell me to restart Claude Code so the bridge_send, bridge_result and bridge_status tools load. Don't send any task through the bridge as part of setup.

Pairing needs approval in the host app, and every task a client sends needs approval on that client. Nothing on this page grants access by itself.