Sync servers

remote

or remote
or remote https://your-thatch-host.example/wtp
or remote --transport ws
or --json remote

Replace the example host with your own endpoint. The default is ws://127.0.0.1:8080/wtp with HTTP transport. The saved URL uses ws:// or wss://; HTTP transport converts it to http:// or https:// when sending requests. Seeing a WebSocket URL in configuration does not mean WebSocket transport was selected.

Captured JSON output with no saved configuration:

{
  "configured": false,
  "remote": "ws://127.0.0.1:8080/wtp",
  "transport": "http"
}

Only http and ws are accepted transport flag values. Thatch's HTTP endpoint has a 256 KiB body limit; WebSocket transport is needed for larger messages.

connect

or connect
or --json connect --timeout 10
or connect --transport ws

connect requires an active enrolled identity. It performs a WTP handshake, reports the server's feature availability, and closes the session. --timeout defaults to 30 seconds per read/write or HTTP attempt; it is not an overall command deadline. --transport overrides the saved choice for this command only.

JSON contains remote, transport, gate_token, route, namespace_id, subspace_id and a features object. A successful handshake is not proof that a local file was uploaded or downloaded.

Entitlement tokens

Direct Thatch servers may not require a gate token. A gate-fronted Online endpoint does. or bind mints and stores a token for the active identity; it requires an identity able to sign as the namespace. A paired terminal instead receives its token from the app's pairing flow.

An expired stored token is rejected before connecting. Use or bind again for an owned identity, or renew the pairing in the app for a paired grant. See Ourcana Online for entitlement inspection and remote data commands.