Remote Access

Use your zqagent remotely from a phone or another device: tasks run on the node and progress, approval requests and results come back in real time.

One Link, Two Identities

Remote access uses a Rust gateway with a binary WSS protocol:

   Phone / browser ──wss──▶ Rust gateway ◀──wss── Node (the machine running tasks)
                               ▲
                          issue credential (HTTPS)
                               │
                            Hub control plane

• Node: holds a signing secret (FLEET_SECRET) and proves its identity to the gateway with it.
• Terminal (phone / browser): never touches the node secret. It signs in to the Hub, exchanges the account session for a short-lived token scoped to one specific node, then connects directly to the gateway with that token. When it expires, just exchange another one — no re-login needed.

The benefit: your phone never stores a secret that could take over a node, and a leaked token only affects the single node it was scoped to.

Using It on a Phone

1. Enroll the node machine (see the "Cloud Enrollment" section of Server Configuration) and enable remote access in the node settings.
2. Open your user center (Hub URL) in the phone browser and sign in with the same account.
3. Go to the Nodes page — the enrolled node appears there; tap it to open its console.

The native app currently reuses the same console pages. If you are building your own client, the protocol contract is docs/wire-protocol.md in the repository (frames, envelope, message definitions and signing).

What You Can Do

Action	Description
Submit a task	Just send a message and the node starts executing
Add information	Send extra instructions mid-run; they are injected into the current task immediately
Approve	Choose allow / allow all / deny for operations that need authorization
Answer questions	Answer the AI's questions or plan confirmations
Interrupt a task	Stop the current task at any time
Manage sessions	Create, switch and browse sessions
Browse files	Inspect project directories and file contents

Notifications and Progress

• Key moments (approval needed, question asked, completed, error) are pushed to your account and visible on any device.
• Progress (which tool is running, what has been output) is pushed in real time.
• Multiple devices signed in to the same account receive notifications simultaneously.

Availability

• The node only needs outbound access to the gateway (wss://, usually over 443) — no public inbound, no open ports.
• If the gateway is unreachable the node reconnects automatically with exponential backoff, and local functionality is unaffected meanwhile.