Skip to content
Claudette

Remote Workspaces

Claudette can connect to workspaces on another machine over an encrypted WebSocket connection. The local app discovers or connects to a remote server and displays remote repos, agents, and terminals alongside local ones.

Sharing from the Desktop App

Section titled “Sharing from the Desktop App”

Click Share this machine in the sidebar. The server starts automatically as a subprocess — no separate installation required. The server is embedded in the Claudette binary (gated behind the default-enabled server feature).

On startup the server prints a connection string:

claudette-server v0.8.0 listening on wss://0.0.0.0:7683
Name: Work Laptop


Connection string (paste into Claudette):
  claudette://work-laptop.local:7683/aBcDeFgH1234...

Headless Server (Standalone)

Section titled “Headless Server (Standalone)”

For headless machines without a GUI, the standalone server binary is still available:

Terminal window
# Build and install the standalone server binary
cargo install --path src-server


# Start it (generates a TLS certificate and pairing token on first run)
claudette-server

Connecting from the Local App

Section titled “Connecting from the Local App”

Automatic (LAN)

Section titled “Automatic (LAN)”

If both machines are on the same network, the server appears automatically in the sidebar under Nearby. Click Connect and enter the pairing token when prompted.

Manual

Section titled “Manual”

Click + Add remote in the sidebar footer and paste the full connection string. Claudette authenticates, stores a session token, and reconnects automatically on future launches.

Server Management

Section titled “Server Management”
Terminal window
# Regenerate the pairing token (revokes all existing sessions)
claudette-server regenerate-token


# Print the current connection string
claudette-server show-connection-string


# Bind to a specific interface or port
claudette-server --bind 192.168.1.50 --port 9000


# Disable mDNS advertisement
claudette-server --no-mdns

Security

Section titled “Security”

All traffic is encrypted with TLS. The local app pins the server’s certificate fingerprint on first connection (trust-on-first-use), similar to SSH’s known_hosts. This means:

  • The first connection requires manual verification of the pairing token
  • Subsequent connections are authenticated automatically via the pinned certificate
  • If the server’s certificate changes, you’ll be prompted to re-verify