Ogp Expose
by @dp-pcs
Expose OGP via a public HTTPS endpoint, usually a stable Cloudflare hostname or named tunnel. Use when the user wants to verify or fix gateway reachability,...
Expose with Cloudflared (Temporary / Ad Hoc)
ogp --for openclaw expose
This will:
1. Start a cloudflared tunnel on the daemon port
2. Display a public URL (e.g., https://abc-def-123.trycloudflare.com)
3. Keep the tunnel running until you stop it (Ctrl+C)
Update your config:
# Edit the correct framework config
Set "gatewayUrl" to the URL shown by cloudflared only if this temporary URL is the intended canonical endpoint
Expose with ngrok (Fallback Only)
ogp --for openclaw expose --method ngrok
This will:
1. Start an ngrok tunnel on the daemon port
2. Display a public URL (e.g., https://abc123.ngrok-free.app)
3. Open ngrok web interface at http://127.0.0.1:4040
Update your config:
# Edit ~/.ogp/config.json
Set "gatewayUrl" to the ngrok URL
The OGP daemon must be installed. If you see errors like 'ogp: command not found', install it first:
npm install -g @dp-pcs/ogp
ogp-install-skills
ogp setup
ogp config show
Full documentation: https://github.com/dp-pcs/ogp
OGP Expose - Public Tunnel Setup
This skill helps expose the OGP daemon to the internet and, more importantly, confirm that the public discovery endpoint matches the intended framework identity.
Tunnel won't start
Public URL resolves but serves the wrong framework
ogp config showgatewayUrlgateway.publicUrl overrides and keep only the canonical gatewayUrlCan't access public URL
ogp --for status )curl http://localhost:/.well-known/ogp Tunnel disconnects frequently
clawhub install ogp-expose