docs: mobile/remote HTTPS access improvements (Tailscale, Windows, gateway token)

[myauroraagi-dev]

Summary

Tested ClawSuite v3.3.0 on Windows PC with Tailscale for mobile access. Several gaps found in documentation and setup experience.

Issues Found

1. No HTTPS/Tailscale guide for remote access

There is no documentation for accessing ClawSuite from mobile or remote devices. The steps required:

• Run tailscale cert <hostname>.tailXXXX.ts.net to generate TLS cert
• Install local-ssl-proxy and proxy port 3000 → 8443 with the cert
• Access via https://<hostname>.tailXXXX.ts.net:8443

2. Windows: npm run dev fails due to inline NODE_OPTIONS

The dev script uses NODE_OPTIONS="--max-old-space-size=2048" vite dev which breaks on Windows PowerShell. Workaround:

$env:NODE_OPTIONS="--max-old-space-size=2048"
npx vite dev --port 3000

3. Gateway token redacted in some environments

openclaw config get gateway.auth.token returns __OPENCLAW_REDACTED__ in certain shell contexts. Workaround is to read directly from ~/.openclaw/openclaw.json.

4. Version mismatch causes stuck 'Initializing' state

ClawSuite v3.3.0 calls nodes.list which doesn't exist in OpenClaw 2026.3.8, causing the UI to hang on initializing. No compatibility matrix exists in the docs.

Suggested Fixes

• Add docs/mobile-remote-access.md with Tailscale HTTPS setup guide
• Fix npm run dev script to be cross-platform (use cross-env package)
• Add note about gateway token fallback in .env.example
• Add version compatibility table to README

[outsourc-e]

Added docs/remote-access.md covering Tailscale setup (TLS certs, local-ssl-proxy), LAN access, Docker, Windows/WSL2 port forwarding, gateway token config, and troubleshooting.