あなたのAIエージェントを、
HUDに。

この英語の例を、OpenClawが動作しているコンピューター上のアシスタントにコピーしてください。最初に調査を求める例であり、掲載によって端末が設定されることはありません。

EXAMPLE PROMPT · English

Set up Tailscale access to the OpenClaw Gateway on this computer running OpenClaw so my existing ClawLensXR Android app can connect securely without an app update.

This is a native app connection, not a browser Control UI or necessarily an official OpenClaw node. Do not assume browser-only Tailscale authentication will authenticate the app.

    Inspect the active OpenClaw profile/service, Gateway port, authentication and existing Tailscale installation/Serve configuration. Consult installed documentation and CLI help; do not assume paths, ports or command syntax.
    Connect the Gateway host and Android phone to the same tailnet, with MagicDNS and HTTPS certificates enabled. Guide me through any required login or administrator approval privately; do not expose credentials or setup codes in chat.
    Keep the Gateway bound to loopback. Configure Tailscale Serve, not Funnel, to provide trusted HTTPS/WebSocket access through the host’s full *.ts.net hostname.
    Preserve existing Serve routes, sessions, authentication, pairing and other services. Inspect and merge configuration—do not reset or replace unrelated routes.
    Keep suitable Gateway authentication enabled for the native app. Do not rely solely on Tailscale browser identity headers, disable device authentication or weaken TLS verification.
    Verify tailnet access rules permit the phone to reach the selected Serve HTTPS port. Do not open router ports, expose the Gateway publicly or configure an exit node unnecessarily.
    Give me the exact app connection URL, normally wss://<gateway-full-hostname>.ts.net with the appropriate port/path. Use the certificate hostname, not the numerical Tailscale IP. Provide secure instructions for entering the required app authentication; never put tokens in URLs or chat.
    Help add a separate saved ClawLensXR connection without deleting the existing connection or changing its credentials. If pairing is required, correlate the phone’s fresh request and approve only that exact request with appropriate owner permission.
    Verify a fresh connection from the actual Android app: correct Gateway, successful authentication/pairing and stable initial requests. A successful ping, working browser dashboard or saved profile alone is not proof.
    Summarize the changes, exact connection URL, remaining blockers and rollback procedure.

Do not update OpenClaw, modify the Android app, reset pairing, rotate existing credentials, start voice recordings or send chat commands. Ask before installing missing software or making disruptive changes. Start with inspection.

OpenClaw接続ガイド