Paseo Relay

Use the local paseo CLI to operate the daemon on the selected host. Relay is the network connection. Start with observation; inspecting a session does not authorize sending it a prompt, resuming, stopping, reloading, restarting, archiving, or detaching it.

1. Establish the host and connection

Record the local host, the intended remote host, and the authorized operation. Discover the installed CLI with command -v paseo, paseo --version, and command-specific --help. A host's display label is neither its SSH address nor sufficient connection information.

Read connection.md to obtain or reuse a pairing offer. The workable starting points are:

• An offer URL supplied privately by the user or stored in their explicitly authorized connection file.
• An already authorized connection to that daemon, through which Paseo can return its offer.
• Access to the target machine or its operator for first pairing. Relay must already be enabled, or enabling it must be authorized.

An offer contains the target serverId, Relay endpoint/TLS setting, and daemon public key. Use Paseo's parser and encrypted Relay transport. Keep connection materials outside the repository and out of command arguments, transcripts, and shared logs.

CLI 0.8.0 accepts an offer URL through PASEO_HOST or --host, although its help lists tcp/ssh. Prefer PASEO_HOST loaded from a private file. Verify the selected daemon's serverId and advertised hostname before choosing its resources. Some bundled 0.8.0 builds ignore the remote target for daemon status and return local status. If that command cannot prove the remote identity, use the small SDK identity check in sdk.md. Do not substitute local status for a remote handshake.

Keep subsequent commands in that same target environment. Treat (serverId, workspaceId) and (serverId, agentId) as the identifiers. Use full IDs obtained from this host; CLI prefix/title matching can select an unintended session.